System requirements for the Capacity Agent

This topic provides hardware requirements and supported operating systems for the Capacity Agent.

Gateway Server and Capacity Agent compatibility

The Gateway Server supports all versions of the Capacity Agents that are earlier than or same as the Gateway Server version.

When you apply Cumulative Hotfix 10 or later on Patch 1 (20.02.01) of TrueSight Capacity Optimization 20.02, the Gateway Server supports versions of the Capacity Agent that are later than the Gateway Server version.

Hardware requirements

The following table describes the hardware requirements for the Capacity Agent.

Operating system	Disk space required for
Operating system	Agent installation	Daily data collection	Historical data
Windows, UNIX, and Linux	300 MB	1 or 2 GB based on the number of processes, file systems, disks, and network interfaces in the system	Depends on the size and the configuration of your system. For information about estimating the disk size for storing historical data, see Estimating-the-disk-space-on-the-Agent-system-for-historical-data.

For Linux systems, the installation directory of each product component must be on a standard Linux filesystem such as ext3 or a Global File System (GFS) for high availability deployments (Active/Passive servers). Installation on a CIFS share mounted as a filesystem is not supported. You can use CIFS share only for the shared repository.

Supported operating systems

The following operating systems are supported for the Capacity Agent installation:

Patch requirements for the operating system

Patch for	Package name	Details
Solaris	libpool.so.1	For Solaris 11: SUNWpool SUNWpoold SUNWpoolr To verify that these packages are installed, run the following command: > pkginfo \| grep SUNWpool

Supported platforms for a Docker host

The following Linux systems are supported for running the Agent on a Docker host:

Red Hat Enterprise Linux
Ubuntu
CentOS

Other requirements

On UNIX and Linux systems, ensure that at least 2 MB of free space is reserved for the /etc file system on all the managed systems, and you have the execute (x) permission for the /etc directory.
Create the agent history and daily data collection repositories on a local file system.
If you want to use remote data repositories on a UNIX network file system, ensure that the rpc.lockd and rpc.statd NFS lock manager daemons run on both the client and server computers.
Ensure that semaphores and shared memory segments are configured on the managed systems where Capacity Agents are installed. For information about configuring the shared memory and semaphores, see Configuring-the-shared-memory-and-semaphores.

Virus scan settings

To avoid unnecessary CPU cycle consumption, BMC strongly recommends configuring the virus scan software to exclude scanning *.lox and *.udr files and any of the following directories:

best1_collect_home\bgs\monitor\log
best1_collect_home\history
%BEST1_HOME%\history

The path of the best1_collect_home directory can be C:\Program Files\BMC Software\Patrol3\BEST1\<product_version> or similar.