OID reference
1.3.6.1.4.1.1206.4.2.18.9.6.3
<Definition> This field indicates the one or more priorities of resource pool used for sidelink communication, or of a logical channel group used in case of scheduled sidelink communication resources, see TS 35.321. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.9.6.3
Identification
{1 3 6 1 4 1 1206 4 2 18 9 6 3}
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.18.9.6.3.0
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.
The displayed source records contain one distinct definition. Compare its source records.
rsuWsaLtePppp OBJECT-TYPE
SYNTAX INTEGER (1..8)
MAX-ACCESS read-only
STATUS current
DESCRIPTION "<Definition> This field indicates the one or more
priorities of resource pool used for sidelink communication, or of a
logical channel group used in case of scheduled sidelink
communication resources, see TS 35.321.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.18.9.6.3"
REFERENCE "IEEE 1609.3-2020 LTEv2xChannelInfo"
::= { rsuWsaLte 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
<Definition> This field indicates the one or more priorities of resource pool used for sidelink communication, or of a logical channel group used in case of scheduled sidelink communication resources, see TS 35.321. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.9.6.3
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: rsuWsaLtePppp
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rsuWsaLtePppp",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"1",
".",
".",
"8",
")",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> This field indicates the one or more priorities of resource pool used for sidelink communication, or of a logical channel group used in case of scheduled sidelink communication resources, see TS 35.321. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.9.6.3\"",
"REFERENCE",
"\"IEEE 1609.3-2020 LTEv2xChannelInfo\"",
"::=",
"{",
"rsuWsaLte",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
1,
8
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> This field indicates the one or more priorities of resource pool used for sidelink communication, or of a logical channel group used in case of scheduled sidelink communication resources, see TS 35.321. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.9.6.3"
],
[
"REFERENCE",
"IEEE 1609.3-2020 LTEv2xChannelInfo"
],
null,
null,
null
]
}Module: NTCIP1218-v01
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DateAndTime', 'RowStatus', 'DisplayString', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'NOTIFICATION-TYPE', 'enterprises'], 'URI-TC-MIB': ['Uri255', 'Uri1024'], 'NTCIP8004v02': ['devices', 'OerString'], 'SYSLOG-TC-MIB': ['SyslogSeverity'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}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: NTCIP8004v02. 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 NTCIP-1218-v01A-2024-AsPublished.pdf — NTCIP1218-v01 (MIB transcription)Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.18.9.6.1 | rsuWsaLteTxPoolEarfcn | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.2 | rsuWsaLtePMax | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.4 | rsuWsaLteTxPool | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.5 | rsuWsaLteMinMcs | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.6 | rsuWsaLteMaxMcs | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.7 | rsuWsaLteMinPdb | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.8 | rsuWsaLteMtu | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.9 | rsuWsaLteMaxBwPerSec | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.10 | rsuWsaLteMaxBwPerSecUnit | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.11 | rsuWsaLteMinPeriodicity | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.12 | rsuWsaLteMaxSpeed | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.13 | rsuWsaLteMaxRange | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.18.9.6.14 | rsuWsaLteMaxCbr | 0 | 0 |