OID reference
1.3.6.1.4.1.2076.13.6.2.2.1
The compliance statement for agents that provide full support for PW-MPLS MIB Module. Such devices can then be monitored and also be configured using this MIB module.
Identification
{1 3 6 1 4 1 2076 13 6 2 2 1}
The displayed source records contain one distinct definition. Compare its source records.
pwMplsModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for agents that provide full
support for PW-MPLS MIB Module. Such devices can
then be monitored and also be configured using
this MIB module."
MODULE -- this module
MANDATORY-GROUPS { pwMplsGroup,
pwMplsOutboundMainGroup,
pwMplsInboundGroup,
pwMplsMappingGroup
}
GROUP pwMplsOutboundTeGroup
DESCRIPTION "This group MUST be supported if the implementation
allows MPLS TE tunnels to carry PW traffic.
"
OBJECT pwMplsMplsType
DESCRIPTION "Support of pwOnly(2) is not required. At least one
of mplsTe(0) or mplsNonTe(1) MUST be supported if
signaling of PW is supported.
"
OBJECT pwMplsExpBitsMode
DESCRIPTION "Support of specifiedValue(2) and
serviceDependant(3) is optional.
"
OBJECT pwMplsLocalLdpID
MIN-ACCESS read-only
DESCRIPTION "A read-write access is required if the
implementation supports more than one LDP entity
identifier for PW signaling.
"
OBJECT pwMplsLocalLdpEntityID
MIN-ACCESS read-only
DESCRIPTION "A read-write access is required if the
implementation supports more than one LDP entity
index for PW signaling.
"
OBJECT pwMplsOutboundLsrXcIndex
MIN-ACCESS read-only
DESCRIPTION "A value other than zero MUST be supported if the
implementation support non TE signaling of the
outer tunnel.
A read-write access MUST be supported if the
implementation supports manually setting of the PW
labels and carrying them over non-TE tunnels.
"
OBJECT pwMplsOutboundIfIndex
MIN-ACCESS read-only
DESCRIPTION "A value other than zero and read-write operations
MUST be supported if the implementation supports
manully configured PW without MPLS outer tunnel.
"
::= { pwMplsCompliances 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The compliance statement for agents that provide full support for PW-MPLS MIB Module. Such devices can then be monitored and also be configured using this MIB module.
Belden, GarrettCom and Hirschmann IT official standalone MIBs
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: pwMplsModuleFullCompliance
{
"smi_kind": "MODULE-COMPLIANCE",
"definition": [
"pwMplsModuleFullCompliance",
"MODULE-COMPLIANCE",
"STATUS",
"current",
"DESCRIPTION",
"\"The compliance statement for agents that provide full support for PW-MPLS MIB Module. Such devices can then be monitored and also be configured using this MIB module.\"",
"MODULE",
"MANDATORY-GROUPS",
"{",
"pwMplsGroup",
",",
"pwMplsOutboundMainGroup",
",",
"pwMplsInboundGroup",
",",
"pwMplsMappingGroup",
"}",
"GROUP",
"pwMplsOutboundTeGroup",
"DESCRIPTION",
"\"This group MUST be supported if the implementation allows MPLS TE tunnels to carry PW traffic. \"",
"OBJECT",
"pwMplsMplsType",
"DESCRIPTION",
"\"Support of pwOnly(2) is not required. At least one of mplsTe(0) or mplsNonTe(1) MUST be supported if signaling of PW is supported. \"",
"OBJECT",
"pwMplsExpBitsMode",
"DESCRIPTION",
"\"Support of specifiedValue(2) and serviceDependant(3) is optional. \"",
"OBJECT",
"pwMplsLocalLdpID",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"A read-write access is required if the implementation supports more than one LDP entity identifier for PW signaling. \"",
"OBJECT",
"pwMplsLocalLdpEntityID",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"A read-write access is required if the implementation supports more than one LDP entity index for PW signaling. \"",
"OBJECT",
"pwMplsOutboundLsrXcIndex",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"A value other than zero MUST be supported if the implementation support non TE signaling of the outer tunnel. A read-write access MUST be supported if the implementation supports manually setting of the PW labels and carrying them over non-TE tunnels. \"",
"OBJECT",
"pwMplsOutboundIfIndex",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"A value other than zero and read-write operations MUST be supported if the implementation supports manully configured PW without MPLS outer tunnel. \"",
"::=",
"{",
"pwMplsCompliances",
"1",
"}"
],
"syntax_tree": [
[
"Status",
"current"
],
[
"DESCRIPTION",
"The compliance statement for agents that provide full support for PW-MPLS MIB Module. Such devices can then be monitored and also be configured using this MIB module."
],
null,
[
"ComplianceModules",
[
[
null,
[
"pwMplsGroup",
"pwMplsOutboundMainGroup",
"pwMplsInboundGroup",
"pwMplsMappingGroup",
"pwMplsOutboundTeGroup"
]
]
]
]
]
}Module: PW-MPLS-STD-MIB
See published definition above
{'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['StorageType'], 'PW-STD-MIB': ['pwIndex'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'transmission', 'enterprises'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'PW-TC-STD-MIB': ['PwIndexType'], 'MPLS-TC-STD-MIB': ['MplsTunnelIndex', 'MplsTunnelInstanceIndex', 'MplsLdpIdentifier', 'MplsLsrIdentifier'], 'MPLS-LSR-STD-MIB': ['MplsIndexType']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2076.13.6.2.2.2 | pwMplsModuleReadOnlyCompliance | 0 | 0 |