Setup guide

Using the ping and tracert Commands
67
tracert
While ping can test for connectivity between two network hosts, tracert (short for “trace
route”) can verify the network path that the data uses to travel between the two hosts.
Because Avid Composer Products applications are data intensive, it is important that large
amounts of data be transferred between the Nearchive Base Server and Storage System and
its clients in a timely fashion. An incorrectly configured network might get the data to its
destination, but be too slow for your application to work effectively.
You can use the tracert command to confirm that the data is traveling along an optimal path.
In a Nearchive environment, the Nearchive Base Server and Storage System and its clients
should send traffic directly to each other. Routers should not be used to direct traffic between
them.
It is possible for network traffic to take one path going to a system and a different path
coming back. Therefore, it is important to run tracert from both the Nearchive Base Server
and Storage System and its clients to test the data path in both directions.
As with ping, you can use many options with tracert. This section discusses two types of
tracert syntax:
tracert [System Name]
where [System Name] is the network name of the remote system to which you are
testing connectivity
or
tracert [IP Address]
where [IP Address] is the IP address of the remote system to which you are testing
connectivity
To run the tracert command:
1. Open an MS-DOS command prompt window.
2. At the command line, type the tracert command (for example,
tracert 192.168.10.5) .
The tracert result should resemble the following:
Tracing route to [remote system name or IP address] over a
maximum of 30 hops:
1 10 ms <10 ms <10 ms [remote system name or IP address]
Trace complete.
One entry indicates
an optimal route.