Troubleshooting Guide

Table Of Contents
Note:
In the current release, troubleshooting using ping and traceroute (including Layer 2 ping and
Layer 2 traceroute) is not supported on EDM. For more information, see Release Notes for VSP
Operating System Software, NN47227-401. As an alternative, use the ACLI.
Before you begin
On the source and destination nodes, you must configure a CFM MD, MA, and MEP, and
assign a nodal MEP to the B-VLAN
If you want to run a Layer 2 IP Traceroute for a specific VRF, you must use EDM in the specific
VRF context first. For more information, see the procedure for selecting and launching a VRF
context view in Configuration - IP Routing for Avaya Virtual Services Platform 4000 Series,
NN46251-505 or Configuring IP Routing on Avaya Virtual Services Platform 7200 Series and
8000 Series, NN47227-505.
Procedure
1. In the navigation tree, expand the following folders: Configuration > Edit > Diagnostics.
2. Click L2Ping/L2Trace Route
3. Click the L2 IP Traceroute tab.
4. To add a new entry, click Insert, specify the destination IP address and, optionally, the TTL
value, and then click Insert.
5. To start the Layer 2 IP traceroute, highlight an entry, and then click the Start button.
6. To update the L2 IP traceroute, click the Refresh button.
7. To stop the Layer 2 IP traceroute, click the Stop button.
L2 IP Traceroute field descriptions
Use the data in the following table to use the L2 IP Traceroute tab.
Name
Description
IpAddrType Specifies the address type of destination IP address
(only IPv4 is supported).
IPAddr Specifies the destination IP Address.
VrfId Specifies the VRF ID.
VrfName Specifies the name of the virtual router.
Ttl Specifies the number of hops remaining to this
L2Trace. This value is decremented by 1 by each
Bridge that handles the L2Trace. The decremented
value is returned in the L2Trace. If 0 on output, the
L2Trace is not transmitted to the next hop. The
default value is 64
Status Indicates the status of the transmit loopback service:
ready: the service is available.
Table continues…
CFM configuration using EDM
January 2017 Troubleshooting 201
Comments on this document? infodev@avaya.com