[LDM #PFH-426407]: LDM Connection

Hi,

re:
> Thanks for getting back to me.

No worries.

re:
> I assume our security is blocking the new address 

We do too, but the IP address is not new.

We changed the DNS for the new LVS cluster director to have the same IP
address as the cluster directory had before the DNS change: 128.117.130.3.
At the same time, we changed the DNS for the old cluster (which is still
running, but will be taken down just in advance of the power down at the
location where it is housed) to be 128.117.135.3.

re:
> - Which is 128.117.130.3

That is correct, but it is the same IP address as before the change.
It is for this reason that we are thinking that there is likely to be
a hardwired outbound firewall rule in place there.

You should test to see if you can get to our new cluster and old
cluster as follows:

<as 'ldm' on your LDM machine>

notifyme -vl- -f ANY -h idd.unidata.ucar.edu     <- new cluster

notifyme -vl- -f ANY -h 128.117.135.3            <- old cluster

NB:

The old cluster (which is only accessible by IP address) will
continue to stay up until either sometime on Sunday or very
early on Monday morning.  Getting NEXRAD2 data flowing again
to your site by adding/changing your REQUEST(s) to the IP
of our old cluster should only be done to get things working
while you sort out the (hypothesized) firewall (?) issue.

Better yet, you should, after sorting out whatever is blocking
your REQUEST attempt(s), setup redundant feeds of the data
feed(s) you want.  This way, if one upstream goes down, you
should still be OK if the other one is up.

Other clusters you should be able to feed from (assuming
that there is reverse DNS for your machine) are:

iddb.unidata.ucar.edu
idd.aos.wisc.edu
idd.meteo.psu.edu


> Correct?
> 
> 
> [ldm@ldm-prod etc]$ notifyme -vl- -f ANY -h idd.unidata.ucar.edu
> 20210722T003602.841212Z notifyme[16934] NOTE notifyme.c:385:main() Starting
> Up: idd.unidata.ucar.edu: 20210722003602.840115 TS_ENDT {{ANY, ".*"}}
> 20210722T003602.841386Z notifyme[16934] NOTE ldm5_clnt.c:460:forn5() LDM-5
> desired product-class: 20210722003602.840115 TS_ENDT {{ANY, ".*"}}
> 20210722T003602.847198Z notifyme[16934] INFO error.c:236:err_log()
> Resolving idd.unidata.ucar.edu to 128.117.130.3 took 0.005555 seconds
> ^C20210722T003608.319804Z notifyme[16934] NOTE notifyme.c:66:cleanup()
> exiting
> 
> 
> 
> 
> address@hidden> wrote:
> 
> > Hi,
> >
> > re:
> > > Support - Lost connection to idd.unidata.ucar.edu    ????
> > >
> > > ldmping idd.unidata.ucar.edu
> > > 20210721T154111.953548Z ldmping[31688] INFO ldmping.c:51:print_label()
> > State    Elapsed Port   Remote_Host           rpc_stat
> > > 20210721T154111.957809Z ldmping[31688] INFO error.c:236:err_log()
> > Resolving idd.unidata.ucar.edu to 128.117.130.3 took 0.003476 seconds
> > > 20210721T154121.958245Z ldmping[31688] ERROR ldmping.c:75:print_hstat()
> > SVC_UNAVAIL  10.004107    0   idd.unidata.ucar.edu  h_clnt_create(
> > idd.unidata.ucar.edu): Timed out while creating connection
> >
> > Yesterday evening at 6 MDT (Wednesday 0Z) the DNS for the
> > idd.unidata.ucar.edu
> > cluster was changed to point at a new, more robust cluster housed at the
> > NCAR Mesa Lab in Boulder, CO.  The reason for the change was an impending
> > week
> > long power down at the NCAR-Wyoming Supercomputer Center in Cheyenne, WY,
> > that will begin this coming Monday at 6 am.  This change was announced to
> > the
> > address@hidden email list a day before the change.  If you or
> > someone
> > else at NCDC is not subscribed to the ldm-users email list, it would be a
> > good
> > idea to subscribe so that you will be informed of changes like this in the
> > future.
> >
> > One can (un)subscribe to any of the email lists that we maintain online at:
> >
> > https://www.unidata.ucar.edu/support/index.html#mailinglists
> >
> > The output from your 'ldmping' invocation shows that the IP address for
> > the new instance of the idd.unidata.ucar.edu is resolvable, so the
> > inability
> > to connect to the LDM on idd.unidata.ucar.edu is surprising.
> >
> > Can you check to see if the situation continue by running the following:
> >
> > <as 'ldm' on your LDM machine>
> > notifyme -vl- -f ANY -h idd.unidata.ucar.edu
> >
> > Since the real-server backends of the idd.unidata.ucar.edu relay cluster
> > are configured with blanket ALLOWs for machines whose domain resolves to
> > '.gov', there should be nothing on our end that is (was?) causing the
> > problem you have reported.
> >
> > 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: PFH-426407
> > 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.
> >
> >
> >
> 
> --
> Michael Urzen
> IT Specialist
> National Climatic Data Center
> address@hidden
> 828-271-4089
> 
> 

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: PFH-426407
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.