OID reference
1.3.6.1.4.1.1206.4.2.4.1.5.1.16
<Definition> Time period in seconds for the sensor zone during which, if there is constant activity for the zone, a Max Presence status is generated for the zone. A max presence fault time of zero (0) means that a max presence status cannot be generated for this sensor zone. <Unit> second <Object Identifier> 1.3.6.1.4…
Identification
{1 3 6 1 4 1 1206 4 2 4 1 5 1 16}
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 NTCIP1209v02-MIB1, the row index sensorZoneNumber is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1206.4.2.4.1.5.1.16.<sensorZoneNumber>. 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.2.4.1.5.1.16
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 2 distinct definitions; some records may not include a definition.
sensorZoneMaxPresenceFaultTime OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"<Definition> Time period in seconds for the sensor zone during which, if there is constant activity for the zone, a Max Presence status is generated for the zone. A max presence fault time of zero (0) means that a max presence status cannot be generated for this sensor zone.
<Unit> second
<Object Identifier> 1.3.6.1.4.1.1206.4.2.4.1.5.1.16"
DEFVAL { 0 }
::= { sensorZoneEntry 16 }sensorZoneMaxPresenceFaultTime OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"<Definition> Time period in seconds for the sensor zone during which, if
there is constant activity for the zone, a Max Presence status is generated
for the zone. A max presence fault time of zero (0) means that a max presence
status cannot be generated for this sensor zone.
<Unit> second
<Object Identifier> 1.3.6.1.4.1.1206.4.2.4.1.5.1.16"
DEFVAL { 0 }
::= { sensorZoneEntry 16 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
<Definition> Time period in seconds for the sensor zone during which, if there is constant activity for the zone, a Max Presence status is generated for the zone. A max presence fault time of zero (0) means that a max presence status cannot be generated for this sensor zone. <Unit> second <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.1.5.1.16
ITE public NTCIP working repository MIBsNTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: sensorZoneMaxPresenceFaultTime
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sensorZoneMaxPresenceFaultTime",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"65535",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Time period in seconds for the sensor zone during which, if there is constant activity for the zone, a Max Presence status is generated for the zone. A max presence fault time of zero (0) means that a max presence status cannot be generated for this sensor zone. <Unit> second <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.1.5.1.16\"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"sensorZoneEntry",
"16",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Time period in seconds for the sensor zone during which, if there is constant activity for the zone, a Max Presence status is generated for the zone. A max presence fault time of zero (0) means that a max presence status cannot be generated for this sensor zone. <Unit> second <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.1.5.1.16"
],
null,
null,
null,
[
"DEFVAL",
0
]
]
}Module: NTCIP1209v02-MIB1
See published definition above
{'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.mibRelated source files and packages:
Module: NTCIP1209v02-MIB1
See published definition above
Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of tss. These exact source files require the reviewed bindings shown below. 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 NTCIP1209v0218jp.pdf — NTCIP1209v02-MIB1 (MIB transcription)Registration