Foglight 5.9.7 - Installing Foglight on Windows with an External Oracle Database

Configuring the cluster multicast port used in High Availability mode

You can change the cluster multicast port that is used when Foglight is running in High Availability (HA) mode. Members of an HA cluster use this port to communicate with each other. For more information, see the High Availability Field Guide.

Setting up Foglight server federation

Federation is a Foglight feature that addresses the needs of customers who monitor large-scale environments that are naturally partitioned into logical units. Each of these partitions is traditionally served by one Management Server instance and its distributed clients and agents.

Federation enables you to use one Management Server to operate, while using other Management Server as the data source. For detailed information about Foglight federation and how to create a federated environment, see the Federation Field Guide.

IMPORTANT: Federation is an advanced feature, which requires a dedicated Management Server separate from the Management Servers that are acting as data collectors. Contact Quest Professional Services to design and implement a federation strategy.

Setting memory parameters for the server

If you are running the Management Server by running bin\fms, you can configure the Java® Virtual Machine’s (JVM) minimum and maximum memory parameters for the server in the <foglight_home>\config\server.config file.

If you are starting Foglight using the run.[bat|sh] command, the JVM heap memory parameters set in the <foglight_home>\config\server.config file do not take effect. Use -X options to pass the memory parameters straight to the VM.

If your installation supports a large number (hundreds) of agents, you can set the Java® heap memory minimum (-Xms) and maximum (-Xmx) options to the same size. For example, assigning 1GB of memory can be set in the server.config file as follows:

Ensure that you uncomment these lines in the file.

You can set up to 100 VM options in total.

NOTE: The -Xms and -Xmx options are different for 32-bit and 64-bit JVMs and available physical memory. The values of the -Xms and -Xmx options do not necessarily have to be the same size. However, the value of the -Xmx option should not exceed certain limits that the System Administrator specifies.

Process heap use

When a thread is created and run, a run-time stack is dynamically allocated from the native process heap (not the Java® heap). This native heap requires a large contiguous memory block. If the system you are running does not have enough RAM, or if the operating system cannot find a large enough contiguous memory block, new native threads cannot be created and a java.lang.OutOfMemoryError occurs.

If the VM generates errors relating to a failure to allocate native resources, or relating to exhaustion of process address space, you must increase the native process heap size. Errors appear as a Java VM internal error message or a detail message associated with an out-of-memory error. Messages with the relevant errors indicate that the problem is process heap exhaustion.

You cannot directly set the size of the process heap. The process heap uses memory within the 32-bit address space not used by the garbage-collected heap. To increase the size of the process heap, decrease the maximum Java heap size using the -Xmx option in the server.config file.

The default stack size can be adjusted with the ‑Xss option.