Status in source: mandatory.
Names: sensorZoneErraticCountsThreshold
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sensorZoneErraticCountsThreshold",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"65535",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> The counts that if a sensor zone?s number of actuations meets or exceeds within the Erratic Counts Fault Time an Erratic Counts status is generated for the zone. An erratic counts threshold of zero (0) means that an erratic counts status cannot be generated for this sensor zone. <Unit> count <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.1.5.1.18\"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"sensorZoneEntry",
"18",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> The counts that if a sensor zone?s number of actuations meets or exceeds within the Erratic Counts Fault Time an Erratic Counts status is generated for the zone. An erratic counts threshold of zero (0) means that an erratic counts status cannot be generated for this sensor zone. <Unit> count <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.1.5.1.18"
],
null,
null,
null,
[
"DEFVAL",
0
]
]
}
- ITE public NTCIP working repository MIBs
· Publisher's source file: NTCIP-1209 — ntcip1209-Tss.mib
Module: NTCIP1209v02-MIB1
See published definition above
Module imports
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-2008': ['OwnerString', 'BITMAP8', 'BITMAP16', 'BITMAP32', 'tss']}
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.
Source data warning: Potentially inaccurate interpretation of historical NTCIP imports: the original references NTCIP8004-2008, which is absent from the public repository snapshot. 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 NTCIP-1209 — ntcip1209-Tss.mib