OID reference

trapMgmtApplicationProtocol

1.3.6.1.4.1.1206.4.1.4.1.6.1.4

Description

<Definition> This object identifies the application layer protocol to use for TMP (Transportation Management Protocol) traps. The possible values are: 1 - other : not defined in this standard 2 - snmp : use SNMPv1 Trap 3 - sfmp : use SFMP Trap <Superseded by> SNMP-TARGET-MIB.snmpTargetParamsMPModel (RFC 3413) <Informa…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.1.4.1.6.1 (trapMgmtEntry)
Node code
4
Node name
trapMgmtApplicationProtocol
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.1.4.1.6.1.4
URN notation
urn:oid:1.3.6.1.4.1.1206.4.1.4.1.6.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) ntcipTraps(4) trapMgmt(1) trapMgmtTable(6) trapMgmtEntry(1) trapMgmtApplicationProtocol(4)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/1/4/1/6/1/4
  • /ISO/Identified-Organization/6/1/4/1/1206/4/1/4/1/6/1/4
  • /ISO/3/6/1/4/1/1206/4/1/4/1/6/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/Protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/Protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/Protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/Protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/Protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/Protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/Protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/Protocols/ntcipTraps/trapMgmt/trapMgmtTable/trapMgmtEntry/trapMgmtApplicationProtocol
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
deprecated, mandatory
Default value
snmp

Definitions may combine these properties differently.

Compare 2 source variants

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

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
deprecated
Default value
snmp

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

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory
Default value
snmp

Enumerated values

Numbers refer to source variants above. Each value is shown only for variants that define it.

ValueNameSource variants
1other1, 2
2snmp1, 2
3sfmp1, 2

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In NTCIP1201-NtcipTraps, the row index trapMgmtManagerIndex is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1206.4.1.4.1.6.1.4.<trapMgmtManagerIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.1.4.1.6.1.4

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

Show 3 published definitions

trapMgmtApplicationProtocol · deprecated

trapMgmtApplicationProtocol   OBJECT-TYPE
  SYNTAX       INTEGER { other (1),
                         snmp (2),
                         sfmp (3) }
  MAX-ACCESS   read-write
  STATUS       deprecated
  DESCRIPTION
    "<Definition> This object identifies the application layer protocol to
      use for TMP (Transportation Management Protocol) traps. The possible 
      values are:
        1 - other : not defined in this standard
        2 - snmp  : use SNMPv1 Trap
        3 - sfmp  : use SFMP Trap
    <Superseded by> SNMP-TARGET-MIB.snmpTargetParamsMPModel (RFC 3413)
    <Informative> In the replacement design, fdNotifyChannelTarget points
      to a row in the snmpTargetAddrTable, which points to a row in the 
      snmpTargetParamsTable, which contains snmpTargetParamsMPModel, which 
      indicates a message processing model (i.e., SNMPv1 vs. SNMPv3). If the 
      NTCIP (or NEMA) community desired, it could define its own processing 
      model (e.g., something similar to SFMP with security) and assign it a 
      value of (1206 * 256) + id, where id is between 0 and 255 (see RFC 
      3411).
    <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4"
  DEFVAL { snmp }
  ::= { trapMgmtEntry 4 }

trapMgmtApplicationProtocol · deprecated

trapMgmtApplicationProtocol OBJECT-TYPE
SYNTAX       INTEGER { other (1),
                          snmp (2),
                          sfmp (3) }
MAX-ACCESS read-write
STATUS       deprecated
DESCRIPTION
   "<Definition> This object identifies the application layer protocol to use
   for TMP (Transportation Management Protocol) traps. The possible values



                                                                                         

                 
        

  are:
  1 - other : not defined in this standard
  2 - snmp : use SNMPv1 Trap
  3 - sfmp : use SFMP Trap
  <Supplanted by> SNMP-TARGET-MIB.snmpTargetParamsMPModel (RFC 3413)
  <Informative> In the replacement design, fdNotifyChannelTarget points to a
  row in the snmpTargetAddrTable, which points to a row in the
  snmpTargetParamsTable, which contains snmpTargetParamsMPModel, which
  indicates a message processing model (i.e., SNMPv1 vs. SNMPv3). If the
  NTCIP (or NEMA) community desired, it could define its own processing model
  (e.g., something similar to SFMP with security) and assign it a value of
  (1206 * 256) + id, where id is between 0 and 255 (see RFC 3411).
  <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4"
DEFVAL     { snmp }
::= { trapMgmtEntry 4 }

trapMgmtApplicationProtocol · mandatory

trapMgmtApplicationProtocol          OBJECT-TYPE
       SYNTAX    INTEGER {
                    other (1),
                    snmp (2),
                    sfmp (3)
                           }
       ACCESS    read-write
       STATUS    mandatory
       DESCRIPTION
       "<Definition> This object identifies the application layer protocol to
         use for TMP (Transportation Management Protocol) traps. The possible
         values are:
             1 - other : not defined in this standard
             2 - snmp : use SNMPv1 Trap
             3 - sfmp : use SFMP Trap
         <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4
       "
         DEFVAL { snmp }
    ::= { trapMgmtEntry 4 }

Meaning

Descriptions

3 unique

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

Description 1

<Definition> This object identifies the application layer protocol to use for TMP (Transportation Management Protocol) traps. The possible values are: 1 - other : not defined in this standard 2 - snmp : use SNMPv1 Trap 3 - sfmp : use SFMP Trap <Superseded by> SNMP-TARGET-MIB.snmpTargetParamsMPModel (RFC 3413) <Informative> In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which points to a row in the snmpTargetParamsTable, which contains snmpTargetParamsMPModel, which indicates a message processing model (i.e., SNMPv1 vs. SNMPv3). If the NTCIP (or NEMA) community desired, it could define its own processing model (e.g., something similar to SFMP with security) and assign it a value of (1206 * 256) + id, where id is between 0 and 255 (see RFC 3411). <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 2

<Definition> This object identifies the application layer protocol to use for TMP (Transportation Management Protocol) traps. The possible values are: 1 - other : not defined in this standard 2 - snmp : use SNMPv1 Trap 3 - sfmp : use SFMP Trap <Supplanted by> SNMP-TARGET-MIB.snmpTargetParamsMPModel (RFC 3413) <Informative> In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which points to a row in the snmpTargetParamsTable, which contains snmpTargetParamsMPModel, which indicates a message processing model (i.e., SNMPv1 vs. SNMPv3). If the NTCIP (or NEMA) community desired, it could define its own processing model (e.g., something similar to SFMP with security) and assign it a value of (1206 * 256) + id, where id is between 0 and 255 (see RFC 3411). <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition> This object identifies the application layer protocol to use for TMP (Transportation Management Protocol) traps. The possible values are: 1 - other : not defined in this standard 2 - snmp : use SNMPv1 Trap 3 - sfmp : use SFMP Trap <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4

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 1ITE public NTCIP working repository MIBs1 record · 1 source

Description 1

trapMgmtApplicationProtocol · deprecatedITE public NTCIP working repository MIBs1 source

Status in source: deprecated.

Names: trapMgmtApplicationProtocol

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "trapMgmtApplicationProtocol",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "snmp",
    "(",
    "2",
    ")",
    ",",
    "sfmp",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> This object identifies the application layer protocol to use for TMP (Transportation Management Protocol) traps. The possible values are: 1 - other : not defined in this standard 2 - snmp : use SNMPv1 Trap 3 - sfmp : use SFMP Trap <Superseded by> SNMP-TARGET-MIB.snmpTargetParamsMPModel (RFC 3413) <Informative> In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which points to a row in the snmpTargetParamsTable, which contains snmpTargetParamsMPModel, which indicates a message processing model (i.e., SNMPv1 vs. SNMPv3). If the NTCIP (or NEMA) community desired, it could define its own processing model (e.g., something similar to SFMP with security) and assign it a value of (1206 * 256) + id, where id is between 0 and 255 (see RFC 3411). <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4\"",
    "DEFVAL",
    "{",
    "snmp",
    "}",
    "::=",
    "{",
    "trapMgmtEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "snmp",
            2
          ],
          [
            "sfmp",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object identifies the application layer protocol to use for TMP (Transportation Management Protocol) traps. The possible values are: 1 - other : not defined in this standard 2 - snmp : use SNMPv1 Trap 3 - sfmp : use SFMP Trap <Superseded by> SNMP-TARGET-MIB.snmpTargetParamsMPModel (RFC 3413) <Informative> In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which points to a row in the snmpTargetParamsTable, which contains snmpTargetParamsMPModel, which indicates a message processing model (i.e., SNMPv1 vs. SNMPv3). If the NTCIP (or NEMA) community desired, it could define its own processing model (e.g., something similar to SFMP with security) and assign it a value of (1206 * 256) + id, where id is between 0 and 255 (see RFC 3411). <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "snmp"
    ]
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

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

Status in source: deprecated.

Names: trapMgmtApplicationProtocol

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "trapMgmtApplicationProtocol",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "snmp",
    "(",
    "2",
    ")",
    ",",
    "sfmp",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> This object identifies the application layer protocol to use for TMP (Transportation Management Protocol) traps. The possible values are: 1 - other : not defined in this standard 2 - snmp : use SNMPv1 Trap 3 - sfmp : use SFMP Trap <Supplanted by> SNMP-TARGET-MIB.snmpTargetParamsMPModel (RFC 3413) <Informative> In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which points to a row in the snmpTargetParamsTable, which contains snmpTargetParamsMPModel, which indicates a message processing model (i.e., SNMPv1 vs. SNMPv3). If the NTCIP (or NEMA) community desired, it could define its own processing model (e.g., something similar to SFMP with security) and assign it a value of (1206 * 256) + id, where id is between 0 and 255 (see RFC 3411). <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4\"",
    "DEFVAL",
    "{",
    "snmp",
    "}",
    "::=",
    "{",
    "trapMgmtEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "snmp",
            2
          ],
          [
            "sfmp",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object identifies the application layer protocol to use for TMP (Transportation Management Protocol) traps. The possible values are: 1 - other : not defined in this standard 2 - snmp : use SNMPv1 Trap 3 - sfmp : use SFMP Trap <Supplanted by> SNMP-TARGET-MIB.snmpTargetParamsMPModel (RFC 3413) <Informative> In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which points to a row in the snmpTargetParamsTable, which contains snmpTargetParamsMPModel, which indicates a message processing model (i.e., SNMPv1 vs. SNMPv3). If the NTCIP (or NEMA) community desired, it could define its own processing model (e.g., something similar to SFMP with security) and assign it a value of (1206 * 256) + id, where id is between 0 and 255 (see RFC 3411). <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "snmp"
    ]
  ]
}
Records for description 3NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 3

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

Status in source: mandatory.

Names: trapMgmtApplicationProtocol

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "trapMgmtApplicationProtocol",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "snmp",
    "(",
    "2",
    ")",
    ",",
    "sfmp",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object identifies the application layer protocol to use for TMP (Transportation Management Protocol) traps. The possible values are: 1 - other : not defined in this standard 2 - snmp : use SNMPv1 Trap 3 - sfmp : use SFMP Trap <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4 \"",
    "DEFVAL",
    "{",
    "snmp",
    "}",
    "::=",
    "{",
    "trapMgmtEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "snmp",
            2
          ],
          [
            "sfmp",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object identifies the application layer protocol to use for TMP (Transportation Management Protocol) traps. The possible values are: 1 - other : not defined in this standard 2 - snmp : use SNMPv1 Trap 3 - sfmp : use SFMP Trap <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.6.1.4"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "snmp"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (16)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.1.4.1.6.1.1 trapMgmtManagerIndex00
1.3.6.1.4.1.1206.4.1.4.1.6.1.2 trapMgmtManagerPointer00
1.3.6.1.4.1.1206.4.1.4.1.6.1.3 trapMgmtCommunityNamePointer00
1.3.6.1.4.1.1206.4.1.4.1.6.1.5 trapMgmtTransportProtocol00
1.3.6.1.4.1.1206.4.1.4.1.6.1.6 trapMgmtPortNum00
1.3.6.1.4.1.1206.4.1.4.1.6.1.7 trapMgmtMaxRetries00
1.3.6.1.4.1.1206.4.1.4.1.6.1.8 trapMgmtRepeatInterval00
1.3.6.1.4.1.1206.4.1.4.1.6.1.9 trapMgmtDelta00
1.3.6.1.4.1.1206.4.1.4.1.6.1.10 trapMgmtQueueDepth00
1.3.6.1.4.1.1206.4.1.4.1.6.1.11 trapMgmtLinkStateStatus00
1.3.6.1.4.1.1206.4.1.4.1.6.1.12 trapMgmtAntiStreamRate00
1.3.6.1.4.1.1206.4.1.4.1.6.1.13 trapMgmtErrStatus00
1.3.6.1.4.1.1206.4.1.4.1.6.1.14 trapMgmtLostTraps00
1.3.6.1.4.1.1206.4.1.4.1.6.1.15 trapMgmtRowStatus00
1.3.6.1.4.1.1206.4.1.4.1.6.1.16 trapMgmtSeqNum00
1.3.6.1.4.1.1206.4.1.4.1.6.1.17 trapMgmtSeqNumAck00