"FD 100/320Gbps NT and FX NT IHub System
Basics, Management and OAM Guide"
Ethernet Connection Fault Management
Issue: 10 3HH-11982-AAAA-TQZZA 173
8.3 Loopback
A loopback message is generated by an MEP to its peer MEP or a MIP (Figure 5).
The functions are similar to an IP ping to verify Ethernet connectivity between the
nodes.
Figure 5 CFM Loopback
The following loopback-related functions are supported:
• Loopback message functionality on an MEP or MIP can be enabled or disabled.
• MEP - Supports generating unicast and multicast loopback messages and
responding to loopback messages with loopback reply messages.
• MEP - Supports generating unicast loopback messages with Test TLV containing
a PRBS pattern with CRC 32 and evaluating if the CRC pattern on the received
loopback reply message matches the CRC pattern sent on the loopback message
• MIP - Supports responding to loopback messages with loopback reply messages
when loopback messages are targeted to self.
• Displays the loopback test results on the originating MEP
8.4 Linktrace
A linktrace message is originated by an MEP and targeted to a peer MEP in the same
MA and within the same MD level (Figure 6). Its function is similar to IP traceroute.
Traces a specific MAC address through the service. The peer MEP responds with a
linktrace reply message after successful inspection of the linktrace message. The
MIPs along the path also process the linktrace message and respond with linktrace
replies to the originating MEP if the received linktrace message has a TTL greater
than 1 and forward the linktrace message if a look up of the target MAC address in
the Layer 2 FIB is successful. The originating MEP shall expect to receive multiple
linktrace replies and from processing the linktrace replies, it can put together the
route to the target bridge.
To Next Page
Loading...
