TightGate-Pro

Dediziertes Remote-Controlled Browser System
zum Schutz vor Gefahren aus dem Internet

Automatisch generierter Auszug aus dem Administrationshandbuch

Datum: 11.04.2019

Herausgeber:

m-privacy GmbH

Technische Redaktion

Werner-Voß-Damm 62

12101 Berlin

Fon: +49 30 243423-34

support@m-privacy.de

www.help.m-privacy.de

Allgemeine Hinweise zu diesem Handbuch

Alle Materialien und Ausführungen wurden mit Sorgfalt erarbeitet und zusammengestellt. Den­noch sind Fehler nicht auszuschließen. Die m-privacy GmbH übernimmt keine Haftung für Schäden, die aus Unrichtigkeit einzelner Angaben entstehen.

Im Sinne einer raschen Orientierung und zur Vermeidung von Sicherheitsrisiken werden besonders wichtige Aspekte durch wiederkehrende Stichworte gekennzeichnet. Diese sind:

Hinweis
Unter diesem Stichwort werden nützliche Details zur rationellen Verwendung von TightGate-Pro er­läutert.

Achtung
Unter diesem Stichwort erfolgen Hinweise zur Problemvermeidung bzw. zur Vorbeugung von Betriebs­störungen bei TightGate-Pro.

Warnung
Unter diesem Stichwort erfolgen Hinweise auf mögliche Fehler bei der Konfiguration und Verwendung von TightGate-Pro, die weitreichende Sicherheitsrisiken bergen oder zu schwerwiegenden Betriebs­störungen führen können.

Inhaltsverzeichnis

Starting up a TightGate-Pro cluster

The following instructions describe the procedure for starting a TightGate-Pro cluster with external Ceph data storage. The start-up procedure must be followed so that the cluster components are optimised and the cluster is ready for use as quickly as possible.

The startup is carried out in several steps:

Step 1: Booting the TightGate-Pro time server

The first step is to start the TightGate-Pro server that serves as the time server for the Ceph servers. This should already be known, usually the first TightGate-Pro server is used for this. The TightGate-Pro will start, but cannot connect to the cluster as it is not yet running. This is fine at this stage, only the service is required as a timer. The integration into the cluster will then take place at a later time.

The determination of the TightGate-Pro time server used by the Ceph servers can be determined on a running Ceph system by running the following command as administrator root in the console with the following command: cat /etc/ntp.conf | grep server
The output of the command lists the IP addresses of the TightGate-Pro servers that are used as time servers.

Step 2: Booting the Ceph servers

To activate data storage for TightGate-Pro, all Ceph servers should now be switched on at the same time if possible. These start up and are ready when a login prompt is displayed on the console. Once all Ceph servers have been started, check that all Ceph servers have connected and that the cluster is running properly. The check is carried out as follows:

Login as administrator root on the console of the first Ceph server.

Execute the command ceph osd tree

The output of the command shows the status up the cluster has started successfully.

Note! The Ceph servers need some time after a restart to bring each other to the same data storage status. If the status is not upyou can start troubleshooting.

Step 3: Booting the TightGate-Pro server

Once the Ceph cluster is running and has found itself, the TightGate-Pro servers are started one after the other. Once they have all started and connected to the cluster, the TightGate-Pro that was started in step 1 is restarted (reboot). When booting the TightGate-Pro servers, the following message can be observed during the boot process, provided the connection to the Ceph servers is successful (the IPs of the Cephs are exemplary):

Mounting Ceph from /home/user: trying monitors: 192.168.111.101:6789, 192.168.111.102:6789, 192.168.111.103:6789 mounted ... ready!
Mounting Ceph from /home/backuser/backup: trying monitors: 192.168.111.101:6789, 192.168.111.102:6789, 192.168.111.103:6789 mounted ... ready!

Step 4: Function check

Once all TightGate-Pro servers have been started up and connected in the cluster, the correct status can be checked as follows:

Login with the TightGate-Viewer as a normal user at the first TightGate-Pro and call up the following URL in the Firefox browser: http://localhost/

In the login window that appears with the user name status and the corresponding password from the password list.

On the status page on the right, click on the menu item Cluster status menu item on the right. The cluster status is displayed for all TightGate-Pro servers and their services. If all TightGate-Pro servers are available and the status for all systems is green, the start is successfully completed.