[EHPweb] Requesting trace routes from Source to Destination

[Robert Simpson]

Thanks Michael,

I'm still having problems logging in to machines at various sites, and  
our 3 quake servers are still not getting earthquake information from  
the three hubs, one of them outside USGS.

Jeff Brody thinks there might be a problem with the Domain Name Server  
- 130.118.4.2.   Hard to believe that a problem with a single Domain  
Name Server could cause such a mess....

Bob Simpson
    simpson at usgs.gov
    (650)-329-4865  (office)  (650)-322-9322 (home)

--------------
On Oct 19, 2008, at 12:27 AM, Tait, Michael R wrote:

> Mr. Simpson,
>
> I’ve opened ticket 2008101901243.   I haven’t determined or isolated  
> the cause of the reported problem.  At this time I am referring to  
> 2nd level to review ticket in the morning.
>
> Thanks,
>
> Michael Tait
> Verizon Business ESN NOSC
> 866-376-6672
>
>
> From: Robert Simpson [mailto:simpson at usgs.gov]
> Sent: Sunday, October 19, 2008 2:13 AM
> To: Tait, Michael R
> Cc: David Oppenheimer H; Wald Lisa; Christopher Bidwell
> Subject: Re: Requesting trace routes from Source to Destination
>
> Hi Mike,
>
> Here are the 3 hubs:
>
> host qdds1.wr.usgs.gov
> qdds1.wr.usgs.gov has address 130.118.43.18
>
> host qdds2.er.usgs.gov
> qdds2.er.usgs.gov has address 130.11.56.112
>
> host dmc.iris.washington.edu
> dmc.iris.washington.edu has address 128.95.166.129
>
> And here are 3 traceroutes, the last one which is still working...
>
> pascal:9>  traceroute ehznorth.wr.usgs.gov
> traceroute to ehznorth.wr.usgs.gov (130.118.61.120), 64 hops max, 40  
> byte packets
>  1  salt5-l3-vlan22 (130.118.22.215)  4.167 ms  0.411 ms  0.299 ms
>  2  ehznorth (130.118.61.120)  0.181 ms  0.242 ms  0.178 ms
>
> pascal:10>  traceroute ehzeast.er.usgs.gov
> traceroute to ehzeast.er.usgs.gov (130.11.44.114), 64 hops max, 40  
> byte packets
>  1  salt5-l3-vlan22 (130.118.22.215)  4.205 ms  0.354 ms  0.241 ms
>  2  mpj1-ca-f000.usgs.net (130.118.12.116)  2.939 ms  0.904 ms   
> 0.848 ms
>  3  198.187.220.102 (198.187.220.102)  66.595 ms  66.583 ms  66.405 ms
>  4  130.11.7.249 (130.11.7.249)  66.497 ms  66.483 ms  66.395 ms
>  5  ehzeast.er.usgs.gov (130.11.44.114)  66.593 ms  66.677 ms   
> 66.585 ms
>
> pascal:11>  traceroute ehzden.cr.usgs.gov
> traceroute to ehzden.cr.usgs.gov (137.227.224.73), 64 hops max, 40  
> byte packets
>  1  salt5-l3-vlan22 (130.118.22.215)  4.109 ms  0.342 ms  0.241 ms
>  2  mp1-ca-f100.usgs.net (130.118.12.117)  3.161 ms  1.009 ms  0.808  
> ms
>  3  198.187.220.123 (198.187.220.123)  28.620 ms  28.677 ms  28.699 ms
>  4  * * *
>  5  * * *
>  6  * * *
>  7  * * *
>  8  * * *
>  9  * * *
> 10  * * *
> 11  * * *
> 12  * * *
> 13  * * *
> 14  * * *
> 15  * * *
> 16  * * *
> 17  * * *
> 18  * * *
> 19  * * *
> 20  * * *
>
>
> On Oct 18, 2008, at 10:59 PM, Tait, Michael R wrote:
>
>
> Mr. Simpson
>
> To help isolate any possible capacity, latency or routing issue; can  
> you please supply us with trace routes from your source ip address  
> to each server?   Could you also supply the ip addresses of the hubs  
> that feed the servers?
>
> Thanks,
>
> Michael Tait
> Verizon Business ESN NOSC
> 866-376-6672
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://geohazards.usgs.gov/pipermail/ehpweb/attachments/20081019/f32a13e2/attachment-0001.html