Network troubleshooting tools

This chapter contains information about network troubleshooting in the following areas:

·         Network Connection Problems

·         ping

·         tracert

·         pathping

·         ethereal

Network connection problems
 

If the DS300 or DS400 Ethernet ports cannot connect to the network, check the following:

 

 

 
 
 

The network cable must be securely attached at all connections. If the cable is attached securely but the problem persists, try a different cable. 

 

Note: You must use Category 5 cabling at a minimum.

 

 

 

The Ethernet Link Status light illuminates when the Ethernet controller receives a LINK pulse from the hub or switch. If the light is off, there might be a bad connector, a bad cable, or a problem with the hub or switch.

 

 
 

 

 

To return to the PD maps, click the Back arrow on your browser.


ping

 

Ethernet networks implement a connection verification test called ping, which is supported by both the DS300 and DS400. It can be invoked through the CLI diag global command.  Ping can also be initiated from any systems running Windows or Linux operating systems.

 

The ping function sends echo request packets to a network device (such as an Ethernet switch). Upon receiving the request, the device sends an echo reply to verify the path from the sending device to the receiving device.

 

To initiate the ping function, type the following at a system command prompt:

 

ping [destination computer or IP address] 

 

Here are some examples:

 

ping www.google.com
ping 192.168.100.4
ping 127.0.0.1

 

The last example in the above list shows how to check whether TCP/IP is installed and active on your system. The last address given is the local host loopback address. Contrary to the definition of this IP address, it does not test the transmit/receive capability of your NIC(s). Diagnostics supplied with your NIC often provide a series of tests that verify the functionality of the card.

 

The following example shows the output from a ping initiated from a Windows command (cmd) window.

 

C:\ping 192.168.100.4
Pinging 192.168.100.4 with 32 bytes of data: 
Reply from 192.168.100.4: bytes=32 time<10ms TTL=128
Reply from 192.168.100.4: bytes=32 time<10ms TTL=128
Reply from 192.168.100.4: bytes=32 time<10ms TTL=128
Reply from 192.168.100.4: bytes=32 time<10ms TTL=128
 

The following example shows the output from an unsuccessful ping test:

 
C:\>ping 192.168.0.4
Pinging 192.168.0.4 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.4:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

For more information on the ping test, refer to the following Microsoft Web site: Ping syntax .

 

 

 

 

tracert

The tracert utility is a diagnostic utility that determines the route taken to a destination by sending Internet Control Message Protocol (ICMP) packets with varying time-to-live (TTL) values to the destination.

Note: Ensure that ICMP is enabled on your system. Some operating systems disable ICMP for security reasons.

To initiate the tracert function, type the following at a system command prompt:

tracert [destination computer or IP address] 

Here are two examples:

tracert www.google.com
tracert 192.168.100.4

 

The following example shows sample output from a tracert test.

 

C:\>tracert www.google.com
Tracing route to www.google.akadns.net [64.233.167.99]
over a maximum of 30 hops:
 
1   <10 ms   <10 ms   <10 ms  192.168.254.254
2     *        *        *     Request timed out.
3    10 ms    10 ms    10 ms  172.30.89.81
4    10 ms    10 ms    10 ms  172.30.89.110
5    10 ms    10 ms    30 ms  172.30.89.174
6    10 ms    10 ms    10 ms  172.30.89.250
7    20 ms    41 ms    20 ms  12.119.95.33
8    20 ms    30 ms    30 ms  gbr3-p100.ormfl.ip.att.net [12.123.218.34]
9    30 ms    20 ms    20 ms  gbr4-p60.ormfl.ip.att.net [12.122.5.138]
10   30 ms    30 ms    20 ms  tbr1-p012302.attga.ip.att.net [12.122.2.181]
11   20 ms    30 ms    30 ms  ggr1-p360.attga.ip.att.net [12.123.20.249]
12   20 ms    30 ms    30 ms  att-gw.atl.cw.net [192.205.32.118]
13   80 ms    50 ms    60 ms  dcr2-loopback.Chicago.savvis.net [208.172.2.100]
14   50 ms    60 ms    60 ms  bpr1-so-0-0-0.ChicagoEquinix.savvis.net [208.175.10.238]
15   50 ms    60 ms    60 ms  bhr1-pos-10-0.ElkGrovech3.savvis.net [208.172.3.74]
16   50 ms    60 ms    60 ms  csr11-ve242.ElkGrovech3.savvis.net [216.64.194.139]
17   81 ms    60 ms    50 ms  216.64.195.50
18   60 ms    60 ms    60 ms  64.233.175.38
19   50 ms    60 ms    61 ms  64.233.167.99
Trace complete

 

For more information on tracert, refer to the following Microsoft Web site: tracert syntax .

pathping

The pathping test provides information about network latency and network loss at intermediate hops between a source and destination. The pathping test sends multiple Echo Request messages to each router between a source and destination over a period of time and then computes results based on the packets returned from each router.

To initiate the pathping function, type the following at a system command prompt:

pathping [destination computer or IP address] 

Here are two examples:

The following example shows sample output from a pathping test.

 

C:\>pathping www.google.com
 
Tracing route to www.google.akadns.net [216.239.39.104]
over a maximum of 30 hops:
  0  IBM-1234567 [192.168.254.129]
  1  192.168.254.254
  2  ...
Computing statistics for 50 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                                                      IBM-1234567 [192.168.254.129]
                                                    0/ 100 =  0%   |
  1    21ms          0/ 100 =  0%     0/ 100 =  0%  192.168.254.254
                                                   10/ 100 =10%   |
  2  10               15/ 100 =15%     3/ 100 =  3%  
 
Trace complete.            

 

For more information on pathping, refer to the following Microsoft web site: pathping syntax.


Ethereal

 

Ethereal® is a powerful tool that enables you to analyze network protocol. With an effective GUI interface, Ethereal lets you interactively browse packet data from a live network or from a previously saved capture file.

 

To download the Ethereal package, go to the following Web site: Ethereal.com

 

Back to the top