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

20050203: IDD - ATM appears down (cont.)

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: 20050203: IDD - ATM appears down (cont.)
  • Date: Thu, 03 Feb 2005 17:27:42 -0700
>From: John Meyers <address@hidden>
>Organization: MoS
>Keywords: 200502040019.j140JJv2027882 IDD

Hi John,

>I saw the message in ldm-users, but we STILL cannot connect to atm.  The 
>same problem is persisting - we have ICMP connectivity, but ldmping 
>fails and packet traces show nothing coming back, as if the ldm port is 
>being filtered.

Here is the story:  all connections on sprintlink to NSF have been
disabled by the NSF admins, and these will not return.  The reason
for this is that the bandwidth usage of the IDD exceeds the capacity
of the NSF sprintlink connection, so when atm drops off of Internet2,
nobody at NSF can get any work done.  As you might well imagine, this
does not sit well with NSF folks.  So, no IDD connections will be allowed
through their backup sprintlink connection.

Given this, please direct your data requests to idd.unidata.ucar.edu
until we can identify an eastcoast server to feed you.

I apologize for not getting back to you on this early today, but I
have been helping put on an LDM/IDD workshop here at UCAR.

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.