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

[TIGGE #WNN-399573]: [Fwd: Re: Re: Almost ready to do the data transfer test]

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: [TIGGE #WNN-399573]: [Fwd: Re: Re: Almost ready to do the data transfer test]
  • Date: Tue, 15 Aug 2006 10:34:30 -0600
Manuel,

> We are testing LDM connectivity between ECMWF and CMA and we seem to
> have problems. I can ldmping CMA's LDM from ECMWF but it seems the
> opposite doesn't work. Do you have any hint ?
> 
> I include YangXin's e-mail below...
> 
> Thanks in advance,
> Manuel

It appears that the LDM at the ECMWF is unable to translate the CMA
IP address into a hostname.  Is this correct?  What are the ALLOW
entries in the ECMWF LDM's configuration-file for the CMA LDM-s?
If they are all hostname-based, then a CMA LDM will be unable to
connect.

The best solution would be to fix the IP-address-to-hostname
translation mechanism used by ECMWF.  This is beyond the scope of
the LDM: you'll have to involve your networking administrators.

A workaround solution would be to add IP-based ALLOW entries for
the CMA LDM-s to the LDM configuration-file at the ECMWF.  For
example,

    ALLOW ANY ^210\.73\.54\.[0-9]{1,3}$

This would allow a connection by any LDM running on a host whose IP
address lies in the inclusive range from 210.73.54.0 to 210.73.54.255.

Having both types of ALLOW entries will not affect the performance of
the LDM -- so you might try that.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: WNN-399573
Department: Support IDD TIGGE
Priority: Normal
Status: Closed