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

20050131: 20050131: IDD - ATM appears down



>From: John Meyers <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200502010025.j110Plv2007379

>Unidata Support wrote:
>
>>>From: "John Meyers" <address@hidden>
>>>Organization: Museum of Science
>>>Keywords: 200501312248.j0VMmQ1H001464 LDM IDD atm
>> 
>> 
>> 
>> Strange...
>> When I first saw your email, I was logged onto atm and it was servicing
>> 69 downstream connections.  I was able to ldmping it from machines here
>> at the UPC and I could ldmping your machine from it.  Just to make sure
>> that there was nothing systematically wrong, I just stopped and
>> restarted its LDM.  After doing this, now machines can connect to the
>> LDM.
>
>It gets stranger.  I still cannot connect.

I just saw a one word omission in my earlier email.  What I meant to
say was:

After doing this, now _NO_ machines can connect to the LDM.

The problem is at atm or in a router that controls traffic to/from
atm.  We are seeing exceedingly strange problems like only being able
to connect with one SSH while ADDE service is totally unaffected.  We
are attempting to contact folks back at NSF/ATM to see if there is
something going on with their router/router rules.  As I noted in the
email I sent to ldm-users, folks should switch to their failover feed
site(s), or, if those site(s) are fed by atm, they can failover to
idd.unidata.ucar.edu.

Sorry for the problems.  This one is mystifying us at the moment.

Tom

>I've tcpdumped an ldmping 
>connection, and I am not getting a single packet back from atm.  I've 
>verified two directional connectivity by both ICMP and HTTP -- both 
>work.  Here's the tcpdump:
>
>19:16:45.872208 IP 10.1.3.29.48681 > atm.geo.nsf.gov.ldm: S 
>270205720:270205720(0) win 5840 <mss 1460,sackOK,timestamp 1844015650 
>0,nop,wscale 2>
>19:16:48.870933 IP 10.1.3.29.48681 > atm.geo.nsf.gov.ldm: S 
>270205720:270205720(0) win 5840 <mss 1460,sackOK,timestamp 1844018650 
>0,nop,wscale 2>
>19:16:54.870014 IP 10.1.3.29.48681 > atm.geo.nsf.gov.ldm: S 
>270205720:270205720(0) win 5840 <mss 1460,sackOK,timestamp 1844024650 
>0,nop,wscale 2>
>19:17:45.874332 IP 10.1.3.29.33266 > atm.geo.nsf.gov.sunrpc: UDP, length 40
>19:17:50.874606 IP 10.1.3.29.33266 > atm.geo.nsf.gov.sunrpc: UDP, length 40
>19:18:20.878988 IP 10.1.3.29.48682 > atm.geo.nsf.gov.ldm: S 
>379531552:379531552(0) win 5840 <mss 1460,sackOK,timestamp 1844110672 
>0,nop,wscale 2>
>19:18:23.878494 IP 10.1.3.29.48682 > atm.geo.nsf.gov.ldm: S 
>379531552:379531552(0) win 5840 <mss 1460,sackOK,timestamp 1844113672 
>0,nop,wscale 2>
>19:18:29.877580 IP 10.1.3.29.48682 > atm.geo.nsf.gov.ldm: S 
>379531552:379531552(0) win 5840 <mss 1460,sackOK,timestamp 1844119672 
>0,nop,wscale 2>
>
>[ldm@wxserver1 ~]$ ldmping atm.geo.nsf.gov
>Feb 01 00:16:45      State    Elapsed Port   Remote_Host           rpc_stat
>Feb 01 00:16:55 SVC_UNAVAIL  10.000626    0   atm.geo.nsf.gov 
>h_clnt_create(atm.geo.nsf.gov): Timed out while creating connection
>Feb 01 00:17:20  ADDRESSED   0.000002    0   atm.geo.nsf.gov 
>h_clnt_create(atm.geo.nsf.gov): Timed out while creating connection
>Feb 01 00:17:55      NAMED  10.000585    0   atm.geo.nsf.gov  can't 
>contact portmapper: RPC: Timed out
>Feb 01 00:18:30 SVC_UNAVAIL  10.003503    0   atm.geo.nsf.gov 
>h_clnt_create(atm.geo.nsf.gov): Timed out while creating connection
>
>
>John
>
--
**************************************************************************** <
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.