OID reference
1.3.6.1.4.1.29601.2.86.2.1.2
Compliance requirement for implementations that only provide read-only support for VPLS-BGP-MIB. Such devices can then be monitored but cannot be configured using this MIB modules.
Identification
{1 3 6 1 4 1 29601 2 86 2 1 2}
The displayed source records contain one distinct definition. Compare its source records.
vplsBgpModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance requirement for implementations that only
provide read-only support for VPLS-BGP-MIB.
Such devices can then be monitored but cannot be
configured using this MIB modules."
MODULE -- this module
MANDATORY-GROUPS {
vplsBgpConfigGroup,
vplsBgpVEGroup,
vplsBgpPwBindGroup
}
OBJECT vplsBgpConfigVERangeSize
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT vplsBgpVEName
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT vplsBgpVEPreference
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT vplsBgpVERowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { vplsBgpCompliances 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Compliance requirement for implementations that only provide read-only support for VPLS-BGP-MIB. Such devices can then be monitored but cannot be configured using this MIB modules.
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: vplsBgpModuleReadOnlyCompliance
{
"smi_kind": "MODULE-COMPLIANCE",
"definition": [
"vplsBgpModuleReadOnlyCompliance",
"MODULE-COMPLIANCE",
"STATUS",
"current",
"DESCRIPTION",
"\"Compliance requirement for implementations that only provide read-only support for VPLS-BGP-MIB. Such devices can then be monitored but cannot be configured using this MIB modules.\"",
"MODULE",
"MANDATORY-GROUPS",
"{",
"vplsBgpConfigGroup",
",",
"vplsBgpVEGroup",
",",
"vplsBgpPwBindGroup",
"}",
"OBJECT",
"vplsBgpConfigVERangeSize",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"Write access is not required.\"",
"OBJECT",
"vplsBgpVEName",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"Write access is not required.\"",
"OBJECT",
"vplsBgpVEPreference",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"Write access is not required.\"",
"OBJECT",
"vplsBgpVERowStatus",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"Write access is not required.\"",
"::=",
"{",
"vplsBgpCompliances",
"2",
"}"
],
"syntax_tree": [
[
"Status",
"current"
],
[
"DESCRIPTION",
"Compliance requirement for implementations that only provide read-only support for VPLS-BGP-MIB. Such devices can then be monitored but cannot be configured using this MIB modules."
],
null,
[
"ComplianceModules",
[
[
null,
[
"vplsBgpConfigGroup",
"vplsBgpVEGroup",
"vplsBgpPwBindGroup"
]
]
]
]
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-VPLS-BGP-MIB
See published definition above
{'SNMPv2-TC': ['RowStatus', 'StorageType'], 'PW-STD-MIB': ['pwIndex'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'enterprises', 'Unsigned32', 'transmission'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'VPLS-GENERIC-MIB': ['vplsConfigIndex'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.29601.2.86.2.1.1 | vplsBgpModuleFullCompliance | 0 | 0 |