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

Re: 20000119: datafeed from cirrus

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: Re: 20000119: datafeed from cirrus
  • Date: Wed, 19 Jan 2000 13:04:23 -0700 (MST)
On Wed, 19 Jan 2000, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >To: Unidata Support <address@hidden>
> >From: Anthony Rockwood - MSCD Meteorology <address@hidden>
> >Subject: datafeed from cirrus
> >Organization: .
> >Keywords: 200001191658.JAA00503
> 
> Rob,
> 
> I had our systems people check our connection to cirrus and this was their
> response:
> 
> *******************************************************************
> Tony
> 
> The good news is, it does not look like a problem on our end.  The
> bad news is it looks like noaa is having network problems.  When
> I try a trace route it times out from inside their network.  You can
> see this by running this as any user:  traceroute cirrus.al.noaa.gov
> You'll see that at hop 17 or 18 it cant go anywhere.
> *************************************************************

Tony,

Networks configurations are a PITA.  I just did a traceroute again:

traceroute to cirrus.al.noaa.gov (140.172.240.73), 30 hops max, 40 byte
packets
 1  flr-n148.ucar.edu (128.117.148.3)  1 ms  0 ms  0 ms
 2  vbnsr-n2.ucar.edu (128.117.2.252)  1 ms  1 ms  1 ms
 3  nist-gw.ucar.edu (192.43.244.15)  3 ms  3 ms  3 ms
 4  brdwy-ncar-T1.boulder.noaa.gov (140.172.5.254)  6 ms  3 ms  3 ms
 5  2a121-asn1-bb.boulder.noaa.gov (140.172.254.52)  4 ms  4 ms  4 ms
 6  cirrus.al.noaa.gov (140.172.240.73)  6 ms *  4 ms
laraine.unidata.ucar.edu.rkambic> ping cirrus.al.noaa.gov
cirrus.al.noaa.gov is alive   

The connection is really good between UCAR and cirrus.

So the problem lies somewhere between mscd and cirrus and as typical
nobody wants to fix it. For the short term, failover to nimbus so at least
you can get the data.  I would tell your network folks that other sites
can get cirrus, so do some more investigation.  If they can't solve the
problem, let's try to get another closer top level site. Don't get me
wrong, I'm not saying it's mscd fault. All I'm saying you are the customer
and the ISP is not providing you the connection needed to the remote site.

Robb...



> 
> Can you suggest what I should do next?
> 
> Thanks,
> 
> Tony
> 
> 
> >  
> > ****************************************************************************
> >    Anthony A. Rockwood              Metropolitan State College of Denver
> >    Meteorology Program              Dept.of Earth and Atmospheric Sciences
> >    303.556.8399                     P.O. Box 173362, Campus Box 22
> >    address@hidden                Denver, CO  80217-3362
> >    http://www.mscd.edu/~eas        http://clem.mscd.edu/~rockwooa
> >  
> > ****************************************************************************
> 
> --
> Kurt Ramsden
> UNIX Administration
> Information Technology; Technical Services
> Metropolitan State College of Denver
> e-mail: address@hidden
> Phone: (303) 556-5016
> Pager: (303) 686-5871
> FAX: (303) 556-5182
> 
> 
> 
> 
> 
> ------- End of Forwarded Message
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================