Juniper Networks 10.4 FromRouter MX-2, start a one-way delay measurementto Router MX-1., Thecounters are displayed aspart of the local MEP database on Router MX-2.

}
protocols{
oam{
ethernet{
connectivity-fault-management{
traceoptions{
fileeoam_cfm.log size 1g files 2 world-readable;
flagall;
}
linktrace{
path-database-size255;
age10s;
}
maintenance-domainmd6 {
level6;
maintenance-associationma6 {
continuity-check{
interval100ms;
hold-interval1;
}
mep101 {
interfacege-0/2/5.0;
directiondown;
auto-discovery;
}
}
}
}
}
}
}
FromRouter MX-2, start a one-way delay measurementto Router MX-1.
user@MX-2> monitorethernetdelay-measurement one-waymep 201 maintenance-domain md6
maintenance-associationma6 count 10
One-way ETH-DM request to 00:90:69:0a:43:94, Interface ge-0/2/5.0
1DM Frames sent : 10
--- Delay measurement statistics ---
Packets transmitted: 10
Average delay: NA, Average delay variation: NA
Best case delay: NA, Worst case delay: NA
Thecounters are displayed aspart of the local MEP database on Router MX-2.
user@MX-2> showoam ethernet connectivity-fault-managementmep-database
maintenance-domainmd6 maintenance-domain ma6
Maintenance domain name: md6, Format: string, Level: 6
Maintenance association name: ma6, Format: string
Continuity-check status: enabled, Interval: 100ms, Loss-threshold: 3 frames
MEP identifier: 101, Direction: down, MAC address: 00:90:69:0a:48:57
Auto-discovery: enabled, Priority: 0
Interface name: ge-0/2/5.0, Interface status: Active, Link status: Up
Defects:
Remote MEP not receiving CCM : no
Erroneous CCM received : no
Cross-connect CCM received : no
RDI sent by some MEP : no
127Copyright© 2010, Juniper Networks,Inc.
Chapter11: ITU-T Y.1731Ethernet Frame Delay Measurements