System requirements for the Gateway Server


For information about sizing and scaling the hardware capacity of Gateway Servers, see Sizing-and-scalability-guidelines-for-Gateway-Servers.

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.

Supported operating systems

The following operating systems are supported for the Gateway Server:

1 - Ensure that a compatible Korn shell is installed on a Red Hat Enterprise Linux 6.x system. The Korn shell is not installed by default.

2 - Server Core installations are not supported.

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.

Other requirements

  • On 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.
  • Ensure that TCP/IP is installed on the Gateway Server computer and the managed systems that run Capacity Agents. The Gateway Server uses the TCP/IP protocol to communicate with these managed systems.
  • Install the cron utility that is required to schedule Manager runs simultaneously.
  • 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.

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.

Back to top ↑

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*