Connectivity Fault Management Messages - Avaya 2330 Manual

MIPs help you to discover the hop-by-hop path between MEPs, which allows you to isolate
connection failures to smaller segments of the network and to discover the location of faults
along the paths.
You can create, enable, and disable MIPs independently of MEPs.
An MIP acts based on the relationship between the level assigned to the connectivity fault
management frame received and the level assigned to the MIP. The possible MIP actions are
the following:
• transparently forwards all connectivity fault management frames that have a higher or
lower MD level than the MIP
• processes frames that have the same MD level as the MIP

Connectivity Fault Management messages

CFM uses standard Ethernet frames distinguished by EtherType or (for multicast messages)
by MAC address. All connectivity fault management messages are confined to an MD. Secure
Router 2330/4134 supports the following connectivity fault management messages:
• CCM—multicast heartbeat messages that MEPs periodically initiate. CCM provide the
following services:
- allow MEPs to discover other MEPs within an MA of a domain
- allow MIPs to discover MEPs
You configure CCM for an MA within a domain, or you configure CCM for a VLAN.
• Loopback messages—unicast frames transmitted by an MEP. Loopback messages are
similar to an Internet Control Message Protocol (ICMP) ping message. You initiate a
loopback message to verify connectivity to a particular MP, which indicates if a destination
is reachable.
• Linktrace messages—multicast frames transmitted by an MEP. CFM linktrace messages
are similar to User Datagram Protocol (UDP) linktrace messages. The administrator
initiates a linktrace message to track the path (hop-by-hop) to a destination MEP.
Configuration — Layer 2 Ethernet
Maintenance Domain
July 2013 27