ping interfaces

Submitted by admin on Wed, 11/03/2010 - 09:06
baby scan
  1. introduction
  2. request from xcl01
  3. request from ics01
  4. troubleshoot

introduction

Ping interfaces. See http://cluster.planetlarg.com/mediawiki/index.php/Ping_errors

request from xcl01

Ping the LIC from xcl01.

  1. Open a CLI on the server host.
  2. Request echoes from the web server interface. 
    issalarg@xcl01:~$ ping -c10 200.0.0.10
PING 200.0.0.10 (200.0.0.10) 56(84) bytes of data.

--- 200.0.0.10 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9013ms

issalarg@xcl01:~$
    Nothing! The firewall drops these packets. Or does it? Is this the sign of a deeper malaise?
  3. Request a web page the web server interface. 
    issalarg@xcl01:~$ lynx -dump http://200.0.0.10/infrastructure/host1
ics01

issalarg@xcl01:~$
    Good! The firewall accepts these packets. All the hardware and software between here and ics01 must be good.
  4. Close the CLI.

request from ics01

Ping ics01's gateway from ics01.

  1. Open a CLI on the server host.
  2. Request 10 echoes from the gateway interface. 
    issalarg@ics01:~$ ping -c10 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.566 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.176 ms

--- 192.168.0.1 ping statistics ---
10 packets transmitted, 2 received, 80% packet loss, time 9012ms
rtt min/avg/max/mdev = 0.176/0.371/0.566/0.195 ms
issalarg@ics01:~$
    Look at those sequence numbers (icmp_seq). 1 and 5? Where did the other eight go? Did they fall on the cyberspace floor? Are they stuck round the ethernet u-bend?
  3. Close the CLI.

troubleshoot

content