Status in source: mandatory.
Names: sectionAddress
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sectionAddress",
"OBJECT-TYPE",
"SYNTAX",
"IpAddress",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\" <Definition> Indicates the IP Address used to reference the group of SSLs assigned to the associated section number. The IpAddress for a section shall take the form of a broadcast address. NTCIP 1210 v01 does not constrain uniqueness of broadcast IP addresses among sections. Individual sections configured to share a common IP broadcast do not support individualized section level control through broadcast commands from the SSM. IP broadcasted commands to any one section are accepted by all sections having the same broadcast IP. Alternatively, unique programming of broadcast IP for each section imposes constraint on the network design. This uniqueness requires all SSLs within a section to be networked on a single subnet, common to their section, and unique from subnets of other sections. <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.1.2.1.2\"",
"DEFVAL",
"{",
"'",
"00000000",
"'",
"h",
"}",
"::=",
"{",
"sectionSetupEntry",
"2",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"IpAddress",
null
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Indicates the IP Address used to reference the group of SSLs assigned to the associated section number. The IpAddress for a section shall take the form of a broadcast address. NTCIP 1210 v01 does not constrain uniqueness of broadcast IP addresses among sections. Individual sections configured to share a common IP broadcast do not support individualized section level control through broadcast commands from the SSM. IP broadcasted commands to any one section are accepted by all sections having the same broadcast IP. Alternatively, unique programming of broadcast IP for each section imposes constraint on the network design. This uniqueness requires all SSLs within a section to be networked on a single subnet, common to their section, and unique from subnets of other sections. <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.1.2.1.2"
],
null,
null,
null,
[
"DEFVAL",
"'00000000'h"
]
]
}
- 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