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

[IDD #GQL-934266]: ldm upstream feed

Hi Louis-Philippe,

> Concerning case #GQL-934266, we are trying to make this work.

We are too :-)

> I am a network analyst here at Shared Service Canada/Environment Canada,
> and Murray Rennie opened this case and the issue could not get resolved.

We have our LDM developer and senior system administrator (who is a
network engineer) involved on our side.

> I would like to know more about the issue and get a network focussed
> person on your side so we could sort this out.

We don't have anything new to add to what we sent Murray previously:

"The following log messages from downstream LDM process 7460

> 20180423T171910.686190Z idd.unidata.ucar.edu.[7460] NOTE 
> requester6.c:588:req6_new() LDM-6 desired product-class: 
> 20180423161910.686090 TS_ENDT {{NEXRAD2, "KA.."},{NONE, 
> "SIG=12b7c3d883511dcf117f085ba231ad9b"}}
> 20180423T171911.009346Z idd.unidata.ucar.edu.[7460] NOTE 
> requester6.c:311:make_request() Upstream LDM-6 on idd.unidata.ucar.edu. is 
> willing to be a primary feeder
> 20180423T171911.225490Z idd.unidata.ucar.edu.[7460] NOTE 
> svc_tcp.c:358:readtcp() EOF on socket 6

show that the downstream LDM process saw its connection to the upstream LDM
process disconnect after only about 0.2 seconds. Our upstream LDM processes
don't do that. The cause is likely due to a third party mimicking the upstream
LDM process and sending a TCP reset (RST) packet to the downstream LDM process.
We've seen firewalls and intrusion detection/prevention systems do this."

If you have any questions, please ask!


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: GQL-934266
Department: Support IDD
Priority: Normal
Status: Closed
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.