Status in source: current.
Names: fsMIEcfmMepExTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsMIEcfmMepExTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"FsMIEcfmMepExEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The Maintenance Association End Point (MEP) table. Each row in the table represents a different MEP. A MEP is an actively managed CFM entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM PDUs and track any responses. It is an end point of a single Maintenance Association, and is an endpoint of a separate Maintenance Entity for each of the other MEPs in the same Maintenance Association (802.1ag clause 3.18). This table uses three indices. The first two indices are the indices of the Maintenance Domain and MA tables, the reason being that a MEP is always related to an MA and Maintenance Domain.\"",
"::=",
"{",
"fsMIEcfmContext",
"13",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"FsMIEcfmMepExEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The Maintenance Association End Point (MEP) table. Each row in the table represents a different MEP. A MEP is an actively managed CFM entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM PDUs and track any responses. It is an end point of a single Maintenance Association, and is an endpoint of a separate Maintenance Entity for each of the other MEPs in the same Maintenance Association (802.1ag clause 3.18). This table uses three indices. The first two indices are the indices of the Maintenance Domain and MA tables, the reason being that a MEP is always related to an MA and Maintenance Domain."
],
null,
null,
null,
null
]
}
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: ARICENT-ECFM-MI-MIB
See published definition above
Module imports
{'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'LLDP-MIB': ['LldpChassisId', 'LldpChassisIdSubtype', 'LldpPortId', 'LldpPortIdSubtype'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TimeInterval', 'TimeStamp', 'RowStatus', 'TruthValue', 'MacAddress', 'TDomain', 'TAddress', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'enterprises', 'Integer32', 'Unsigned32'], 'Q-BRIDGE-MIB': ['VlanIdOrNone', 'VlanId']}
Related source files and packages:
- Belden, GarrettCom and Hirschmann IT official standalone MIBs
· Publisher's source file: fscfmmi.mib
Module: ARICENT-ECFM-MI-MIB
Same published definition
Module imports
{'IF-MIB': ['InterfaceIndex'], 'LLDP-MIB': ['LldpChassisId', 'LldpChassisIdSubtype', 'LldpPortId', 'LldpPortIdSubtype'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TimeInterval', 'TimeStamp', 'RowStatus', 'TruthValue', 'MacAddress', 'TDomain', 'TAddress', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'enterprises', 'Integer32', 'Unsigned32'], 'Q-BRIDGE-MIB': ['VlanIdOrNone', 'VlanId']}
Related source files and packages: