サポートと今すぐチャット
サポートとのチャット

Foglight 7.3.0 - High Availability Field Guide

Requirements

If you plan to run the Foglight® Management Server in HA mode, there are certain considerations:

•
A server running in HA mode can only use an external database. An external instance of MySQL with an InnoDB storage engine can be used if your database administrator has installed one. Please see the Foglight System Requirements and Platform Support Guide for information about the external databases supported for Foglight.
If you have been using a Management Server with the embedded database, refer to the Appendix: “Switching from an Embedded to an External Database” in the Foglight Installation and Setup Guide.
•
The database must be running for Foglight to operate. You may have to implement a combined database-backup and High Availability solution to achieve true redundancy of all components.
•
Specific ports are required for the HA setup to work, all of which must be set to the same values for all Management Servers in the HA cluster. For more information, see Configuring High Availability mode ports.
•
By default, HA mode works only within the local subnet and uses UDP (User Datagram Protocol) for communication. You can reconfigure your HA cluster to use TCP (Transmission Control Protocol), which can work outside of the local subnet; this is the recommended alternative if your HA cluster consists of a small number of designated HA Management Servers.
Configuring HA outside of a subnet (across a WAN) introduces some potential performance issues. Review the information in Important considerations for configuring HA over WAN before you configure the HA cluster.
•
To use the Remote Monitor, JRE 1.5 or later must be installed on the machine hosting the Remote Monitor, and the JAVA_HOME environment variable must be set to point to the installation directory. For more information, see Remote Monitor.

 

Managing High Availability mode

High Availability (HA) mode enables you to install multiple Foglight® Management Servers, where one server is the primary server and the others are standby servers. If the primary server stops responding, then the responsibility is taken over by one of the standby servers.

This describes the common management tasks for HA servers.

For information on tuning an HA cluster for better performance, see Tuning connection issues in HA implementations .

•
Enabling High Availability mode
•
Starting and stopping the server in High Availability mode
•
Redirecting secondary Management Servers to the correct URL
•
Starting and stopping the HA server from the command line
•
Configuring High Availability mode ports
•
Important considerations for configuring HA over WAN
•
Exploring the High Availability view
•
Configuring Foglight Agent Manager for HA mode
•
Upgrading cartridges in a High Availability environment
•
Troubleshooting FAQ

Enabling High Availability mode

You can enable High Availability mode during a Foglight® Management Server installation, or afterwards by editing the server.config file.

Enabling During Installation
To enable HA mode during installation of a new Management Server:
1
On the Foglight Mode page of the installer, select HA (High Availability) as the server startup mode.
2
In the HA Partition field, type the partition name.
 
* 
IMPORTANT: All Management Servers that you want to act as either primary or secondary servers within the same HA cluster must be configured with the same partition name.
3
You may also need to configure additional database settings in the Foglight Database Configuration step of the Management Server installer.
Configure the server to connect to the same database instance as all other members of the cluster, by setting the DB Type, DB Host, DB Port or Instance and DB Name to the same values as those used for the other members.
 
* 
NOTE: In some rare cases, certain settings might be different. For example, the value for DB Host might be different if there is a firewall between the database and certain members of the cluster in your environment.
You must also set the Database Administrator Account User ID and Password to the same values as those used for the other Management Servers that share the same HA partition name.
 
* 
IMPORTANT: The Database Administrator Account User ID cannot be the same as the Foglight Database Account User ID.
Enabling HA mode after installation
To enable HA mode after installation:
1
Open the file <foglight_home>/config/server.config on each Management Server that you want to participate in the HA cluster.
2
Locate and uncomment the parameter server.ha.partition.name.
3
Set the argument of server.ha.partition.name to the partition name for your HA cluster.
 
* 
IMPORTANT: All Management Servers that you want to act as either primary or secondary servers within the same HA cluster must be configured with the same partition name.
4
Configure the Foglight Management Server to connect to the same database instance as all other members of the HA cluster, by setting the parameters listed below to the same values as the other members:
 
* 
IMPORTANT: In some rare cases, certain parameters might be different. For example, the value for server.database.host might be different if there is a firewall between the database and certain members of the cluster in your environment.
a
server.database.host: Set the argument of this parameter to the Foglight database host name (or IP address).
b
server.database.port: Set the argument to the Foglight database port number.
c
server.database.name: Set the argument to the Foglight database name.
d
server.database.user: Set the argument to the Foglight database user name.
e
server.database.password: Set the argument to the Foglight database user password.
f
server.database.type: Set the argument to the type of database used (mysql, oracle, or sqlsvr).
5
Specific ports are required for the HA setup to work. These are listed in Configuring High Availability mode ports .
Ensure that all Management Servers in the HA cluster have these ports set to the same values in <foglight_home>/config/server.config.
 
* 
NOTE: When running in HA mode, the Foglight Management Server may use ports in addition to the ones that you can set using server.config. For more information, see Configuring High Availability mode ports.
6
Restart the Foglight Management Server in HA mode by navigating to <foglight_home>/bin and running the following command:
fmsha
 
* 
NOTE: For more information about command-line options, see Starting and stopping the HA server from the command line .

Starting and stopping the server in High Availability mode

To run the Foglight® Management Server in HA mode, you must use an external database, which must be running before you start the server.

To start the server in HA mode:

Do one of the following:

•
(Windows only) Choose Start > Programs > Quest > Foglight > High Availability > Start Foglight In HA Mode.
•
Enter the following from the command-line:
fmsha
 
* 
NOTE: For more information about command-line options, see Starting and stopping the HA server from the command line .

After the server starts successfully, the following message appears in the command shell or window:

Forge Server startup completed.

To stop the High Availability Server:

Do either of the following:

•
Type Ctrl-C in the command shell in which the Foglight HA server started.
•
(Windows only) Choose Start > Programs > Quest > Foglight > High Availability > Stop Foglight In HA Mode.
•
Open a second command shell, navigate to the directory <foglight_home>/bin, and execute the following command:
fmsha --stop
After the server stops successfully, the command shell closes.
 
* 
NOTE: For more information about command-line options, see Starting and stopping the HA server from the command line .
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択