[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[LDM #ZJW-284386]: Fwd: ldm-relay1 problems
- Subject: [LDM #ZJW-284386]: Fwd: ldm-relay1 problems
- Date: Thu, 10 Nov 2016 13:29:52 -0700
Hi Gerry,
re:
> Clusters were supposed to remain OUTSIDE, with the relays INSIDE.
I am a bit confused about the terms being used for the pieces of the TAMU
cluster.
Correct me if I am wrong on any of the below bullets:
- the fully qualified hostname that downstreams make REQUESTs to
is idd.tamu.edu (aka ldm.tamu.edu)
This machine should be accessible by all ALLOWed downstream users,
so it should live outside of the TAMU security perimeter(?).
- Steve and I think that the machines ldm-relay[01] are responsible
for REQUESTing LDM/IDD datastreams from various upstream hosts
In our cluster, we call machines acting in this role 'accumulators'.
These machines should live outside of the TAMU security perimeter(?).
- each of the real-server backend machines of the cluster, ldm[123]
(should?) redundantly REQUEST all (ANY) datastreams from the accumulators
If your machines are setup like this, then outbound traffic on port 388
from these machines should be allowed through the TAMU security perimeter(?).
- idd.tamu.edu (aka ldm.tamu.edu) receives downstream feed REQUESTs and forwards
them to the real server backends
Does my view match how things are really setup?
re:
> Not sure how that got confused over time.
:-)
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: ZJW-284386
Department: Support LDM
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.