Manualshelf

Troubleshooting Guide

ManualsBrandsExtreme Networks ManualsComputers & AccessoriesFabric-enabled multi-service edge switches
21222324252627282930
Table Of Contents
Chapter 7: Troubleshooting tool
fundamentals
This section provides conceptual information about the methods and tools that you can use to
troubleshoot and isolate problems in the Avaya Virtual Services Platform 4000 Series network.
Troubleshooting overview
The types of problems that typically occur with networks involve connectivity and performance.
Virtual Services Platform 4000 supports a diverse range of network architectures and protocols,
some of which maintain and monitor connectivity and isolate connectivity faults.
In addition, Virtual Services Platform 4000 supports a wide range of diagnostic tools that you can
use to monitor and analyze traffic, capture and analyze data packets, trace data flows, view
statistics, and manage event messages.
Certain protocols and tools are tailored for troubleshooting specific Virtual Services Platform 4000
network topologies. Other tools are more general in their application and you can use them to
diagnose and monitor ingress and egress traffic on Virtual Services Platform 4000.
If connectivity problems occur and the source of the problem is unknown, it is usually best to follow
the Open Systems Interconnection (OSI) network architecture layers. Confirm that your physical
environment, such as the cables and module connections, operates without failures before moving
up to the network and application layers.
To gather information about a problem, consider the following information:
• Consider the OSI model when you troubleshoot. Start at Layer 1 and move upwards. The
Address Resolution Protocol (ARP) can cause problems; ARP operates at Layer 2 to resolve
MAC addresses to IP addresses (Layer 3).
• Device-specific tools and protocols can help you gather information. This document outlines
Virtual Services Platform 4000-specific tools.
• You can use client- and server-based tools from Microsoft, Linux, and UNIX. For example, you
can use Windows tools like ifconfig, ipconfig, winipcfg, and route print to obtain IP information
and routing tables. Servers also maintain route tables.
The following command output shows example output of the route print command.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\jsmith>route print
===============================================================================
January 2017 Troubleshooting 28
Comments on this document? infodev@avaya.com