Whether or not to use VLAN tagging for management.
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.17713.250.1.17
Whether or not to use VLAN tagging for management.
Identification
{1 3 6 1 4 1 17713 250 1 17}
| Value | Name |
|---|---|
| 0 | disabled |
| 1 | enabled |
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.17713.250.1.17.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.
vlanTagging OBJECT-TYPE
SYNTAX INTEGER {
disabled(0),
enabled(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Whether or not to use VLAN tagging for management."
::= { configuration 17 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Whether or not to use VLAN tagging for management.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: vlanTagging
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vlanTagging",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"disabled",
"(",
"0",
")",
",",
"enabled",
"(",
"1",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Whether or not to use VLAN tagging for management.\"",
"::=",
"{",
"configuration",
"17",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"disabled",
0
],
[
"enabled",
1
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Whether or not to use VLAN tagging for management."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: CAMBIUM-PTP250-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'IpAddress', 'enterprises'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}Related source files and packages:
Same file in Observium Community.
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.17713.250.1.1 | iPAddress | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.2 | subnetMask | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.3 | gatewayIPAddress | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.4 | remoteMACAddress | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.5 | masterSlaveMode | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.6 | maximumTransmitPower | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.7 | antennaGain | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.8 | cableLoss | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.9 | channelBandwidth | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.10 | remoteIPAddress | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.11 | linkName | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.12 | siteName | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.13 | configuredModulationMode | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.14 | band | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.15 | configuredRange | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.16 | channelSelection | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.18 | vlanId | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.19 | vlanPriority | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.22 | fixedModMode | 0 | 0 | |
| 1.3.6.1.4.1.17713.250.1.23 | dualPayload | 0 | 0 |