Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos ®
OS 12.3 Ethernet Interfaces Configuration Guide
Configuring the Maintenance Endpoint Interface
MEP Interface
Configuration
NOTE: Starting with Junos OS Release 12.3, for all interfaces configured on
Modular Port Concentrators (MPCs) on MX Series 3D Universal Edge Routers,
you no longer need to configure the no-control-word statement for all Layer
2 VPNs and Layer 2 circuits over which you are running CFM MEPs. For all
other interfaces on MX Series routers and on all our routers and switches,
you must continue to configure the no-control-word statement at the [edit
routing-instances routing-instance-name protocols l2vpn] or [edit protocols
l2circuit neighbor neighbor-id interface interface-name] hierarchy level when
you configure CFM MEPs. Otherwise, the CFM packets are not transmitted,
and the show oam ethernet connectivity-fault-management mep-database
command does not display any remote MEPs.
You must specify the interface to which the MEP is attached. It can be a physical interface,
logical interface, or trunk interface.
On MX Series routers, you can enable the MEP on a specific VLAN of a trunk interface.
To configure the interface, include the interface interface-name statement at the [edit
protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name mep mep-id] hierarchy level.
This example shows the MEP interface configuration statements:
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name]
mep mep-id {
direction (up | down);
interface (ge | xe)-(fpc/pic/port | fpc/pic/port.domain | fpc/pic/port.domain vlan vlan-id);
auto-discovery;
priority number;
}
Configuring the Maintenance Endpoint Priority
You can specify the IEEE 802.1 priority bits that are used by continuity check and link
trace messages.
To configure the priority, include the priority statement at the [edit protocols oam ethernet
connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name mep mep-id] hierarchy level.
Configuring the Maintenance Endpoint Lowest Priority Defect
192
You can specify the lowest priority defect that is allowed to generate a fault alarm. This
configuration determines whether to generate a fault alarm whenever it detects a defect.
This configuration is done at the MEP level.
Copyright © 2012, Juniper Networks, Inc.