OID reference
1.3.6.1.4.1.29601.2.1.2.1.1
Each entry contains 'Access Loop Identification' information for port or port and VLAN. When VLAN-ID is configured as '0' the configurations are applicable for port and all the VLANs on that port. When VLAN-ID is configured as a valid value, then the configuration is applicable for the port and particular VLAN-ID on t…
Identification
{1 3 6 1 4 1 29601 2 1 2 1 1}
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.
fsDcsPortCtrlEntry OBJECT-TYPE
SYNTAX FsDcsPortCtrlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry contains 'Access Loop Identification' information for port or port and VLAN.
When VLAN-ID is configured as '0' the configurations are applicable for port and all the VLANs on that port.
When VLAN-ID is configured as a valid value, then the configuration is applicable for the port and particular VLAN-ID on that port."
INDEX { fsDcsPortCtrlIndex, fsDcsPortCtrlVlanId }
::= { fsDcsPortCtrlTable 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Each entry contains 'Access Loop Identification' information for port or port and VLAN. When VLAN-ID is configured as '0' the configurations are applicable for port and all the VLANs on that port. When VLAN-ID is configured as a valid value, then the configuration is applicable for the port and particular VLAN-ID on that port.
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: fsDcsPortCtrlEntry
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsDcsPortCtrlEntry",
"OBJECT-TYPE",
"SYNTAX",
"FsDcsPortCtrlEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"Each entry contains 'Access Loop Identification' information for port or port and VLAN. When VLAN-ID is configured as '0' the configurations are applicable for port and all the VLANs on that port. When VLAN-ID is configured as a valid value, then the configuration is applicable for the port and particular VLAN-ID on that port.\"",
"INDEX",
"{",
"fsDcsPortCtrlIndex",
",",
"fsDcsPortCtrlVlanId",
"}",
"::=",
"{",
"fsDcsPortCtrlTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"FsDcsPortCtrlEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Each entry contains 'Access Loop Identification' information for port or port and VLAN. When VLAN-ID is configured as '0' the configurations are applicable for port and all the VLANs on that port. When VLAN-ID is configured as a valid value, then the configuration is applicable for the port and particular VLAN-ID on that port."
],
null,
null,
[
"INDEX",
[
[
0,
"fsDcsPortCtrlIndex"
],
[
0,
"fsDcsPortCtrlVlanId"
]
]
],
null
]
}Vendor MIB copy from the Observium Community archive.
Module: AricentDCS-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['DisplayString', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'enterprises']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.29601.2.1.2.1.1.1 | fsDcsPortCtrlIndex | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.1.2.1.1.2 | fsDcsPortCtrlVlanId | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.1.2.1.1.3 | fsDcsPortCtrlRemoteAgentIdentifier | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.1.2.1.1.4 | fsDcsPortCtrlRemoteAgentIDStatus | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.1.2.1.1.5 | fsDcsPortCtrlAccessLoopStatus | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.1.2.1.1.6 | fsDcsPortCtrlAgentCircuitID | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.1.2.1.1.7 | fsDcsPortCtrlVlanRowStatus | 0 | 0 |