[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: McIDAS GOES-8 Vis Area Files

Jim Koermer wrote:
My IDD and local appear to be the problem. We are the only place showing
high latencies on the McIDAS topology page. I can traceroute fine to
UMICH, but I bet if anyone tries to traceroute to mammatus.plymouth.edu,
they may see a problem. If anyone would care to do a traceroute, I'd
appreciate seeing the results. It's tough to convince my network folks
that there is a problem without some additional evidence.

                                Jim

Jim Koermer wrote:
>
> I haven't received any new visible data this morning (as of 1345Z), yet
> NOAAPORT GINI data are being recived. Anyone else seeing this?
>
>                                 Jim
> --
> James P. Koermer             E-Mail: address@hidden
> Professor of Meteorology     Office Phone: (603)535-2574
> Natural Science Department   Office Fax: (603)535-2723
> Plymouth State College       WWW: http://vortex.plymouth.edu/
> Plymouth, NH 03264

--
James P. Koermer             E-Mail: address@hidden
Professor of Meteorology     Office Phone: (603)535-2574
Natural Science Department   Office Fax: (603)535-2723
Plymouth State College       WWW: http://vortex.plymouth.edu/
Plymouth, NH 03264

Hi Jim,

Yes, traceroute shows some slow speeds:

(anne) imogene:/home/anne/pdfFiles 60 % traceroute mammatus.plymouth.edu
traceroute to mammatus.plymouth.edu (158.136.73.164), 30 hops max, 38 byte packets
 1  flr-n140 (128.117.140.254)  0.644 ms  0.453 ms  0.465 ms
 2  vbnsr-n2.ucar.edu (128.117.2.252)  0.755 ms  0.788 ms  0.769 ms
 3  internetr-n243-104.ucar.edu (128.117.243.106)  1.176 ms  0.903 ms  0.925 ms
 4  den-edge-10.ucar.edu (128.117.243.118)  1.976 ms  2.016 ms  2.311 ms
 5  den-core-02.inet.qwest.net (205.171.16.173)  2.220 ms  1.902 ms  2.307 ms
 6  p5-2.crtntx1-cr8.bbnplanet.net (4.24.117.65)  22.588 ms  22.282 ms  22.211 ms
 7  p5-3.crtntx1-ba2.bbnplanet.net (4.24.8.197)  22.355 ms  22.635 ms  22.608 ms
 8  mae-dallas-atm-gtei.globalcenter.net (4.24.147.26)  46.747 ms  47.218 ms  48.611 ms
 9  pos2-0-622M.cr1.JFK.gblx.net (206.132.253.85)  69.820 ms  65.329 ms  67.808 ms
10  pos0-0-622M.cr1.NYC3.gblx.net (206.132.253.194)  70.618 ms  65.695 ms  77.552 ms
11  pos2-0-622M.cr2.NYC3.gblx.net (208.48.234.134)  72.730 ms  81.409 ms  77.148 ms
12  * UniversityofNewHampshire.ATM3-0.cr2.NYC3.gblx.net (208.51.142.110)  86.481 ms  78.120 ms
13  ehy623.plymouth.edu (158.136.12.2)  83.093 ms  89.944 ms *
14  ehy623.plymouth.edu (158.136.12.2)  105.475 ms  106.389 ms  102.536 ms
15  xhyd04-1.plymouth.edu (158.136.1.1)  150.469 ms  150.097 ms  155.712 ms
16  xlam04-2.plymouth.edu (158.136.2.3)  132.760 ms  130.825 ms  84.880 ms
17  mammatus.plymouth.edu (158.136.73.164)  100.782 ms  92.011 ms  85.251 ms

In case you haven't seen it before, we have a web page about this: http://www.unidata.ucar.edu/packages/ldm/troubleshooting/networkTrouble.html

It looks like a lot of the slow speeds are on your campus.   It is definately worthwhile to gather evidence to take to your network people.  Perhaps they can switch you to a site closer to the exterior connection so you can avoid the slow hops on campus...

Good luck!

Anne 

-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                  P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************