Troubleshooting Guide

Destination addresses for C-VLAN l2 traceroute and linktrace messages
For C-VLANs, CFM uses the following destination MAC addresses for the corresponding
maintenance domain (MD) levels for l2 traceroute and linktrace messages.
The Avaya Virtual Services Platform switch supports both l2 traceroute and linktrace for
C-VLANs, but Avaya prefers you use l2 traceroute.
Table 37: MD levels and corresponding destination addresses for CFM for C-VLANs
CFM MD Level Destination MAC address
0 01:80:c2:00:00:38
1 01:80:c2:00:00:39
2 01:80:c2:00:00:3a
3 01:80:c2:00:00:3b
4 01:80:c2:00:00:3c
5 01:80:c2:00:00:3d
6 01:80:c2:00:00:3e
7 01:80:c2:00:00:3f
l2 tracetree
The l2 tracetree command is a proprietary command that allows a user to trigger a multicast
LTM message by specifying the B-VLAN and I-SID. This command allows the user to view a
multicast tree on the SPBM B-VLAN from the source node to the destination nodes for a particular I-
SID.
Note:
The Avaya Virtual Services Platform 4000 Series does not support the l2 tracetree
command on C-VLANs because no multicast tree exists on C-VLANs.
Maintenance domain intermediate points (MIP)
MIPs do not initialize any CFM messages. MIPs passively receive CFM messages, process the
messages received and respond back to the originating MEP. By responding to received CFM
messages, MIPs can support discovery of hop-by-hop path among MEPs, allow connection failures
to be isolated to smaller segments of the network to help discover location of faults along the paths.
MIPs can be created independent of MEPs. MIP functionality can be summarized as:
• Respond to Loopback (ping) messages at the same level as itself and addressed to it.
• Respond to Linktrace (traceroute) messages.
• Forward Linktrace messages after decrementing the TTL.
CFM fundamentals
January 2017 Troubleshooting 151
Comments on this document? [e-mail]