Status in source: deprecated.
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"
]
]
}