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

[IDD #MUN-941483]: 20151107: COD Comcast address for LDM feed

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: [IDD #MUN-941483]: 20151107: COD Comcast address for LDM feed
  • Date: Sat, 07 Nov 2015 09:08:37 -0700
HI Vittorio,

re:
> Given our incredible latencies using CONDUIT for our 12 UTC products,
> we conducted some internal tests and found that the problem appears
> to be in our hardware infrastructure associated with 1 of our 2 campus
> internet providers.  Thus, we are going to try our Comcast feed as the
> sole provider for our climate server and see if that resolves things as
> a temporary fix until our hardware can be updated.

OK.  I am not confident that running a high volume LDM/IDD feed through
COMCAST will work given their track record of interrupting connections
that they don't like.  But, this is worth a try.

re:
> So, can you both (Wisc. and Unidata) add an allow for:
> 
> eth1 Link encap:Ethernet  HWaddr ac:16:2d:76:17:d5
> inet addr:107.0.209.213*  Bcast:107.0.209.223  Mask:255.255.255.240
> UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> RX packets:771283 errors:0 dropped:0 overruns:0 frame:0
> TX packets:185671 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1090412278 (1.0 GB)  TX bytes:12006040 (12.0 MB)
> Interrupt:36
> 
> to your conf files so we can test this out?  This will be our new test
> static IP for climate.cod.edu.

OK.  I have setup our primary and backup IDD relay clusters

idd.unidata.ucar.edu
iddb.unidata.ucar.edu

to ALLOW feed REQUESTs from 107.0.209.213

Comment:

- before doing the configuration I tried to contact (via a 'notifyme'
  invocation) to your LDM at 107.0.209.213, but it appears that the connection
  (to port 388) is being blocked by a firewall somewhere

  For troubleshooting purposes, it would be useful if we (machines in the
  .unidata.ucar.edu) could make feed REQUESTs to the LDM running
  on 107.0.209.213.

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: MUN-941483
Department: Support IDD
Priority: Normal
Status: Closed