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

20041129: IDD feeds from atm.geo.nsf.gov

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: 20041129: IDD feeds from atm.geo.nsf.gov
  • Date: Mon, 29 Nov 2004 12:29:22 -0700
>From: "Patrick L. Francis" <address@hidden>
>Organization: Bowling Green State University
>Keywords: 200411291316.iATDGZlI028344 IDD

Hi Patrick,

>strange things are afoot at the circle K ...
>
>atm to weather/unidata.bgsu.edu showing monster latencies... internal and 
>oar.net
>connectivity appears OK.
>
>http://my.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?HDS+unidata.bgsu.edu

I looked at all of the feeds you are getting from atm.geo.nsf.gov
(namely, HDS, IDS|DDPLUS, and UNIWISC) and see the exact same latency
signature each one.  The signatures are so consistent, that I am
assuming that your ~ldm/etc/ldmd.conf request line is for 'WMO' and
looks something like:

request WMO     ".*"    atm.geo.nsf.gov

A 'traceroute' from atm.geo.nsf.gov shows a big latency in simple ping
packets:

% traceroute unidata.bgsu.edu
traceroute to unidata.bgsu.edu (129.1.112.220), 30 hops max, 40 byte packets
 1  colima.nsf.gov (198.181.231.1)  12 ms  15 ms  13 ms
 2  arlg-nsf.maxgigapop.net (206.196.177.137)  7 ms  3 ms  7 ms
 3  dcne-so3-0-0.maxgigapop.net (206.196.178.42)  8 ms  15 ms  14 ms
 4  abilene-rtr.maxgigapop.net (206.196.177.2)  7 ms  9 ms  4 ms
 5  nycmng-washng.abilene.ucaid.edu (198.32.8.84)  12 ms  17 ms  14 ms
 6  chinng-nycmng.abilene.ucaid.edu (198.32.8.82)  36 ms  28 ms  27 ms
 7  iplsng-chinng.abilene.ucaid.edu (198.32.8.77)  248 ms  243 ms *
 8  clmbq-r2-po0-0.bb.oar.net (192.88.192.133)  35 ms  34 ms  34 ms
 9  dytnq-r3-at1-0s16.bb.oar.net (192.88.191.101)  37 ms  37 ms  38 ms
10  bgsu2-r1-at2-0s103.cpe.oar.net (192.88.192.174)  60 ms  61 ms  61 ms
11  129.1.8.252 (129.1.8.252)  773 ms  737 ms  711 ms
12  129.1.8.125 (129.1.8.125)  749 ms  806 ms  815 ms
13  * * *
14  * * *
15  unidata.bgsu.edu (129.1.112.220)  858 ms  796 ms  741 ms

The bottleneck appears to be on the BGSU campus:

% awhois 129.1.8.252

OrgName:    Bowling Green State University 
OrgID:      BGSU
Address:    University Computer Services
Address:     Math Science Building
City:       Bowling Green
StateProv:  OH
PostalCode: 43403
Country:    US

NetRange:   129.1.0.0 - 129.1.255.255 
CIDR:       129.1.0.0/16 
NetName:    BGSU
NetHandle:  NET-129-1-0-0-1
Parent:     NET-129-0-0-0-0
NetType:    Direct Assignment
NameServer: NS1.BGSU.EDU
NameServer: NS2.BGSU.EDU
NameServer: NS1.OAR.NET
NameServer: NS2.OAR.NET
Comment:    
RegDate:    1987-06-05
Updated:    2001-01-29

TechHandle: KS770-ARIN
TechName:   Strickland, Kent 
TechPhone:  +1-419-372-2911
TechEmail:  address@hidden 

# ARIN WHOIS database, last updated 2004-11-28 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.

I would contact your campus network folks and initiate an inquiry
about the large latencies seen with 'traceroute'.  I would also
do a 'traceroute' from unidata.bgsu.edu to atm.geo.nsf.gov to see
if the problem at 129.1.8.252 is bidirectional:

% traceroute atm.geo.nsf.gov

Please let us know the results of your 'traceroute'.

Cheers,

Tom
--
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.