Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dcmOFMRelation",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"and",
"(",
"1",
")",
",",
"or",
"(",
"2",
")",
",",
"endOfDef",
"(",
"3",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Indicates how multiple filters can be related together to trigger the specified logical output. It is up to the application to ensure that the rows are populated in the correct sequence to achieve the desired Boolean relationship. The Boolean relationships are processed in an ascending order as specified by the second index within each logical output. If 3 rows were defined (1-1-and, 1-2-or, 1-3-end) the result would be that logical output 1 is triggered if ((filter 1 and filter 2) or filter 3)=True. The currently defined values are: and (1) – This defines a Boolean ‘and’ operation between the filter specified in this row and the filter defined in the next row for the same logical output as determined by the second index of this table. The logical output shall not be triggered unless both filters are true. or (2) – This defines a Boolean ‘or’ operation between the filter specified in this row and the filter defined in the next row for the same logical output as determined by the second index of this table. The logical output shall not be triggered unless either one of the filters are true. endOfDef (3) – Indicates that this row is the end of the definition for the criteria required to trigger the specified logical output. If only one mapping is used per output (this row), the value of this object shall be set to endOfDef. In opposite to the common setup of SNMP MIB objects, this object was purposely setup to NOT include a value of (other).\"",
"::=",
"{",
"dcmOFMEntry",
"6",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"and",
1
],
[
"or",
2
],
[
"endOfDef",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Indicates how multiple filters can be related together to trigger the specified logical output. It is up to the application to ensure that the rows are populated in the correct sequence to achieve the desired Boolean relationship. The Boolean relationships are processed in an ascending order as specified by the second index within each logical output. If 3 rows were defined (1-1-and, 1-2-or, 1-3-end) the result would be that logical output 1 is triggered if ((filter 1 and filter 2) or filter 3)=True. The currently defined values are: and (1) – This defines a Boolean ‘and’ operation between the filter specified in this row and the filter defined in the next row for the same logical output as determined by the second index of this table. The logical output shall not be triggered unless both filters are true. or (2) – This defines a Boolean ‘or’ operation between the filter specified in this row and the filter defined in the next row for the same logical output as determined by the second index of this table. The logical output shall not be triggered unless either one of the filters are true. endOfDef (3) – Indicates that this row is the end of the definition for the criteria required to trigger the specified logical output. If only one mapping is used per output (this row), the value of this object shall be set to endOfDef. In opposite to the common setup of SNMP MIB objects, this object was purposely setup to NOT include a value of (other)."
],
null,
null,
null,
null
]
}
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1206:2005, Object Definitions for Data Collection and Monitoring (DCM) Devices Published November 2005 — original PDF
· Official record
Module: DCM-MIB1
See published definition above
Module imports
{'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}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: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.
Source data warning: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB-II. 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 NTCIP1206v0123f.pdf — DCM-MIB1 (MIB transcription)
Related source files and packages:
Show more related files and packages
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1206:2005, Object Definitions for Daqta Collection and Monitoring (DCM) Devices Published November 2005 (superceded by NTCIP 1206 v02) — original PDF
· Official record
Module: DCM-MIB1
Same published definition
Module imports
{'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}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: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.
Source data warning: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB-II. 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 NTCIP1206v0123f-1.pdf — DCM-MIB1 (MIB transcription)
Related source files and packages: