Status in source: mandatory.
Names: tmpMsgConfigStatus
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"tmpMsgConfigStatus",
"OBJECT-TYPE",
"SYNTAX",
"ConfigEntryStatus",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\" <Definition> Indicates the state of the associated TMP message definition. Depending on any validity checks that are performed on the TMP message definition, a set request on this object may or may not be honored. The states are defined as: valid (1), underCreation (2), invalid (3) Note - The rules associated with accessing the tmpMsgSetupTable are defined in NTCIP 1103 v02. <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.6.1.1.2\"",
"REFERENCE",
"\" NTCIP 1103 v02 - Section 5.2.4.1 \"",
"::=",
"{",
"tmpMsgConfigEntry",
"2",
"}"
],
"syntax_tree": [
[
"row",
"ConfigEntryStatus"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Indicates the state of the associated TMP message definition. Depending on any validity checks that are performed on the TMP message definition, a set request on this object may or may not be honored. The states are defined as: valid (1), underCreation (2), invalid (3) Note - The rules associated with accessing the tmpMsgSetupTable are defined in NTCIP 1103 v02. <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.6.1.1.2"
],
[
"REFERENCE",
"NTCIP 1103 v02 - Section 5.2.4.1"
],
null,
null,
null
]
}
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1210 v01, Field Master Stations (FMS)—Part 1: Object Definitions for Signal System Masters (SSM) Published September 2013 — original PDF
· Official record
Module: NTCIP1210v01-51
See published definition above
Module imports
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'null', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004v0217-SMI': ['OwnerString', 'BITMAP8', 'BITMAP16', 'ssm'], 'NTCIP1103v0217-STMP': ['ConfigEntryStatus']}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 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: NTCIP8004v0217-SMI. 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 NTCIP1210v0155r.pdf — NTCIP1210v01-51 (MIB transcription)
Related source files and packages:
Show more related files and packages