Requirements for Gateway Server
This topic explains the various requirements for Gateway Server.
Minimum system requirements for each component
The Gateway Server computers are where you run the Manager runs that collect data to measure the performance of managed computers. A managed computer is any computer from which you want to collect data.
Data is collected through a Capacity Agent (Microsoft Windows, UNIX, or Linux), where the target is the computer on which the agent is installed.
The following table lists the minimum requirements for each Gateway Server component: Console and Managed computers:
Minimum system requirements by component
Minimum OS requirements for full support | System requirements | |
|---|---|---|
Console | ||
For details, see Supported operating systems for the console. | Processor: Pentium 4, 1.2 GHz Disk space:
Memory: 2 GB Additional requirements: .NET Framework 3.0 or later. | |
Managed computers | ||
For details, see Supported operating systems for the Agent. | Processor: Pentium 4, 1.2 GHz Disk space:
History and collect data do not have to be on the same drive as the product software. The amount of disk space necessary for history data varies depending on the size and configuration of your system. Memory: 2 GB Additional requirements: Install an Agent locally on the computer to collect data. | |
Note
Gateway Server Supports x86 or x86-64 architecture. The Windows Itanium architecture is not supported.
General system requirements
The following table lists general system requirements for Gateway Server:
General requirements
Requirement | Description |
|---|---|
Console display | The Gateway Server requires a desktop display with a resolution of 1024 x 768, color or gray scale. This resolution must be fully available. X emulation packages might reduce actual pixel counts, causing the screens to be truncated. |
TCP/IP | The Gateway Server uses TCP/IP to communicate between the console and remote (agent) node computers so TCP/IP must be installed on both the console and node. |
Collect Data repository | From 25 to 100 MB are required on each node depending on its activity. Space requirements vary greatly, depending on factors that include the type of data collected and collection frequency. |
Disk space requirements for Windows and Linux
This section lists disk space requirements for installing Gateway Server on Microsoft Windows and Linux computers.
| Requirement | Console or Agent | Description |
|---|---|---|
Windows | ||
| Disk Space | Console | Estimated disk space requirements are:
|
Agent | The history and collect data directories do not have to be on the same drive as the product software.
| |
Linux | ||
File system space for | Console and Agent | The |
Local file system | Console and Agent | The history and collected data repositories must be placed on a local file system, not a remote one. Data repositories on a UNIX network file system must have the NFS lock manager daemons, rpc.lockd and rpc.statd, running on both the client and server side for console-side repositories. |
Disk space | Console |
Note: When you install Capacity Agent, the installation wizard prompts you for the name of the directory that will be the repository for the Investigate history data. The repository requires a minimum of 75 MB of storage space. For information about estimating the size of the history data repository, see Estimating the disk space on the Agent system for historical data. |
| Disk space | Agent | The following are estimated disk space requirements, assuming the defaults of 3 days of collect data and 2 days of agent history retention:
|
For more information, see
Knowledge Article KA348468
.
Virus scan settings
If you run virus protection software on the same computer where Gateway Server software resides, BMC strongly recommends that you configure the virus scan software so that it does not scan *.lox and *.udr files, nor any of the following directories to avoid unnecessary CPU cycle consumption.
best1_collect_home\bgs\monitor\logbest1_collect_home\history%BEST1_HOME%\history
best1_collect_home could be the C:\Program Files\BMC Software\Patrol3\BEST1\7.5.10 folder, or similar.
Red Hat Enterprise Linux 6.0 requirements
- Before you can run the Gateway Server or Agent on a Red Hat Enterprise Linux 6.0 system, ensure that a compatible Korn shell is installed. Red Hat Enterprise Linux 6.0 does not install a Korn shell by default.
- Before you can use Red Hat Enterprise Linux 6.0 on a 64-bit system, you need to install the RPM
libstdc.i686package, which contains 32-bit libraries that are required by Gateway Server. Red Hat Enterprise Linux 6.0 does not install 32-bit libraries on 64-bit systems by default.
Collecting NT Network Segment Statistics
If you want to collect metrics associated with the NT Network Segment Statistics, you must install the Network Monitor agent, a Microsoft Windows service that enables you to capture and collect packets of information to detect and troubleshoot problems on your network.
The statistics are displayed through the Network Segment Object in Investigate. This object is available only when the Network Monitor Agent is installed on your system. Once installed, the Network Monitor agent can be automatically started when the console is started.
The Network Monitor agent is available only for Windows 2000 Server and Windows Server 2003. For Windows XP, use the Network Monitor Capture utility (NetCap) located with the Support Tools on the Windows XP CD.
For more information about the metrics associated with NT Network Segment Statistics, see NT Network Segment Statistics. For information about installing the Network Monitor agent or Network Monitor Capture utility, see your system administrator.
Migrating Active Manager runs during an upgrade
If you are running the product in a UNIX environment, the UNIX installation program does not automatically migrate active Manager runs from the earlier console version to the later console version during an upgrade. To migrate active Manager runs, you must run a migration script as a separate post-upgrade step.
To use the migration script, you must leave the earlier version of the Gateway Server installed on the computer when you upgrade the console. Therefore, do not select the Uninstall existing version option on the Configure Gateway Server Migration page when you install the later console version.
If you are running the product in a Microsoft Windows environment, the installation program manages the migration for you.
Secure Capacity Agent install requirements
On all operating systems other than Linux, you can install the Secure Capacity Agent by using the installation utilities of Gateway Server or Capacity Agent. In both cases, you must perform a custom installation and then select Advanced on the Configure Gateway Server Security Level page.
Note
Linux OSs only support a basic security level.
For more information about the Secure Capacity Agent, see Initiating Secure Agent data collection.
Comments