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

20021027: [8710] tgftp.nws.noaa.gov inaccessible -- no PacNW real-time MM5



All,

NOAAport data stream carried notices of the Verizon network outage
at NCEP today. See the NOXX header messages for more details.
The NMC2 data stream (conduit) is flowing at this time.

Steve Chiswell
Unidata User Support





>From: Matt Rehder <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200210271742.g9RHg3q14018

>David,
>
>Are you still having problems connecting to tgftp.nws.noaa.gov?  From
>my location I am able to succesfully trace and I'm able to succesfully
>trace past our routing zone from our router that serves the
>atmos.washington.edu domain.  From what subnet are you trying to reach
>tgftp.nws.noaa.gov?
>
>-matt
>
>
>
>On Sun, 27 Oct 2002, David Ovens wrote:
>
>>Folks,
>>
>>I finally got through to tgftp.nws.noaa.gov, so that's not the
>>problem.  I have done a traceroute and it looks like we are having
>>bottlenecks somewhere else (see below).  I am forwarding this on to
>>our University NetOps folks just in case they can help.
>>
>>103 ovens,address@hidden traceroute tgftp.nws.noaa.gov
>>traceroute to tgftp.nws.noaa.gov (205.156.51.200), 30 hops max, 40 byte packe
> ts
>> 1  hoover.cac.washington.edu (128.95.175.100)  1 ms  0 ms  1 ms
>> 2  uwbr2-GE0-1.cac.washington.edu (140.142.150.24)  0 ms  0 ms  0 ms
>> 3  uwbr1-GE0-2.cac.washington.edu (140.142.156.1)  0 ms  0 ms  0 ms
>> 4  * * *
>> 5  * * *
>> 6  * * agr3-loopback.NewYork.cw.net (206.24.194.103)  59 ms
>> 7  acr1-loopback.NewYork.cw.net (206.24.194.61)  59 ms  59 ms  59 ms
>> 8  205.171.14.154 (205.171.14.154)  25 ms  18 ms  18 ms
>> 9  205.171.8.201 (205.171.8.201)  82 ms  82 ms  82 ms
>>10  205.171.9.10 (205.171.9.10)  78 ms  78 ms  78 ms
>>11  205.171.9.94 (205.171.9.94)  82 ms  82 ms  82 ms
>>12  65.125.14.202 (65.125.14.202)  84 ms  84 ms  84 ms
>>13  140.90.111.34 (140.90.111.34)  84 ms  84 ms  84 ms
>>14  140.90.81.194 (140.90.81.194)  84 ms  84 ms  84 ms
>>15  tgftp.nws.noaa.gov (205.156.51.200)  84 ms  84 ms  84 ms
>>
>>Our CONDUIT/NMC2 feed seems to have last succeeded at 3:38 am PST (say
>>it does not appear to be any daylight savings switchover problem, per se).
>>
>>David
>>
>>ovens wrote:
>>>
>>> We are unable to connect via ftp to tgftp.nws.noaa.gov and therefore
>>> cannot obtain ETA 104 and 1-degree AVN/GFS grids used to initialize
>>> our real-time PacNW MM5.  Also, the CONDUIT/NMC2 feed is empty --
>>> probably for the same reason.
>>>
>>> David
>>> --
>>>
>>> David Ovens         e-mail: address@hidden
>>> (206) 685-8108          plan: Real-time MM5 forecasting for Pacific Northwe
> st
>>> Research Meteorologist
>>> Dept of Atmospheric Sciences, Box 351640
>>> University of Washington
>>> Seattle, WA  98195
>>>
>>
>>
>>--
>>
>>David Ovens           e-mail: address@hidden
>>(206) 685-8108          plan: Real-time MM5 forecasting for Pacific Northwest
>>Research Meteorologist
>>Dept of Atmospheric Sciences, Box 351640
>>University of Washington
>>Seattle, WA  98195
>>
>

**************************************************************************** <
Unidata User Support                                    UCAR Unidata Program <
(303)497-8643                                                  P.O. Box 3000 <
address@hidden                                   Boulder, CO 80307 <
---------------------------------------------------------------------------- <
Unidata WWW Service                        http://www.unidata.ucar.edu/      <
**************************************************************************** <


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.