Juniper ACX1000 Configuration Manual page 1197

Copyright © 2017, Juniper Networks, Inc.
Chapter 34: Configuring Operations, Administration, and Management (OAM)
maintenance-domain maintenenace-domain-name {
level level-number;
maintenance-association maintenance-domain-name {
continuity-check {
interval 1s;
loss-threshold 3;
}
mep mep-id {
interface interface-name;
direction up | down;
priority priority-value;
action-profile action-profile-name;
}
}
}
NOTE: You cannot configure a maintenance domain level that is lower than
or equal to the level that it is associated with.
To support ETH-AIS transmission, the following configuration information required by a
server MEP:
Server MEP definition—Defines the association of server MEP identifier to the server
layer.
For Layer 2 circuit and Layer 2 VPN, the logical interface connected to a customer
network (UNI) would be the identifier for the server layer that needs to be monitored
by the server MEP.
For physical link loss detection, the physical interface under Ethernet protocol would
be the identifier for the server layer that needs to be monitored by the server MEP.
Association of server MEP defect—Defines the association of server MEP defects to
ETH-AIS action.
Association action profile and server MEP—Defines the binding of server MEP and
action profile.
To configure ETH-AIS in server MEP, you need to:
Create an action profile with ETH-AIS action for server MEP defects.
Attach the action profile to a server MEP
To create an action profile, include the following statements at the [edit protocols oam
ethernet connectivity-fault-management] hierarchy level:
[edit protocols oam ethernet connectivity-fault-management]
action-profile action-profile-name {
event {
server-mep-defects {
link-loss-defect;
l2circuit-defect;
l2vpn-defect;
}
1139