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

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

HI Vittorio,

> 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.

> So, can you both (Wisc. and Unidata) add an allow for:
> eth1 Link encap:Ethernet  HWaddr ac:16:2d:76:17:d5
> inet addr:*  Bcast:  Mask:
> 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


to ALLOW feed REQUESTs from


- before doing the configuration I tried to contact (via a 'notifyme'
  invocation) to your LDM at, 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


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