Dell Wyse Enhanced Ubuntu Linux T50 Instrukcja Użytkownika Strona 43

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 220
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 42
Chapter 6. High Availability (HA)
Both machines have an unique hostname and an unique IP address, but there is also a third IP address
that is active only on the node currently responsible for the VSM server service. This is the so called HA
address, the address the clients are connecting to.
6.2. Configuration of ThinLinc for HA Operations
In this section, we describe how ThinLinc is configured for High Availability.
6.2.1. Installation of a New HA Cluster
In this section, we will describe how to setup a new HA cluster. In the examples we will use a primary
node with the hostname tlha-primary and IP address 10.0.0.2, a secondary node with the hostname
tlha-secondary and IP address 10.0.0.3, and a HA IP address of 10.0.0.4 with the DNS name tlha.
1. Begin by installing ThinLinc as described in Chapter 3 on both nodes.
2. Both nodes in the HA cluster must have the same SSH host key. Copy /etc/ssh/ssh_host_
*
from the primary host to the secondary host, and restart ssh on the secondary host.
3. Install and configure the system-level high-availability software, for example the software provided
by the Linux-HA project, which can be found at http://linux-ha.org. This and other high-availability
software may also be provided as part of your distribution, so check for the solution which best fits
your requirements before proceeding.
4. Configure the system’s high-availability software to watch the status of the other machine via the
network, and to enable the HA IP address 10.0.0.4 on the active node. The machine with the
hostname tlha-primary should normally be active.
5. Configure each VSM agent to allow privileged operations both from tlha-primary and
tlha-secondary:
[root@agent root] tl-config ’/vsmagent/allowed_clients=tlha-primary tlha-secondary’
Also, set the master_hostname to the DNS name of the HA interface:
[root@agent root] tl-config /vsmagent/master_hostname=tlha
Restart all VSM agents after changing the configuration values.
If the tl-config command is not found, logout and login again in order to let the login scripts add
/opt/thinlinc/bin and /opt/thinlinc/sbin to the PATH.
6. Verify operations of VSM Server on both nodes. Make sure you can start the VSM server properly
on both hosts, and connect to the respective hosts when VSM server is running (i.e., it should be
possible to connect, using tlclient, to both tlha-primary and to tlha-secondary).
Both nodes should be configured with the whole list of VSM agents in
/vsmserver/terminalservers.
33
Przeglądanie stron 42
1 2 ... 38 39 40 41 42 43 44 45 46 47 48 ... 219 220

Komentarze do niniejszej Instrukcji

Brak uwag