Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight Evolve 9.3 - Installing Foglight on a UNIX System with an External PostgreSQL Database

Before Installing Foglight Installing Foglight
Preparing to install Installing a new version of the Management Server Installed directories Foglight settings HP patch checking tool Uninstalling Foglight Upgrading the Management Server Installing Foglight FAQ
Running the Management Server Installing and Upgrading Cartridges Installing Agents

High Availability mode

Before you install Foglight, determine if you are going to set up and run the Management Server in High Availability (HA) mode or as a standalone server. High Availability mode enables you to install multiple Management Servers where one server is the primary server and the others are standby servers. If the primary server stops responding, then one of the standby servers in the HA cluster takes over the responsibility.

Configuring multiple servers using HA mode offers the following benefits:

•
Automatic restart: The restart process (FoglightHA Daemon) runs on the same host as the Management Server it is monitoring and monitors the state of the server. If the server stops responding or has a fatal error, then the restart process stops and restarts the server automatically. The process can also send out email notifications about various conditions of the server.
 
* 
NOTE: The default value for the restart process is 10 minutes (600 seconds). Machines with a slower processing speed take longer to reboot. You can modify the default time by editing the startup.grace variable in the restart_monitor.config file (located in the config directory).
•
Standby Server: To reduce outage times, a standby server instance is created (for a particular Foglight Management Server), and forms a partition. One server becomes the primary server and communicates with the agents, receives and processes data, and processes rules. All other servers are standby servers. If a primary server stops responding, one of the standby servers resumes service and becomes the primary server.

Considerations for running the Management Server in HA mode

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

•
Specific ports are required for the HA setup to work:
•
Cluster Mcast Port
•
HA JNDI RMI Port
•
HA JNDI JNP Port
•
HA JRMP Invoker Port
•
HA Pooled Invoker Port
•
HA JNDI UDP Group Port
All of these ports must be set to the same values for all Management Servers in the HA cluster. See the Administration and Configuration Guide for port descriptions and default port assignments.
•
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 alternative is the recommended option if your HA cluster consists of a few designated HA Management Servers. See the High Availability Field Guide for more information.
•
In both High Availability Mode and Single Server Mode, 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 failover of all components. Failover ensures that monitoring operations are not interrupted.
•
A server running in HA mode can only use an external database.

For more information about installing and configuring HA mode, see the High Availability Field Guide.

Using an external database

An external instance of the PostgreSQL® database can be used if your database administrator has installed one. Please see the System Requirements and Platform Support Guide for information about the external databases supported by Foglight.

A setup with an external database has the advantage of using existing infrastructure. For setup, a remote administrator user/password with rights to create users and tables in the user/temp tablespace is required. Remote administrator access must be granted.

Licensing

This section provides information about licensing for Foglight.

 
* 
IMPORTANT: See the Administration and Configuration Guide for information about license requirements, managing licenses, and the different categories of cartridges (based on their license requirements).
Providing a license file during installation

You can install a license file during installation if you perform a Custom Install. See Step 13: Add Foglight license file in Installing a new version of the Management Server.

Importing a license file after installation

You can also import a license after installing Foglight. There are three ways of providing a license file to the Management Server after installation.

Using the manual process
•
Move an existing license file into the <foglight_home>/license folder.
Using the Foglight Administration module
•
Upload a license file using the Foglight Administration module. See the Administration and Configuration Guide for instructions.
Using the command line
1
Start the Foglight Management Server.
2
Ensure that JAVA_HOME is set.
3
If you have not already done so, extract the file fglcmd.zip in <foglight_home>/tools.
4
Upload a license by navigating to <foglight_home>/tools and entering the following command:
fglcmd -usr <username> -pwd <password> -cmd license:import ‑f <license_file>
The preceding command assumes that you are using the default port 8080 and localhost. If you are not running with these default values, use the following options to indicate server and port:
-port <xx> -srv <server_name>
For example, if you want to connect to the Management Server using the default HTTPS port, include the option -port 8443 with the fglcmd command.
 
* 
NOTE: See the Command-Line Reference Guide for information about running the fglcmd utility and the options that can be used with fglcmd, including additional license-management commands.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation