OID reference
1.3.6.1.4.1.5504.10.1.7.2.2.1
The compliance statement for 2BASE-TL/10PASS-TS interfaces. Compliance with the following external compliance statements is prerequisite: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 IF-INVERTED-STACK-MIB ifInvCompliance EtherLike-MIB dot3Compliance2 MAU-MIB mauModIfCompl3
Identification
{1 3 6 1 4 1 5504 10 1 7 2 2 1}
The displayed source records contain one distinct definition. Compare its source records.
efmCuCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for 2BASE-TL/10PASS-TS interfaces.
Compliance with the following external compliance statements
is prerequisite:
MIB Module Compliance Statement
---------- --------------------
IF-MIB ifCompliance3
IF-INVERTED-STACK-MIB ifInvCompliance
EtherLike-MIB dot3Compliance2
MAU-MIB mauModIfCompl3"
MODULE -- this module
MANDATORY-GROUPS {
efmCuBasicGroup,
efmCuPmeGroup,
efmCuAlarmConfGroup,
efmCuNotificationGroup
}
GROUP efmCuPme2BProfileGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting 2BASE-TL Phy."
GROUP efmCuPme10PProfileGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting 10PASS-TS Phy."
GROUP efmCuPAFGroup
DESCRIPTION
"Support for this group is only required for
implementations supporting PME Aggregation Function (PAF)."
GROUP ifStackCapabilityGroup
DESCRIPTION
"Support for this group is optional for implementations
supporting layered interfaces architecture with
flexible cross-connect between the layers."
GROUP efmCuPAFErrorsGroup
DESCRIPTION
"Support for this group is optional for implementations
supporting PME Aggregation Function (PAF)."
GROUP efmCuPme10PStatusGroup
DESCRIPTION
"Support for this group is optional for implementations
supporting 10PASS-TS Phy."
OBJECT efmCuPmeSubTypesSupported
SYNTAX BITS {
ieee2BaseTLO(0),
ieee2BaseTLR(1),
ieee10PassTSO(2),
ieee10PassTSR(3)
}
DESCRIPTION
"Support for all subtypes is not required. However at least
one value SHALL be supported"
OBJECT efmCuPmeAdminSubType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required (needed only for PMEs
supporting more than a single subtype, e.g.
ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and
ieee10PassTSR)"
OBJECT efmCuTargetWorstCaseSnrMgn
MIN-ACCESS read-only
DESCRIPTION
"Write access is optional. For PHYs without write access
the target SNR margin SHALL be fixed at 5dB for 2BASE-TL
and 6dB for 10PASS-TS."
OBJECT efmCuTargetCurrentConditionSnrMgn
MIN-ACCESS read-only
DESCRIPTION
"Write access is optional. For PHYs without write access
the target SNR margin SHALL be fixed at 5dB for 2BASE-TL
and 6dB for 10PASS-TS."
-- EdNote: To be Continued
::= { efmCuCompliances 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The compliance statement for 2BASE-TL/10PASS-TS interfaces. Compliance with the following external compliance statements is prerequisite: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 IF-INVERTED-STACK-MIB ifInvCompliance EtherLike-MIB dot3Compliance2 MAU-MIB mauModIfCompl3
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: efmCuCompliance
{
"smi_kind": "MODULE-COMPLIANCE",
"definition": [
"efmCuCompliance",
"MODULE-COMPLIANCE",
"STATUS",
"current",
"DESCRIPTION",
"\"The compliance statement for 2BASE-TL/10PASS-TS interfaces. Compliance with the following external compliance statements is prerequisite: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 IF-INVERTED-STACK-MIB ifInvCompliance EtherLike-MIB dot3Compliance2 MAU-MIB mauModIfCompl3\"",
"MODULE",
"MANDATORY-GROUPS",
"{",
"efmCuBasicGroup",
",",
"efmCuPmeGroup",
",",
"efmCuAlarmConfGroup",
",",
"efmCuNotificationGroup",
"}",
"GROUP",
"efmCuPme2BProfileGroup",
"DESCRIPTION",
"\"Support for this group is only required for implementations supporting 2BASE-TL Phy.\"",
"GROUP",
"efmCuPme10PProfileGroup",
"DESCRIPTION",
"\"Support for this group is only required for implementations supporting 10PASS-TS Phy.\"",
"GROUP",
"efmCuPAFGroup",
"DESCRIPTION",
"\"Support for this group is only required for implementations supporting PME Aggregation Function (PAF).\"",
"GROUP",
"ifStackCapabilityGroup",
"DESCRIPTION",
"\"Support for this group is optional for implementations supporting layered interfaces architecture with flexible cross-connect between the layers.\"",
"GROUP",
"efmCuPAFErrorsGroup",
"DESCRIPTION",
"\"Support for this group is optional for implementations supporting PME Aggregation Function (PAF).\"",
"GROUP",
"efmCuPme10PStatusGroup",
"DESCRIPTION",
"\"Support for this group is optional for implementations supporting 10PASS-TS Phy.\"",
"OBJECT",
"efmCuPmeSubTypesSupported",
"SYNTAX",
"BITS",
"{",
"ieee2BaseTLO",
"(",
"0",
")",
",",
"ieee2BaseTLR",
"(",
"1",
")",
",",
"ieee10PassTSO",
"(",
"2",
")",
",",
"ieee10PassTSR",
"(",
"3",
")",
"}",
"DESCRIPTION",
"\"Support for all subtypes is not required. However at least one value SHALL be supported\"",
"OBJECT",
"efmCuPmeAdminSubType",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"Write access is not required (needed only for PMEs supporting more than a single subtype, e.g. ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and ieee10PassTSR)\"",
"OBJECT",
"efmCuTargetWorstCaseSnrMgn",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"Write access is optional. For PHYs without write access the target SNR margin SHALL be fixed at 5dB for 2BASE-TL and 6dB for 10PASS-TS.\"",
"OBJECT",
"efmCuTargetCurrentConditionSnrMgn",
"MIN-ACCESS",
"read-only",
"DESCRIPTION",
"\"Write access is optional. For PHYs without write access the target SNR margin SHALL be fixed at 5dB for 2BASE-TL and 6dB for 10PASS-TS.\"",
"::=",
"{",
"efmCuCompliances",
"1",
"}"
],
"syntax_tree": [
[
"Status",
"current"
],
[
"DESCRIPTION",
"The compliance statement for 2BASE-TL/10PASS-TS interfaces. Compliance with the following external compliance statements is prerequisite: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 IF-INVERTED-STACK-MIB ifInvCompliance EtherLike-MIB dot3Compliance2 MAU-MIB mauModIfCompl3"
],
null,
[
"ComplianceModules",
[
[
null,
[
"efmCuBasicGroup",
"efmCuPmeGroup",
"efmCuAlarmConfGroup",
"efmCuNotificationGroup",
"efmCuPme2BProfileGroup",
"efmCuPme10PProfileGroup",
"efmCuPAFGroup",
"ifStackCapabilityGroup",
"efmCuPAFErrorsGroup",
"efmCuPme10PStatusGroup"
]
]
]
]
]
}Vendor MIB copy from the Observium Community archive.
Module: EFM-CU-MIB
See published definition above
{'Zhone': ['ietfDrafts'], 'IF-MIB': ['ifIndex', 'ifSpeed', 'InterfaceIndex'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'PhysAddress', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'TimeTicks', 'mib-2'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}Related source files and packages:
Registration