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

[CONDUIT #ILM-125352]: Change to data path on NCEPs conduit

Hi Carissa,

re:
> I don't seem to have a thread with any UI folks on it. Can you please let
> them know that we need them to test to see if the connection works to
> conduit3.
> 
> 140.90.101.93

I will contact the LDM/IDD admin at UIllinois this morning.  For reference,
his contact info is:

David Wojtowicz <address@hidden>

re:
> Thanks,

No worries.

FYI: by accident we discovered that at least some of the machines that
comprise the idd.unidata.ucar.edu IDD relay cluster are connected to
Cisco switches that have sets of ports whose aggregate outbound bandwidth
is limited to 1 Gbps.  It turns out that this has occasionally been causing
latency problems in data relayed by us, and would, if left unaltered, limited
our ability to relay the 0.25 degree GFS data that is to be added to CONDUIT.
Our system administrator, Mike Schmidt, has been working with the NCAR/UCAR
network folks to get all of our idd.unidata.ucar.edu real-server backend
machines moved over to routers that will allow for at least 2 Gbps per
connection.  This may seem like it might not be important, but a snapshot
of the aggregate volume data flowing being relayed by us is currently
hovering at about 4.2 Gbps... logs of data :-)

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: ILM-125352
Department: Support CONDUIT
Priority: Normal
Status: Closed