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

20050203: toplevel IDD relay atm.geo.nsf.gov once again accessible (cont.)



>From: Tom McDermott <address@hidden>
>Organization: SUNY Brockport
>Keywords: 200502031338.j13DcTv2013547 IDD atm

Hi Tom,

>Please be advised that nothing has changed regarding the accessibiliity of 
>the ldm server on atm from our site (vortex.esc.brockport.edu)  since OZ 
>on Sunday when this problem arose.

 ...

>So it would seem that not all aspects of this problem have been solved.

Thanks for reporting this.  I am under the impression that this has to
do with a routing change made by the NSF/ATM network folks that affects
connections to atm.geo.nsf.gov over the commodity Internet (as you
speculate below).  The reason the NSF folks made a change was related
to the LDM traffic using up all of their bandwidth when their I2
connection goes down.  It looks like they went too far in their routing
changes.  We will work with the NSF folks to rectify this.

Cheers,

Tom

>Throughout this period atm has responded to pings:
>
>[920] vortex% ping atm.geo.nsf.gov
>atm.geo.nsf.gov is alive
>
>but not to ldmpings:
>
>[921] vortex% ldmping atm.geo.nsf.gov
>Feb 03 13:17:45      State    Elapsed Port   Remote_Host 
>rpc_stat
>Feb 03 13:17:55 SVC_UNAVAIL  10.001698    0   atm.geo.nsf.gov 
>h_clnt_create(atm.geo.nsf.gov): Timed out while creating connection
>
>It also has been evident throughout this period that some (upstream) sites 
>have been able to connect to atm, as witness the following entries from 
>the 13Z stats file from yesterday morning on our server:
>
>20050202135837     HDS atm.geo.nsf.gov_v_f5.aos.wisc.edu         48 
>985347       5.47   28@4
>100 20050202135841
>20050202135958     HDS atm.geo.nsf.gov_v_gusher.atmos.albany.edu 
>9456  119564809       3.4
>7   28@4159 20050202135959
>20050202133126 IDS|DDPLUS atm.geo.nsf.gov_v_f5.aos.wisc.edu         27 
>38386       2.19
>5@3126 20050202133130
>20050202135947 IDS|DDPLUS atm.geo.nsf.gov_v_gusher.atmos.albany.edu 
>17719    9834073
>0.84   13@0030 20050202135948
>20050202135609 FNEXRAD atm.geo.nsf.gov_v_idd.unidata.ucar.edu          4 
>17373      17.12
>  22@4757 20050202135616
>20050202135752 FNEXRAD atm.geo.nsf.gov_v_unidata2.ssec.wisc.edu        100 
>715572      14.33
>    25@2544 20050202135757
>
>This led me to suspect that this might be a routing problem (perhaps sites 
>on Internet 2 can connect, others not), except that a route does exist 
>from our host to atm:
>
>[927] vortex% traceroute atm.geo.nsf.gov
>traceroute to atm.geo.nsf.gov (198.181.231.53), 30 hops max, 40 byte 
>packets
>  1  137.21.88.254 (137.21.88.254)  0.741 ms  0.582 ms  0.428 ms
>  2  137.21.1.244 (137.21.1.244)  0.842 ms  0.659 ms  0.982 ms
>  3  well1.uwave.brockport.edu (137.21.1.254)  2.400 ms  2.496 ms  2.135 ms
>  4  64-132-176-201.gen.twtelecom.net (64.132.176.201)  3.719 ms  2.584 ms 
> 2.982 ms
>  5  66.192.240.144 (66.192.240.144)  3.123 ms  3.326 ms  2.522 ms
>  6  66.192.244.62 (66.192.244.62)  28.210 ms  27.423 ms  27.534 ms
>  7  168.215.54.30 (168.215.54.30)  28.525 ms  27.727 ms  27.965 ms
>  8  sl-gw22-chi-6-3.sprintlink.net (144.223.21.145)  34.291 ms  35.045 ms 
> 34.352 ms
>  9  sl-bb21-chi-4-1.sprintlink.net (144.232.10.13)  34.231 ms  33.242 ms 
> 34.369 ms
>10  sl-bb22-nyc-15-0.sprintlink.net (144.232.9.148)  35.016 ms  33.187 ms 
>33.181 ms
>11  sl-bb21-nyc-14-0.sprintlink.net (144.232.7.101)  33.434 ms  33.216 ms 
>32.719 ms
>12  sl-bb27-pen-12-0.sprintlink.net (144.232.20.97)  35.327 ms  35.527 ms 
>34.879 ms
>13  sl-gw42-pen-9-0.sprintlink.net (144.232.5.82)  35.498 ms  35.355 ms 34.758 
>ms
>14  sl-natio20-1-0-0.sprintlink.net (160.81.65.26)  40.813 ms  40.160 ms 
>40.931 ms
>15  63.173.108.130 (63.173.108.130)  40.445 ms  40.348 ms  40.855 ms
>16  atm.geo.nsf.gov (198.181.231.53)  41.771 ms  40.517 ms  69.818 ms>

>So it would seem that not all aspects of this problem have been solved.
>
>Tom
>-----------------------------------------------------------------------------
>Tom McDermott                          Email: address@hidden
>Systems Administrator                  Phone: (585) 395-5718
>Earth Sciences Dept.                   Fax: (585) 395-2416
>SUNY College at Brockport
>
>
>On Wed, 2 Feb 2005, Unidata Support wrote:
>
>>> From: Unidata User Support <address@hidden>
>>> Organization: Unidata Program Center/UCAR
>>> Keywords: 200502010020.j110KAv2006748 IDD
>>
>> Sites receiving IDD feeds from atm.geo.nsf.gov:
>>
>> IDD relay from atm.geo.nsf.gov was re-established early yesterday
>> (Tuesday) morning.  We purposefully did not announce the machine's
>> return to service while we worked on a number of items that caused us
>> to stop and restart the LDM several times.  We will be installing
>> needed OS patches that will necessitate a machine reboot in the coming
>> days, so please don't be suprised by the machine disappearing for a
>> short period.
>>
>> Any sites that switched from atm.geo.nsf.gov to their failover can
>> now switch back.
>>
>> Also, any sites currently feeding from emo.unidata.ucar.edu should
>> switch to feed from idd.unidata.ucar.edu as soon as possible.  emo will
>> be removed from relay service in the near timeframe, so please switch
>> now so you won't lose data service.  Thanks!
>>
>> Sorry for the inconveniences...
>>
>> Tom Yoksas
>> ****************************************************************************
>> Unidata User Support                                    UCAR Unidata Program
>> (303)497-8643                                                  P.O. Box 3000
>> address@hidden                                   Boulder, CO 80307
>> ----------------------------------------------------------------------------
>> Unidata WWW Service              http://my.unidata.ucar.edu/content/support 
>> ****************************************************************************
>>
>
--
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.