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

[LDM #NDJ-862794]: Problems accessing data from Southern Region HQ LDM

Doug,

> We have an allow any in our include file:
> 
> ncepidp.conf:allow    ANY    140.90.100.144    # vm-lnx-ncodf1.ncep.noaa.gov
> ncepidp.conf:allow    ANY    140.90.100.145    # vm-lnx-ncodf2.ncep.noaa.gov
> ncepidp.conf:allow    ANY    140.90.100.153    #
> vm-lnx-ncodfdev.ncep.noaa.gov

So, you're not using the OK-pattern and NOT-pattern fields. Well, that shoots
that hypothesis down.

> From my LDM server I cannot connect to TCP port 388. LDMPING times out
> and a telnet to port 388 times out.

You mean a notifyme(1) on the local host can't connect to the LDM server
on the local host?!

> The 140.90.100.153 server can
> connect to me on port 388 but I cannot answer requests on port 388.

What do you mean by "I cannot answer requests on port 388"?

> A
> packet trace show the following:
> 
> 120.779236 216.38.81.29 -> 140.90.100.153 STUN 110 ChannelData TURN Message
> 120.837055 140.90.100.153 -> 216.38.81.29 STUN 94 ChannelData TURN Message
> 120.837078 216.38.81.29 -> 140.90.100.153 TCP 66 unidata-ldm > 55656
> [ACK] Seq"1 Ack 1 Win 4 Len=0 TSvalw0113915 TSecr 76576943
> 
> When the downstream server requests data from me are the requests
> answered on port 388 or on the ephemeral port. If on the ephemeral port
> do we need any connection tracking enable to keep the connection alive?

A downstream LDM connects to port 388 on the host running an LDM server.
The server then forks an upstream LDM process that uses the same connection
to send data-products to the downstream LDM. So the source port of the 
data-products will be 388 and the destination port with be an ephemeral
on on the downstream host.

> Thanks,
> Doug Gaer
> NWS, SRH
> 
> --
> Douglas Gaer, ITO, SRH, 817-978-1100 x.114

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: NDJ-862794
Department: Support LDM
Priority: Normal
Status: Closed