09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Ping implementations vary from platform <strong>to</strong> platform in terms of <strong>the</strong>ir command line<br />

interface (CLI), supported features, and pro<strong>to</strong>cols. When using ping on a system for<br />

<strong>the</strong> first time, check <strong>the</strong> documentation <strong>to</strong> see what options are available. On a UNIX<br />

system, this can be done using <strong>the</strong> command. On Cisco IOS, use<br />

, and on Windows systems, type C:\ ping and <strong>the</strong> CLI usage and<br />

options are displayed.<br />

Using Ping<br />

The ping command can executed from <strong>the</strong> command line in both <strong>the</strong> Windows NT<br />

and UNIX environments, using <strong>the</strong> following command syntax . Depending on <strong>the</strong> ping implementation, ei<strong>the</strong>r a group or stream of ICMP<br />

messages will be sent <strong>to</strong> <strong>the</strong> specified target host. When debugging user <strong>network</strong><br />

problems, this should be <strong>the</strong> first thing you ask <strong>the</strong>m <strong>to</strong> do. If <strong>the</strong> ping test is<br />

successful, move on <strong>to</strong> <strong>the</strong> problem specifics. Quite often, a user will complain that<br />

he cannot get email, when it turns out that he cannot reach anything on <strong>the</strong> <strong>network</strong><br />

because he is not physically connected or <strong>the</strong> IP address information is not properly<br />

configured.<br />

When using <strong>the</strong> ping command <strong>the</strong> host's IP implementation needs <strong>to</strong> be functioning<br />

correctly. This can easily be accomplished by pinging <strong>the</strong> loopback interface that<br />

uses <strong>the</strong> IP address 127.0.0.1:<br />

%ping 127.0.0.1<br />

PING 127.0.0.1 (127.0.0.1): 56 data bytes<br />

64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.478 ms<br />

64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.161 ms<br />

^C<br />

—- 127.0.0.1 ping statistics —-<br />

2 packets transmitted, 2 packets received, 0% packet loss<br />

round-trip min/avg/max = 0.161/0.319/0.478 ms<br />

%<br />

If this ping test fails, <strong>the</strong> host's IP implementation is not functioning correctly or not<br />

configured (an all <strong>to</strong>o common problem with hosts configured using DHCP).<br />

Check <strong>the</strong> host's IP configuration information. On a UNIX host, this is done using <strong>the</strong><br />

command, which will list all of <strong>the</strong> configured interfaces and if <strong>the</strong>y<br />

are up or down. On a Cisco router, you can use <strong>the</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!