[Thinlinc-technical] HA++

[Peter Astrand]

In general, we recommend that all machines of a cluster (both VSM Servers 
and VSM Agents) are located on the same network segment. Running VSM 
Server in a DMZ and the Agents on another network does not really give any 
advantages. Any particular reason why you want to do that?

Also, splitting the cluster across the Internet is not either recommended. 
The communication protocols used inside a ThinLinc cluster are designed 
for a local network segment.

Can you tell us what you are trying to achieve? Perhaps you are looking 
for some kind of "meta cluster" or "cluster of cluster" functionality?

Best regards, 
Peter

On Mon, 21 Apr 2014, Rui Lapa wrote:

> Hello,
>
>    We are testing thinlinc with a strange scenario.
>
>    The vsmservers will be on our facilities (DMZ), and the agents will be 
> both on our facilities (LAN) and simultaneouslly on remote locations 
> (Internet).
>
>    The vsmservers have private IP's, NAT'd behind 4 possible circuits, each 
> one with it's own external IP (round-robin).
>     We have an external virtual IP load balanced to both vsmservers.
>
>    The external agents will receive a status polling (tcp/904) from either 4 
> external IP's.
>     The internal agents will be polled using their private LAN IP.
>
>    On the agent we have configured "/vsmagent/allowed_clients" mapped to the 
> 4 public IP's, but they are switching down/up/down/up!
>
>    Is this scenario possible, and where are we making a mistake?
>
> Thanks a lot,
>    Rui Lapa
> _______________________________________________
> Thinlinc-technical mailing list
> Thinlinc-technical at lists.cendio.se
> Manage your subscription:
> http://lists.cendio.se/mailman/listinfo/thinlinc-technical
>
>


---
Peter Astrand		ThinLinc Chief Developer
Cendio AB		http://cendio.com
Teknikringen 8		http://twitter.com/ThinLinc
583 30 Linkoping	http://facebook.com/ThinLinc
Phone: +46-13-214600	http://google.com/+CendioThinLinc