Chat now with support
Chat mit Support

Foglight 5.9.1 - High Availability Field Guide

Running on Oracle RAC

In this configuration, the Management Server was installed on two distinct physical hosts, one acting as HA mode primary, and the other as secondary. This setup was run over an Oracle® RAC cluster to provide HA at the database layer. In addition, an HTTP proxy was configured to provide end users with a single URL for access to the Foglight™ browser interface.

Figure 1. Oracle RAC configuration

 
* 
NOTE: For more information about Oracle RAC, see: http://www.oracle.com/technetwork/database/clustering/overview/index.html.
To configure an HA cluster on RAC:
1
During installation of the primary Management Server, choose Oracle as the external database.
2
Choose the Configure Later option.
3
Ensure that you do not start the Management Server automatically when installation is complete.
4
Before starting the server, open the datasource-oracle.properites file and edit the url section:
url=jdbc:oracle:thin:@(DESCRIPTION= (FAILOVER=ON) (ADDRESS_LIST=(LOAD_BALANCE=ON)
(ADDRESS=(PROTOCOL=TCP) (HOST=primary.domain.com) (PORT=1521))
(ADDRESS=(PROTOCOL=TCP) (HOST=secondary.domain.com) (PORT=1521)))
(CONNECT_DATA=(SERVICE_NAME=FGLRAC.domain.com)))
5
Install the Management Server on each machine in the cluster in turn.
6
Replace the datasource-oracle.properites file on each machine with the modified one shown partially in Step 4.
7
Start the primary and secondary Management Servers.
 
* 
NOTE: The previous procedure outlines only one method of configuration. Other methods include: using the SQL scripts included with Foglight to do the first-time configuration, and further configuration of the oracle-ds.xml file. These methods are possible, but have not been tested.

Running behind an HTTP proxy

One of the most common configurations is running the Management Server in HA mode behind a proxy so that end users and the agent configuration only need one URL for connection to the browser interface.

In the following example, a third-party software program called balance is used as a proxy.

To run the Management Server behind an HTTP proxy:
1
Install balance, available from: http://www.inlab.de/balance.html.
2
Configure balance to forward connections made to the server’s port 8888 to the Foglight™ UI port on the two machines in the HA cluster.
3
Configure the proxy to regularly test the two Management Servers to determine which one is active and to send all requests to the active Management Server.
 
* 
NOTE: On failover to another member of the cluster, the Foglight browser interface session will restart.

Running in a cluster

This section describes one scenario for running the Foglight™ Management Server in HA mode with clustering at the application layer. In particular, the focus is on operating system level clustering used in commercial systems such as Oracle®, Microsoft®, and VeritasTM clusters.

Figure 2. Cluster configuration

This scenario uses the Linux® HA Project’s heartbeat software for SuSE ES 10.1. The heartbeat package includes a virtual IP resource called IPaddr2.

Configuration:
1
One virtual IP resource was set up in the cluster to migrate between two hosts.
2
The Management Server was installed on a shared disk so that it could run on either node in the cluster.
3
Agents were configured with the virtual IP.
4
All interaction with the Foglight browser interface was done through the virtual IP.
 
* 
NOTE: The agent has no mechanism to tie it to a particular interface, and it stops sending data to the Management Server at failover until restarted.

For more information about the Linux HA Project and heartbeat, see http://linux-ha.org.

 

Tuning connection issues in HA implementations

In some cases, the communication between servers in the cluster is not reliable. Sometimes unwanted behaviors occur, such as:

•
A secondary server takes over while the primary server is still running.
•
Messages from an HA member are discarded as “message from non-member”.
•
When starting up a secondary server, it fails to recognize the primary server.

These issues may be attributable to JGroup (the underlying communication package that JBoss® uses for its HA implementation) and to the fact that a Foglight HA implementation uses UDP for communication by default and UDP is by nature an unreliable protocol.

•
Tuning the Management Server
•
Managing hosts with multiple network interfaces
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen