In critical and/or high-loaded environments, it is possible that the load needs to be distributed among several machines and to be sure that if any Pandora FMS component fails, the system remains online.
Pandora FMS has been designed to be modular but it is also designed to work in collaboration with other components and to be able to assume the load of those components that failed.
Obviously, agents are not redundant. The solution is to redundate critical systems -regardless of whether they have Pandora FMS agents running or not- and thus redundate the monitoring of these systems.
High Availability (**HA**) can be used in several scenarios:
+
いくつかの場面において、次のような高可用性 (**HA**) 構成が可能です。
+
* Data server.
+
* Network Servers, WMI, Plugin, Web, Prediction, Recon, and similar.
+
* Database (**BBDD**).
+
* Pandora FMS web console.
+
* データサーバ
+
* ネットワークサーバ、WMI、プラグイン、Web、予測、自動検出など
+
* データベース
+
* Pandora FMS Web コンソール
+
<wrap #ks2 />
===== データサーバの HA =====
===== データサーバの HA =====
-
最も簡単な方法は、エージェントに実装されている HA を使用することです(プライマリが応答しない場合は代替サーバーに接続できます)。 ただし、データサーバはポート 41121 をサポートし、標準の TCP ポートであるため、通常の TCP サービスのバランシングまたはクラスタリングを可能にする商用ソリューションを使用することができます。
-
Pandora FMS データサーバでは、(異なるホスト名およびサーバ名で)設定された 2つの Pandora FMS データサーバを利用する必要があります。それぞれに tentacle サーバーを設定する必要があります。 各マシンは異なる IP アドレスを持ちます。 外部バランサを使用する場合、バランサにエージェントからのデータ送信用の接続 IP アドレス(VIP)を割り当てます。
+
* For Pandora FMS data server you need to build two machines with a Pandora FMS data server configured (and different hostname and server name).
+
* A Tentacle server must be configured in each of them.
+
* Each machine will have a different IP address.
+
* If you are going to use an external balancer, it will provide a single IP address to which the agents will connect to send their data.
+
* In the case of using the HA mechanism of the agents, there will be a small delay in sending data, since at each agent execution, it will try to connect with the primary server, and if it does not answer, it will try to connect with the secondary server (if it was configured this way).
* 外部バランサーを使用する場合は、エージェントがデータを送信するために接続するための単一の IP アドレスが提供されます。
+
* エージェントの HA メカニズムを使用する場合は、エージェントの実行ごとにプライマリサーバに接続しようとし、応答がない場合はセカンダリサーバに接続しようとするため (そのように設定されている場合)、データの送信に若干の遅延が発生します。
-
Pandora FMS データサーバの設定を変更する必要はありません。それぞれのサーバに別々の名前を設定してさえいえれば、サーバの状態ビューでいずれかがダウンしていることがわかり便利です。Pandora FMS データモジュールは、いずれかのサーバで処理することができます。事前のサーバ指定は不要です。簡単に HA 構成がとれるように設計されています。
+
If two data servers are to be used and both handle remote policies, collections, and configurations, key directories must be shared so that all instances of the data server can read and write to these directories. Consoles must also have access to these shared directories.
-
エージェントの HA メカニズムを使用する場合は、データの送信にわずかな遅延があります。これは、エージェントの実行ごとにプライマリサーバとの接続を試みるためです。応答しない場合 セカンダリに対してこれを行います(設定されている場合)。これについては、次の "ソフトウエアエージェントでのバランシング" で説明します。
It is important to only share subdirectories within ''data_in'' and not ''data_in'', itself as it will negatively affect server performance.
-
<code>
+
</WRAP>
-
# Secondary server configuration
+
-
# ==============================
+
-
# If secondary_mode is set to on_error, data files are copied to the secondary
+
-
# server only if the primary server fails. If set to always, data files are
+
-
# always copied to the secondary server
+
-
secondary_mode on_error
+
-
secondary_server_ip localhost
+
-
secondary_server_path /var/spool/pandora/data_in
+
-
secondary_server_port 41121
+
-
secondary_transfer_mode tentacle
+
-
secondary_server_pwd mypassword
+
-
secondary_server_ssl no
+
-
secondary_server_opts
+
-
</code>
+
-
There are the following options (for more information, go to the [[:en:documentation:02_installation:05_configuration_agents#general_agent_parameters|Agent configuration chapter]]).
From Software Agents, it is possible to perform data server balancing, since it is possible to configure a master (main) and a backup (operational backup) data server. In the Software Agent configuration file ''pandora_agent.conf'' [[:en:documentation:pandorafms:installation:05_configuration_agents#ks3|it should be configured and uncommented]] the following part of the agent configuration file:
* <wrap :en>**secondary_server_ip**</wrap>: IP address of the secondary server.
+
* <wrap :en>**secondary_server_path**</wrap>: Path where the XML is copied to the secondary server, typically ''/var/spool/pandora/data_in'' .
+
* <wrap :en>**secondary_server_port**</wrap>: Port through which the XML will be copied to the secondary server, in Tentacle 41121, in SSH port 22 and in FTP 21.
+
* <wrap :en>**secondary_transfer_mode**</wrap>: Transfer mode to be used to copy the XML to the secondary server, Tentacle, SSH, FTP.
+
* <wrap :en>**secondary_server_pwd**</wrap>: Password option for FTP transfer.
+
* <wrap :en>**secondary_server_ssl**</wrap>: You may set ''yes'' or ''no'' depending on whether you want to use SSL to transfer data through Tentacle.
+
* <wrap :en>**secondary_server_opts**</wrap>: Other options required for the transfer will be entered in this field.
+
* <wrap :en>**secondary_mode**</wrap>: Mode in which the secondary server must be. It may have two values:
You need to install [[:en:documentation:pandorafms:introduction:02_architecture#ks1_1|multiple servers]]: network server, WMI server, Plugin server, Web server or prediction server, on several machines on the network (all with the same visibility to the systems you want to monitor) and all on the same segment (so that network latency data is consistent).
If [[:en:documentation:05_big_environments:06_ha#high_availability_database|High Availability is enabled in the Database]] some extra configurations are needed to connect more Pandora FMS servers to the MySQL cluster. In the ''pandora_server.conf'' file (located by default at ''/etc/pandora''), for each of the independent Pandora FMS servers to be added, the following parameters must be configured:
+
If [[#ks6|High Availability is enabled in the Database]], some extra configurations are needed to connect more Pandora FMS servers to MySQL cluster. In the ''pandora_server.conf'' file (located by default at ''/etc/pandora''), for each of the independent Pandora FMS servers to be added, the following parameters must be configured:
* ''dbuser'': You must have the username to access the MySQL cluster. For example:
* ''dbuser'': You must have the username to access the MySQL cluster. For example:
行 160:
行 201:
</code>
</code>
+
+
<wrap #ks5 />
===== Pandora FMS コンソールの HA =====
===== Pandora FMS コンソールの HA =====
-
Just [[[:en:documentation:06_metaconsole:03_installation|install another console]] pointing to the database. Any of the consoles can be used simultaneously from different locations by different users. A [[https://pandorafms.com/guides/public/books/load-balancing-with-keepalived|web load balancer]] can be used in front of the consoles in case horizontal growth is needed for console load sharing. The session system is managed through cookies and these are stored in the browser.
+
Just [[:en:documentation:pandorafms:command_center:03_installation|install another console]] pointing to the database. Any console can be used simultaneously from different locations by different users. A [[https://pandorafms.com/guides/public/books/load-balancing-with-keepalived|web load balancer]] can be used before the consoles, in case horizontal growth is needed for console load sharing. The session system is managed through cookies and these are stored in the browser.
In the case of using remote configuration and to manage it from all consoles, both data servers and consoles must share the input data directory (default: ''/var/spool/pandora/data_in'') for the remote configuration of agents, collections and other directories (see topic [[:en:documentation:07_technical_annexes:15_security_architecture|"Security architecture"]]).
+
In the case of using remote configuration and to manage it from all consoles, both data servers and consoles must share the input data directory (default: ''/var/spool/pandora/data_in'') for remote configuration of agents, collections and other directories (see topic [[:en:documentation:pandorafms:technical_annexes:15_security_architecture#ks3_1_1|"Security architecture"]]).
When updating Pandora FMS console in an HA environment, it is important to bear in mind the following points when updating by means of OUM through **Management** → **Warp update** → [[:en:documentation:pandorafms:installation:02_anexo_upgrade|Update offline]]. The OUM package can downloaded from Pandora FMS support website.
+
When updating Pandora FMS console in an HA environment, it is important to bear in mind the following points when updating by means of OUM through **Management** → **Warp update** → [[:en:documentation:pandorafms:installation:02_anexo_upgrade|Update offline]]. The OUM package may be downloaded from Pandora FMS support website.
**3.-** Change the temporary password to ''pandora'' of the **root** user. Remember that the **mysql >** prompt corresponds to the MySQL command interpreter (**MYSQL CLI**):
**3.-** Change the temporary password to ''pandora'' of the **root** user. Remember that the **mysql >** prompt corresponds to the MySQL command interpreter (**MYSQL CLI**):
-
**3.-** **root** ユーザのテンポラリパスワードを ''pandora'' に変更します。**mysql >** プロンプトは MySQL コマンドインタプリタ(**MYSQL CLI**)です。
In the following instructions the authentication method ''mysql_native_password'' is used, to use ''caching_sha2_password'' please refer to the topic "[[:en:documentation:pandorafms:technical_annexes:46_mysql_sha|SHA authentication method configuration in MySQL]]".
In the following instructions the authentication method ''mysql_native_password'' is used, to use ''caching_sha2_password'' please refer to the topic "[[:en:documentation:pandorafms:technical_annexes:46_mysql_sha|SHA authentication method configuration in MySQL]]".