OID reference
1.3.6.1.4.1.2076.150.2.3.1.1
MEP identifier of the Remote MEP which caused the cross-connect defect, 0 indicates that no remote MEP is cross-connected.
Identification
{1 3 6 1 4 1 2076 150 2 3 1 1}
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.
Published row index: fsEcfmMdIndex, fsEcfmMaIndex, fsEcfmMepIdentifier.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2076.150.2.3.1.1
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.
Available source records contain 2 distinct definitions; some records may not include a definition.
fsEcfmXconnRMepId OBJECT-TYPE
SYNTAX Unsigned32(0..8191)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"MEP identifier of the Remote MEP which caused the cross-connect
defect, 0 indicates that no remote MEP is cross-connected."
::= { fsEcfmMepExEntry 1 }fsEcfmXconnRMepId OBJECT-TYPE
SYNTAX Unsigned32(0..8191)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"MEP Identifier of the Remote MEP which caused the cross-connect
defect, 0 indicates that no remote MEP is cross-connected."
::= { fsEcfmMepExEntry 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
MEP identifier of the Remote MEP which caused the cross-connect defect, 0 indicates that no remote MEP is cross-connected.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Description 2
MEP Identifier of the Remote MEP which caused the cross-connect defect, 0 indicates that no remote MEP is cross-connected.
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: fsEcfmXconnRMepId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsEcfmXconnRMepId",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"(",
"0",
".",
".",
"8191",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"MEP identifier of the Remote MEP which caused the cross-connect defect, 0 indicates that no remote MEP is cross-connected.\"",
"::=",
"{",
"fsEcfmMepExEntry",
"1",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32",
[
"integerSubType",
[
[
0,
8191
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"MEP identifier of the Remote MEP which caused the cross-connect defect, 0 indicates that no remote MEP is cross-connected."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-ECFM-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'LLDP-MIB': ['LldpChassisId', 'LldpChassisIdSubtype'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'MacAddress', 'TDomain', 'TAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'enterprises', 'Integer32', 'Unsigned32'], 'Q-BRIDGE-MIB': ['VlanId'], 'IEEE8021-CFM-MIB': ['Dot1agCfmPortStatus', 'Dot1agCfmInterfaceStatus']}Related source files and packages:
Status in source: current.
Names: fsEcfmXconnRMepId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsEcfmXconnRMepId",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"(",
"0",
".",
".",
"8191",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"MEP Identifier of the Remote MEP which caused the cross-connect defect, 0 indicates that no remote MEP is cross-connected.\"",
"::=",
"{",
"fsEcfmMepExEntry",
"1",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32",
[
"integerSubType",
[
[
0,
8191
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"MEP Identifier of the Remote MEP which caused the cross-connect defect, 0 indicates that no remote MEP is cross-connected."
],
null,
null,
null,
null
]
}Module: ARICENT-ECFM-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'ECFM-MIB': ['Dot1agCfmPortStatus', 'Dot1agCfmInterfaceStatus'], 'LLDP-MIB': ['LldpChassisId', 'LldpChassisIdSubtype'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'MacAddress', 'TDomain', 'TAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'enterprises', 'Integer32', 'Unsigned32'], 'Q-BRIDGE-MIB': ['VlanId']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2076.150.2.3.1.2 | fsEcfmErrorRMepId | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.3 | fsEcfmMepDefectRDICcm | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.4 | fsEcfmMepDefectMacStatus | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.5 | fsEcfmMepDefectRemoteCcm | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.6 | fsEcfmMepDefectErrorCcm | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.7 | fsEcfmMepDefectXconnCcm | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.8 | fsEcfmMepCcmOffload | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.9 | fsEcfmMepLbrIn | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.10 | fsEcfmMepLbrInOutOfOrder | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.11 | fsEcfmMepLbrBadMsdu | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.12 | fsEcfmMepUnexpLtrIn | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.13 | fsEcfmMepLbrOut | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.14 | fsEcfmMepCcmSequenceErrors | 0 | 0 | |
| 1.3.6.1.4.1.2076.150.2.3.1.15 | fsEcfmMepCciSentCcms | 0 | 0 |