Chat now with support
Chat with Support

Foglight for Virtualization Enterprise Edition 8.6 - Federation Field Guide

Planning for federation

When planning to deploy the federation feature, customers must respect the following practical considerations:

Services on Federated Children sharing the same name are joined in the Federation Master (for example, if on Federated Child A, a user has created a service Foo, and on Federated Child B, another user has created a service Foo, then both services are merged in the Federation Master to service Foo, which contains any logical components included in either A or B).
10 ms or lower in most cases leads to optimal results.
10 ms to 100 ms might be acceptable, depending on the complexity and frequency of browser interface requests.
100 ms and higher is likely to result in significant slowness.

Communication ports

To ensure that the federation setup works correctly, the Federation Master must open a certain set of connections to each Federated Child. When a firewall exists between the Federation Master and the Federated Children, the appropriate ports must be opened.

Federation connections are always established in the Federation Master to Federated Child direction. Once a connection is established, data transfer is bidirectional.

The following table lists the ports that must be opened to initiate these connections in a federated environment.

JRMP

4444

The Federation Master requires this port for generic communication with its Federated Children.

This port number is specified for each Federated Child in its server.config file, in the server.jrmp.invoker.port property.

JNDI JNP

1099

The Federation Master uses this port during the connection setup process.

This port number is specified for each Federated Child in its server.config file, in the server.jndi.jnp.port property.

JNDI RMI

1098

The Federation Master and the Federated Children use this port for transferring JNDI request/response data between them.

This port number is specified for each Federated Child in its server.config file, in the server.jndi.rmi.port property.

IMPORTANT: Starting in version 5.9.2, Foglight for Java EE Technologies no longer supports Nexus Federation. Without Federation, all application servers that could possibly participate in servicing the same request (through RMI or other remote calls) should be connected to the same Nexus.

HA considerations

High Availability (HA) mode enables you to install multiple 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.

Only the Federated Children can be run in High Availability mode. Running a Federation Master in HA mode is currently not supported.

In a federated environment with two or more Federated Children working in HA mode, the Management Server automatically chooses the primary Federated Child for data synchronization.

Configuring a federated environment

The Federation Master is a Foglight Management Server that has been configured to incorporate the data of federated instances. A Federation Master can not be utilized as any other Management Server (for example, no connected clients, agents, standard rule analysis).

When installing a Management Server, federation is by default disabled. When you install a Management Server, the server does not know if it is going to operate as a Federation Master or as a normal server. The server identifies this only on startup, by checking the server.federation variable in the server.config file. If this variable is set to TRUE, the server makes a number of changes that are necessary for it to run efficiently (given a certain load).

A Federation Master must always be started with server.federation variable set to TRUE. If a Federation Master starts up, even just one time, as a normal server, it makes modifications to the server that deplete its performance as Federation Master.

When upgrading a Federation Master, you must first verify that the server.federation variable was not changed to FALSE before you restart the server.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating