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

[CONDUIT #RFO-442890]: GFS upgrade

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [CONDUIT #RFO-442890]: GFS upgrade
  • Date: Mon, 29 Dec 2014 10:46:55 -0700
Hi Carissa,

re:
> I just tried calling you, let me know when you have a few minutes to
> troubleshoot. Our folks see all firewalls open for you.

I have been/am working from home this morning, and I can be reached at
303.258.0906 until about noon MST.

Let's verify that we are trying to access the correct machine:  all
of my 'notifyme' tests are trying to reach 140.90.101.93.

FYI:

- the 'notifyme' that I left running on lead.unidata.ucar.edu never
  did reach 140.90.101.93

- 'traceroute to 140.90.101.93' from lead.unidata.ucar.edu shows:

 1  ml-mr-j1-es-n12 (128.117.12.251)  0.978 ms  1.128 ms  1.385 ms
 2  mlra-ml-mr-j1-es-net (128.117.243.55)  0.221 ms  0.217 ms  0.210 ms
 3  tcom-gs-1-n243-72 (128.117.243.77)  0.377 ms  0.363 ms  0.380 ms
 4  xe-0-1-2.873.core-l3.frgp.net (128.117.243.9)  1.252 ms  1.237 ms  1.227 ms
 5  v3454.rtr-chic.frgp.net (192.43.217.222)  23.328 ms  23.284 ms  23.348 ms
 6  et-9-0-0.115.rtr.wash.net.internet2.edu (198.71.45.57)  40.900 ms  40.804 
ms  40.721 ms
 7  198.71.45.228 (198.71.45.228)  41.415 ms  40.848 ms  40.817 ms
 8  ae0.clpk-core.maxgigapop.net (206.196.178.81)  42.108 ms  41.775 ms  41.518 
ms
 9  noaa-rtr.maxgigapop.net (206.196.177.118)  41.559 ms  41.588 ms  54.023 ms
10  140.90.111.36 (140.90.111.36)  42.104 ms  41.796 ms  41.755 ms
11  140.90.76.69 (140.90.76.69)  41.965 ms  42.302 ms  42.050 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
 ...

Cheers,

Tom

> address@hidden> wrote:
> 
> > Hi Carissa,
> >
> > We are still unable to connect to the LDM on 140.90.101.93 to
> > REQUEST a feed of CONDUIT data.  The command I am using to check
> > the connectivity is:
> >
> > notifyme -vl- -f CONDUIT -h 140.90.101.93
> >
> > The inability to connect from the two machines that worked last
> > week (lead.unidata.ucar.edu and atm.ucar.edu) appears to be a
> > result of a firewall somewhere in NOAA.
> >
> > Can you (re)contact your network admins to see if they can figure
> > out why our attempts to connect are being blocked?
> >
> > Thanks in advance...
> >
> > Cheers,
> >
> > Tom
> > --
> >
> > ****************************************************************************
> > Unidata User Support                                    UCAR Unidata
> > Program
> > (303) 497-8642                                                 P.O. Box
> > 3000
> > address@hidden                                   Boulder, CO
> > 80307
> >
> > ----------------------------------------------------------------------------
> > Unidata HomePage                       http://www.unidata.ucar.edu
> >
> > ****************************************************************************
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: RFO-442890
> > Department: Support CONDUIT
> > Priority: Normal
> > Status: Closed
> >
> >
> 
> 

Cheers,

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


Ticket Details
===================
Ticket ID: RFO-442890
Department: Support CONDUIT
Priority: Normal
Status: Open