Edge-Core ES3510MA-DC, Management Manual, Page: 995 / 1098

C
HAPTER
40
| CFM Commands
– 995 –
packet-size – The size of the loopback message. (Range: 64-1518
bytes)
D
EFAULT
S
ETTING
Loop back count: One loopback message is sent.
Loop back size: 64 bytes
C
OMMAND
M
ODE
Privileged Exec
C
OMMAND
U
SAGE
◆
Use this command to test the connectivity between maintenance
points. If the continuity check database does not have an entry for the
specified maintenance point, an error message will be displayed.
◆
The point from which the loopback message is transmitted (i.e., the
DSAP) and the target maintenance point specified in this command
must be within the same MA.
◆
Loop back messages can be used for fault verification and isolation
after automatic detection of a fault or receipt of some other error
report. Loopback messages can also used to confirm the successful
restoration or initiation of connectivity. The receiving maintenance point
should respond to the loop back message with a loopback reply.
◆
When using the command line or web interface, the source MEP used
by to send a loopback message is chosen by the CFM protocol.
However, when using SNMP, the source MEP can be specified by the
user.
E
XAMPLE
This example sends a loopback message to the specified remote MEP.
Console#ethernet cfm loopback dest-mep 1 md voip ma rd
Console#
mep fault-notify
lowest-priority
This command sets the lowest priority defect that is allowed to generate a
fault alarm. Use the no form to restore the default setting.
S
YNTAX
mep fault-notify lowest-priority priority
no fault-notify lowest-priority
priority – Lowest priority default allowed to generate a fault alarm.
(Range: 1-6)
D
EFAULT
S
ETTING
Priority level 2