Status in source: mandatory.
Names: ssmBlockGetControl
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ssmBlockGetControl",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"2",
".",
".",
"16",
")",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\" <Definition> An OER encoded string of reference parameters for SSM Block Uploads. The parameter values in this string are: ssmBlockDataType INTEGER (0..255) ssmBlockDataID INTEGER (0..255) ssmBlockIndex1 INTEGER (0..255) if needed ssmBlockQuantity1 INTEGER (0..255) if needed ssmBlockIndex2 INTEGER (0..255) if needed ssmBlockQuantity2 INTEGER (0..255) if needed ssmBlockIndex3 INTEGER (0..255) if needed ssmBlockQuantity3 INTEGER (0..255) if needed ssmBlockIndex4 INTEGER (0..255) if needed ssmBlockQuantity4 INTEGER (0..255) if needed ssmBlockIndex5 INTEGER (0..255) if needed ssmBlockQuantity5 INTEGER (0..255) if needed A GET of ssmBlockData shall use values currently in this object to define the data to be returned. A SET of this object shall be evaluated for validity and Error Status of badValue(3) be returned for the following conditions: 1) ssmBlockDataType is not supported 2) ssmBlockDataID is not supported 3) ssmBlockIndex1 is zero or not supported 4) ssmBlockQuantity1 is zero or ssmBlockIndex1 + ssmBlockQuantity1 - 1 is not supported 5) ssmBlockIndex2 is zero or not supported 6) ssmBlockQuantity2 is zero or ssmBlockIndex2 + ssmBlockQuantity2) - 1 is not supported 7) ssmBlockIndex3 is zero or not supported 8) ssmBlockQuantity3 is zero or ssmBlockIndex3 + ssmBlockQuantity3 - 1 is not supported 9) ssmBlockIndex4 is zero or not supported 10) ssmBlockQuantity4 is zero or ssmBlockIndex4 + ssmBlockQuantity4) - 1 is not supported 11) ascBlockIndex5 is zero or not supported 12) ascBlockQuantity5 is zero or ascBlockIndex5 + ascBlockQuantity5) - 1 is not supported 13) if the SET length is zero or incorrect for ssmBlockDataType & ssmBlockDataID 14) if the GetResponse length for a GET on ssmBlockData using maximum data field sizes would exceed a local limitation When this validity check fails, ssmBlockErrorStatus shall be set equal to the Bullet Value (1..14) above that generated the error. <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.26.1\"",
"::=",
"{",
"ssmBlockObjects",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
2,
16
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> An OER encoded string of reference parameters for SSM Block Uploads. The parameter values in this string are: ssmBlockDataType INTEGER (0..255) ssmBlockDataID INTEGER (0..255) ssmBlockIndex1 INTEGER (0..255) if needed ssmBlockQuantity1 INTEGER (0..255) if needed ssmBlockIndex2 INTEGER (0..255) if needed ssmBlockQuantity2 INTEGER (0..255) if needed ssmBlockIndex3 INTEGER (0..255) if needed ssmBlockQuantity3 INTEGER (0..255) if needed ssmBlockIndex4 INTEGER (0..255) if needed ssmBlockQuantity4 INTEGER (0..255) if needed ssmBlockIndex5 INTEGER (0..255) if needed ssmBlockQuantity5 INTEGER (0..255) if needed A GET of ssmBlockData shall use values currently in this object to define the data to be returned. A SET of this object shall be evaluated for validity and Error Status of badValue(3) be returned for the following conditions: 1) ssmBlockDataType is not supported 2) ssmBlockDataID is not supported 3) ssmBlockIndex1 is zero or not supported 4) ssmBlockQuantity1 is zero or ssmBlockIndex1 + ssmBlockQuantity1 - 1 is not supported 5) ssmBlockIndex2 is zero or not supported 6) ssmBlockQuantity2 is zero or ssmBlockIndex2 + ssmBlockQuantity2) - 1 is not supported 7) ssmBlockIndex3 is zero or not supported 8) ssmBlockQuantity3 is zero or ssmBlockIndex3 + ssmBlockQuantity3 - 1 is not supported 9) ssmBlockIndex4 is zero or not supported 10) ssmBlockQuantity4 is zero or ssmBlockIndex4 + ssmBlockQuantity4) - 1 is not supported 11) ascBlockIndex5 is zero or not supported 12) ascBlockQuantity5 is zero or ascBlockIndex5 + ascBlockQuantity5) - 1 is not supported 13) if the SET length is zero or incorrect for ssmBlockDataType & ssmBlockDataID 14) if the GetResponse length for a GET on ssmBlockData using maximum data field sizes would exceed a local limitation When this validity check fails, ssmBlockErrorStatus shall be set equal to the Bullet Value (1..14) above that generated the error. <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.26.1"
],
null,
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