OID reference
1.3.6.1.4.1.52642.9.20.1.2.3.2.1
The first element of the table contains the value 0, the second element the MSTID value corresponding to VID 1, the third element the MSTID value corresponding to VID 2, and so on, with the next to last element of the table containing the MSTID value corresponding to VID 4094, and the last element containing the value…
Identification
{1 3 6 1 4 1 52642 9 20 1 2 3 2 1}
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Product context
The FS.COM catalogue lists MIB packages containing this definition for these models:
A definition in a model's MIB package does not establish that the device implements it or permits access.
The displayed source records contain one distinct definition. Compare its source records.
vtssMstpConfigMstiConfigEntry OBJECT-TYPE
SYNTAX VTSSMstpConfigMstiConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The first element of the table contains the value 0, the second element
the MSTID value corresponding to VID 1, the third element the MSTID
value corresponding to VID 2, and so on, with the next to last element
of the table containing the MSTID value corresponding to VID 4094, and
the last element containing the value 0."
INDEX { vtssMstpConfigMstiConfigVid }
::= { vtssMstpConfigMstiConfigTable 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The first element of the table contains the value 0, the second element the MSTID value corresponding to VID 1, the third element the MSTID value corresponding to VID 2, and so on, with the next to last element of the table containing the MSTID value corresponding to VID 4094, and the last element containing the value 0.
FS.COM official Documentation Hub native MIB packages
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: vtssMstpConfigMstiConfigEntry
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vtssMstpConfigMstiConfigEntry",
"OBJECT-TYPE",
"SYNTAX",
"VTSSMstpConfigMstiConfigEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The first element of the table contains the value 0, the second element the MSTID value corresponding to VID 1, the third element the MSTID value corresponding to VID 2, and so on, with the next to last element of the table containing the MSTID value corresponding to VID 4094, and the last element containing the value 0.\"",
"INDEX",
"{",
"vtssMstpConfigMstiConfigVid",
"}",
"::=",
"{",
"vtssMstpConfigMstiConfigTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"VTSSMstpConfigMstiConfigEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The first element of the table contains the value 0, the second element the MSTID value corresponding to VID 1, the third element the MSTID value corresponding to VID 2, and so on, with the next to last element of the table containing the MSTID value corresponding to VID 4094, and the last element containing the value 0."
],
null,
null,
[
"INDEX",
[
[
0,
"vtssMstpConfigMstiConfigVid"
]
]
],
null
]
}Module: VTSS-MSTP-MIB
See published definition above
{'VTSS-TC': ['VTSSDisplayString', 'VTSSInterfaceIndex', 'VTSSUnsigned16', 'VTSSUnsigned8'], 'VTSS-SMI': ['vtssSwitchMgmt'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.52642.9.20.1.2.3.2.1.1 | vtssMstpConfigMstiConfigVid | 0 | 0 | |
| 1.3.6.1.4.1.52642.9.20.1.2.3.2.1.2 | vtssMstpConfigMstiConfigMstid | 0 | 0 |