Status in source: deprecated.
Names: trapData
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"trapData",
"OBJECT-TYPE",
"SYNTAX",
"ITSOerString",
"MAX-ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition> It contains an octet string (event notification) with octet trap sequence number (trapMgmtSeqNum)and octet trap manager index (trapMgmtManagerIndex), followed by one or more OER encoded sequences of ventide (eventConfigID), eventTime (globalTime of the occurrence of the event), eventLogTimeMilliseconds (fractional second of the occurrence of the event), and reported data (as pointed to by eventConfigLogOID). For aggregated trap messages (ackTrapChain and noackTrapChain) the trapData contains the octet trap sequence number (trapMgmtSeqNum) and octet trap manager index (trapMgmtManagerIndex), followed by from 1 to trapMaxAggregationSize triplets. The sequence to which OER encoding is applied is formally defined by the TrapDataStructure (see Section 6.4.1). <Superseded by> NOTIFICATION-MIB.fdNotificationData (ISO 20684-4) <Informative> The original syntax for this object was OerString as defined in NTCIP 8004 v02. NTCIP 8004 v03 recommends the use of ITSOerString in SMIv2 modules as it is formally defined as a textual convention in ISO 20684-1. Both OerString and ITSOerString resolve to OCTET STRING, so while the written syntax has changed, there is no impact on how it is encoded. The replacement object switches the order of the initial index and sequence number. It also uses a ITSDailyTimeStamp, which indicates time of day to the millisecond. It also includes a latency of the data and each data field is presented as a CHOICE of either the data value or the PDU error that the get operation generated. <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.2\"",
"::=",
"{",
"trapMgmt",
"2",
"}"
],
"syntax_tree": [
[
"row",
"ITSOerString"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition> It contains an octet string (event notification) with octet trap sequence number (trapMgmtSeqNum)and octet trap manager index (trapMgmtManagerIndex), followed by one or more OER encoded sequences of ventide (eventConfigID), eventTime (globalTime of the occurrence of the event), eventLogTimeMilliseconds (fractional second of the occurrence of the event), and reported data (as pointed to by eventConfigLogOID). For aggregated trap messages (ackTrapChain and noackTrapChain) the trapData contains the octet trap sequence number (trapMgmtSeqNum) and octet trap manager index (trapMgmtManagerIndex), followed by from 1 to trapMaxAggregationSize triplets. The sequence to which OER encoding is applied is formally defined by the TrapDataStructure (see Section 6.4.1). <Superseded by> NOTIFICATION-MIB.fdNotificationData (ISO 20684-4) <Informative> The original syntax for this object was OerString as defined in NTCIP 8004 v02. NTCIP 8004 v03 recommends the use of ITSOerString in SMIv2 modules as it is formally defined as a textual convention in ISO 20684-1. Both OerString and ITSOerString resolve to OCTET STRING, so while the written syntax has changed, there is no impact on how it is encoded. The replacement object switches the order of the initial index and sequence number. It also uses a ITSDailyTimeStamp, which indicates time of day to the millisecond. It also includes a latency of the data and each data field is presented as a CHOICE of either the data value or the PDU error that the get operation generated. <Object Identifier> 1.3.6.1.4.1.1206.4.1.4.1.2"
],
null,
null,
null,
null
]
}
- ITE public NTCIP working repository MIBs
· Publisher's source file: NTCIP-1201 — ntcip1201-AuxIO.mib
Module: NTCIP1201-NtcipTraps
See published definition above
Module imports
{'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'IpAddress', 'zeroDotZero'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'NTCIP1201-Report': ['eventConfigID'], 'FIELD-DEVICE-TC-MIB': ['ITSOerString'], 'NTCIP8004-Transportation': ['application', 'protocols', 'NtcipRowStatusStatic']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
· Download NTCIP-1201 — ntcip1201-AuxIO.mib
Same file in ntcip1201-SNMPConfig.mib.
Same file in ntcip1201-Security.mib.
Same file in ntcip1201-ProfilesSTMP.mib.
Same file in ntcip1201-NtcipTraps.mib.