Mypower
S4100
Troubleshooting
Maipu Confidential & Proprietary Information
Page
59
of
124
The ping ethernet
command is executed on the
MIP device.
Use the show ethernet cfm maintenance-points local
command to view whether the device is configured with MEP.
If not, the device is MIP and does not support the loopback
test function.
The MD and MA parameters
are incorrect.
If the system prompts “the service instance * is not
configured” when executing ping Ethernet, the MD and MA
name are incorrect.
The link is disconnected or
when the remote CCM
packet is not received, the
remote MEP ID in the local
database is not updated and
is still in the UP state, but it
is found that the link is
disconnected during the
loopback test.
Updating the remote MEP information at the local needs the
3.5 multiples of CC time, so maybe the remote MEP becomes
invalid in fact, but it is in the up state at the local. Here, it is
normal to find that the link is disconnected during the loopback
test. You can wait for some time to view whether the MEP is
updated to the failed state at the local, so as to confirm
whether it is the cause of the problem.
Fault 3: The link tracking cannot be performed or all devices on all links
cannot be displayed.
Possible Reasons
Judging Methods and Solutions
The traceroute Ethernet
command is executed on the
MIP device.
You can use the show ethernet cfm maintenance-points
local command to view whether the device is configured with
MEP. If not, the device is MIP and does not support link
tracking function.
The MD and MA are not
configured on the device.
The device that is not configured with MD or MA directly
forwards the link tracking packets at L2 and do not make
response and as a result, the devices displayed by traceroute
may be incomplete.
The MD and MA parameters
are wrong.
If the system prompts “the service instance * is not
configured” when executing the traceroute Ethernet
command, it indicates that MD and MA name are incorrect.
The link is disconnected or
when the remote CCM
packet is not received, the
remote MEP ID in the local
database is not updated and
is still in the UP state, but it
is found that the link is
disconnected during the
loopback test.
Updating the remote MEP information at the local needs the
3.5 multiples of CC time, so maybe the remote MEP becomes
invalid in fact, but it is in the up state at the local. Here, it is
normal that the link tracking cannot return the correct devices.
You can wait for some time to view whether the MEP is
updated to the failed state at the local, so as to confirm
whether it is the cause of the problem.
The TTL value that
executing the link tracking is
too small.
When the TTL value is 0, the device does not forward the link
tracking packets any more, so TTL value must be larger than or
equal to the number of the devices in the link, so as to get the
correct information of each device. Therefore, you need to
input the appropriate TLL value when executing the link
