Chapter 5: Initial Troubleshooting - Avaya Virtual Services Platform 7000 Series Troubleshooting Manual

Chapter 5: Initial troubleshooting

The problems that typically occur with networks involve connectivity and performance. A good
practice is to follow the OSI network architecture layers. Confirm that the physical environment, such
as the cables and module connections, is operating failure free before moving up to the network and
application layers.
As part of your initial troubleshooting, Avaya recommends that you check the Knowledge and
Solution Engine on the Avaya web site for known issues and solutions related to the problem you
are experiencing.
Information for technical support
Before you contact Avaya technical support personnel, it is important that you perform the following
tasks:
• Use the show running-config command to obtain the default and current switch
configuration.
• Use the show tech command to obtain technical information about system status, hardware,
software, and switch operation.
• Review log files for information about past events.
• Use the show sys-info or show system verbose commands to obtain the software
version that is running on all cards.
• Obtain an accurate and detailed topology diagram of your network that shows the nodes and
connections.
• Obtain information about recent changes or upgrades to your system, network, or custom
applications (for example, if configuration or code was changed), including the date and time of
the changes, and the names of the individuals who made them. Get a list of events that
occurred prior to the trouble, such as an upgrade, a LAN change, increased traffic, or
installation of new hardware.
• After connectivity problems occur, obtain information about at least five working source and
destination IP address pairs, and five IP address pairs with connectivity issues, using the
following commands:
- show tech
- show running-config
- show port-statistics <port>
• Use the EDM MIB web page functions. For more information, see Configuring System
Monitoring on Avaya Virtual Services Platform 7000 Series, NN47202–505.
Troubleshooting Avaya VSP 7000 Series
28
Comments on this document? infodev@avaya.com
July 2015