This section presents a list of known federation-related issues:
• |
Foglight® Management Server federation mode fails if the Federated Child runs on a Red Hat 5 environment and it does not have a DNS entry added. |
• |
java.lang.IllegalArgumentException: null object name errors appear in the Federation Master log file when a Federated Child is shut down. |
• |
Cartridge files (.car) installed on a Federation Master must be the exact same versions as the cartridge files installed on the Federated Children. |
This section presents a list of the most frequently asked questions related to Foglight® federation:
• |
For a complete list of versions supported in this and previous versions of the Federation Master, see Requirements.
For optimal results, your Federation Master and Federated Child(ren) should be the same version.
The Federation Master stores about 15% of what a Management Server stores.
In federation, multiple High Availability Federated Children can be added to the list of servers in federation.config. If High Availability makes one Federated Child become the primary server of a cluster, the Federation Master automatically receives data from this new primary server.
Federated Children can run in High Availability mode, Federation Masters cannot.
No, the Federation Master does not accept agent connections (see details on the earlier FAQ Does the Federation Master have any High Availability capabilities, to prevent it from being a single point of failure?).
[Hide the following information until we have a formula for calculating the repository sizing]
1 |
3 |
Reset TopologyRefreshPeriod to its old value. |
• |
If you have set up token exchange security between the Federation Master and the Federated Child, the username on the Federated Child will understand to take the name from the Federation Master. For instructions on how to set up token exchange security, see Security settings.
Topology changes made on the Federated Children are visible on the Federation Master with a delay defined by the TopologyRefreshPeriod parameter in the federation.config file. Alarms are treated differently than topology changes, and their refresh frequency is defined by the MaxAlarmUpdateDelay parameter in the federation.config file.
The Management Server reloads the federation.config periodically, and all changes take effect upon reload (by default, once a minute).
You can override any property in the server.config using the standard system properties methods that are recognized by the common code. If a property from server.config is overridden via a system property, then the override holds even if the configuration is modified at runtime.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center