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

Foglight 7.3.0 - Federation Field Guide

Requirements

Federation has the following requirements:

•
A server must be dedicated as a Federation Master.
•
The minimum hardware needed by a federated environment to run Foglight® follows the recommendations for any Management Server. It varies widely, depending on a number of factors, including the number of agents being used, the persistence and data-rollup policies, agent configuration settings, and platform. For detailed information, see the Foglight System Requirements and Platform Support Guide.
•
Identical cartridges must be installed on the Federation Master and the Federated Child(ren).
•
Version compatibility. The following table presents the Federation Master - Federated Children compatibility matrix supported in Foglight.
 
Table 1. Federation Master - Federated Children compatibility matrix
Federation Master Version
Federated Child Versions

5.9.1

5.9.1

5.7.5.x

5.7.5.x, 5.7.1, 5.7.0, 5.6.x

5.7.1

5.7.1, 5.7.0, 5.6.x

5.7.0

5.7.0, 5.6.x

5.6.11

5.6.11, 5.6.10, 5.6.7, 5.6.5, 5.6.4, 5.6.3, 5.6.2, 5.6.0

5.6.10

5.6.10, 5.6.7, 5.6.5, 5.6.4, 5.6.3, 5.6.2, 5.6.0

5.6.7

5.6.7, 5.6.5, 5.6.4, 5.6.3, 5.6.2, 5.6.0

5.6.5

5.6.5, 5.6.4, 5.6.3, 5.6.2, 5.6.0

* 
IMPORTANT: If a Federated Child is an earlier version than your Federation Master, performance may not be optimal. For best results, upgrade your Federated Children to the same version as the Federated Master.
•
The maximum number of Federated Children in a federated environment is 20.

Scalability expectations

The deciding factor for scalability is the unified topology monitored by all of the Federated Children. The Federation Master keeps an internal representation of this global view. The memory consumption for the Federation Master is 1:4 (that is, four Federated Children are handled by one Federation Master).

To satisfy memory address space, sufficiently large environments may require a 64-bit VM to run the Federation Master.

 

Managing federation

Federation is an advanced deployment option that requires careful consideration. At a minimum, it requires dedicated hardware for a Federation Master, a plan for propagating and unifying models, and an established workflow to execute the administration of the servers.

This section describes the use of the Federation Master and Federated Children, and how to configure the federated environment. It also provides troubleshooting information.

•
Understanding federation communication channels
•
Planning for federation
•
Configuring a federated environment
•
Troubleshooting
•
Frequently asked questions

Understanding federation communication channels

Topology is retrieved from all servers periodically and then stored in the federation database. When the UI requests topology data, it is retrieved from the local federation database.

Three “channels” of communication exist between the Federated Children and the Federation Master: Topology synchronization, Metric pull on demand, and the Alarm service communication channel.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択