one of our boxes at rackshack are giving this problem. any idea what can it be wrong l?


1 vlan206.inr-203-eva.Berkeley.EDU (128.32.206.1) 0.727 ms 3.269 ms 0.996 ms
2 vlan209.inr-201-eva.Berkeley.EDU (128.32.255.1) 0.829 ms 0.672 ms 0.680 ms
3 fast4-1-0.inr-new-666-doecev.Berkeley.EDU (128.32.0.73) 1.522 ms 0.994 ms 0.971 ms
4 qsv-juniper--ucb-gw.calren2.net (128.32.0.66) 3.656 ms 9.394 ms 3.128 ms
5 POS1-0.hsipaccess1.SanJose1.Level3.net (209.247.159.109) 3.041 ms 3.248 ms 3.962 ms
6 ae0-55.gar1.SanJose1.level3.net (64.159.2.140) 4.661 ms 3.667 ms 4.109 ms
7 so-6-0-0.edge1.SanJose1.level3.net (209.244.3.138) 4.782 ms 4.111 ms 4.289 ms
8 interconnect-eng.SanJose1.Level3.net (209.245.146.206) 4.441 ms 5.801 ms 4.184 ms
9 sntcca1wcx2-pos1-0.wcg.net (64.200.240.125) 4.955 ms 5.880 ms 5.275 ms
10 anhmca1wcx2-oc48.wcg.net (64.200.151.98) 16.545 ms 16.653 ms 15.946 ms
11 dllstx1wcx3-oc48.wcg.net (64.200.240.5) 66.509 ms 65.467 ms 66.294 ms
12 dllstx1wcx2-oc48.wcg.net (64.200.110.77) 65.531 ms 65.752 ms 66.027 ms
13 dllstx1wcx2-intcomm-pos.wcg.net (64.200.111.178) 66.970 ms 66.304 ms 66.090 ms
14 64.200.162.2 (64.200.162.2) 66.377 ms 65.969 ms 66.530 ms
15 207.218.223.37 (207.218.223.37) 1096.358 ms !H 3997.073 ms !H 3999.032 ms !H

can you SSH into the box and look around?

With returns like:

1096.358 ms !H 3997.073 ms !H 3999.032 ms !H

This usually yields kernel IP routing issues. If this only affects a set range of IPs, you can correct this with the route command provided you can log into the machine.

An !H in traceroute means that the router is reporting back that the "Host is unreachable".