Status in source: unconfirmed.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"trapMode",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> This object defines a number of different methods for handling the trap data prior to or as it is transferred to the trap channel. The trap modes are as follows: 1 - forced : NOACK, the trap is sent (not queued) regardless of the trapMgmtLinkStateStatus. 2 - ack_noQ : ACK, the trap is sent if the trapMgmtLinkStateStatus is READY; otherwise the trap is simply dropped (lost) – however, if the trap is transmitted, it is acknowledged and the retry mechanism is invoked. 3 - ack : ACK, the trap is sent if the trapMgmtLinkStateStatus is READY, otherwise the trap message shall be queued. 4 - noack_noQ : NOACK, the trap is sent if the trapMgmtLinkStateStatus is READY or PENDING; otherwise the trap is simply dropped (lost). 5 - noack : NOACK, the trap is sent if the trapMgmtLinkStateStatus is READY or PENDING; it is queued if the channel status is ERROR. 6 - ack_Aggr : ACK, the trap data (eventConfigID, timestamp, and reported data) are added to the ackTrapChain for transmission to the management station when a chain termination condition occurs and the trapMgmtLinkStateStatus is READY. ackTrapChains are not queued and are transmitted prior to any queued traps. 7 - noack_Aggr : NOACK, the trap data (eventConfigID, timestamp, and reported data) are added to the noackTrapChain for transmission to the management station when a chain termination condition occurs and the trapMgmtLinkStateStatus is READY or PENDING; otherwise the noackTrapChain grows accepting new traps. 8-255 : reserved (not used in a proprietary manner) <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.7.1.2 \"",
"REFERENCE",
"\"NTCIP 1103 v03 Sections 6.2.3 and 6.2.4\"",
"DEFVAL",
"{",
"1",
"}",
"::=",
"{",
"trapEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> This object defines a number of different methods for handling the trap data prior to or as it is transferred to the trap channel. The trap modes are as follows: 1 - forced : NOACK, the trap is sent (not queued) regardless of the trapMgmtLinkStateStatus. 2 - ack_noQ : ACK, the trap is sent if the trapMgmtLinkStateStatus is READY; otherwise the trap is simply dropped (lost) – however, if the trap is transmitted, it is acknowledged and the retry mechanism is invoked. 3 - ack : ACK, the trap is sent if the trapMgmtLinkStateStatus is READY, otherwise the trap message shall be queued. 4 - noack_noQ : NOACK, the trap is sent if the trapMgmtLinkStateStatus is READY or PENDING; otherwise the trap is simply dropped (lost). 5 - noack : NOACK, the trap is sent if the trapMgmtLinkStateStatus is READY or PENDING; it is queued if the channel status is ERROR. 6 - ack_Aggr : ACK, the trap data (eventConfigID, timestamp, and reported data) are added to the ackTrapChain for transmission to the management station when a chain termination condition occurs and the trapMgmtLinkStateStatus is READY. ackTrapChains are not queued and are transmitted prior to any queued traps. 7 - noack_Aggr : NOACK, the trap data (eventConfigID, timestamp, and reported data) are added to the noackTrapChain for transmission to the management station when a chain termination condition occurs and the trapMgmtLinkStateStatus is READY or PENDING; otherwise the noackTrapChain grows accepting new traps. 8-255 : reserved (not used in a proprietary manner) <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.7.1.2"
],
[
"REFERENCE",
"NTCIP 1103 v03 Sections 6.2.3 and 6.2.4"
],
null,
null,
[
"DEFVAL",
1
]
]
}