Hardware requirements

Hardware requirements must be considered when determining the size of your environment.

This section provides:

Hardware requirements for BMC ProactiveNet Server

When determining the size of your environment for data management, event management, hybrid management (impact event management), consider the following hardware requirements for BMC ProactiveNet Server.

Notes

  • The recommended hardware requirements are valid, whether you use physical or virtual machines.
  • If you are installing the BMC ProactiveNet server in a virtual environment, ensure to reserve CPU and memory resources.
  • BMC recommends a tier 1 SAN storage (2-4 GBps SAN dedicated channel) for the BMC ProactiveNet Server.

Hardware requirements for BMC ProactiveNet Server environments with the embedded Sybase database

Consider the following hardware requirements for a Sybase database server when you are planning the size of your environment for data event management, and impact event management.

Environment

Configuration Item

Data event management and impact event management

Small

Platform

  • Windows 2008 R2 (64-bit), Intel Core i7
    CPU: 4 vCPU, Frequency: 2.2 GHz  and Threads :16
  • SPARC Enterprise T-Series or M-Series Servers, 
    CPU: 4 CPUs, of 3 GHz, UltraSPARC T2, and 32 threads or more
  • Linux 2.6.32-358.18.1.el6.x86_64,
    CPU: 4 vCPU, Frequency: 2.2GHz  and threads :16

RAM

8 GB

Storage configuration

200 GB (30 GB for the server + 170 GB for the database)

15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)

Medium

Platform

  • Windows 2008 R2 (64-bit), Intel Core i7
    CPU: 4 vCPU, Frequency: 2.2 GHz, threads :16
  • SPARC Enterprise T-Series or M-Series Servers,
    CPU: 4 CPUs, 3 GHz, UltraSPARC T2, and 32 threads or more
  • Linux 2.6.32-358.18.1.el6.x86_64,
    CPU: 4 vCPU, Frequency: 2.2GHz  and threads :16

RAM

16 GB

An additional 4 GB of RAM is required if data views will be used. This is only for the Sybase database.

Storage configuration

300 GB (50 GB for the server + 250 GB for the database) 
15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)

Large

Platform

  • Windows 2008 R2 (64-bit), Intel Core i7
    CPU: 8 vCPU, Frequency: 2.2GHz  and threads :16
  • SPARC Enterprise T-Series or M-Series Servers,
    CPU: 8 CPUs, 3 GHz, UltraSPARC T2, and 32 threads or more
  • Linux 2.6.32-358.18.1.el6.x86_64,
    CPU: 8 vCPU, Frequency: 2.2GHz  and threads :16

RAM

32 GB

An additional 8 GB of RAM is required if data views will be used. This is only for the Sybase database.

Storage configuration

600 GB (100 GB for the server + 500 GB for the database) 

15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)

Hardware requirements for an Oracle database

Consider the following hardware requirements for an Oracle database server when you are planning the size of your environment for data event management, and impact event management.

BMC ProactiveNet hardware requirements for the Oracle database server

For information about supported databases, see Supported-databases-and-Web-consoles-system-requirements.

Hardware requirements for the computer on which BMC ProactiveNet is installed when it is configured with an Oracle database

Environment

Configuration Item

Data event management and impact event management

Small

Platform

  • Windows 2008 R2 (64-bit), Intel Core i7
    CPU: 4 vCPU, Frequency: 2.2 GHz  and Threads :16
  • SPARC Enterprise T-Series or M-Series Servers, 
    CPU: 4 CPUs, of 3 GHz, UltraSPARC T2, and 32 threads or more
  • Linux 2.6.32-358.18.1.el6.x86_64,
    CPU: 4 vCPU, Frequency: 2.2GHz  and threads :16

RAM

8 GB

Storage configuration

30 GB

15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)

Medium

Platform

  • Windows 2008 R2 (64-bit), Intel Core i7
    CPU: 4 vCPU, Frequency: 2.2 GHz, threads :16
  • SPARC Enterprise T-Series or M-Series Servers,
    CPU: 4 CPUs, 3 GHz, UltraSPARC T2, and 32 threads or more
  • Linux 2.6.32-358.18.1.el6.x86_64,
    CPU: 4 vCPU, Frequency: 2.2GHz  and threads :16

RAM

16 GB

Storage configuration

50 GB
15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)

Large

Platform

  • Windows 2008 R2 (64-bit), Intel Core i7
    CPU: 8 vCPU, Frequency: 2.2GHz  and threads :16
  • SPARC Enterprise T-Series or M-Series Servers,
    CPU: 8 CPUs, 3 GHz, UltraSPARC T2, and 32 threads or more
  • Linux 2.6.32-358.18.1.el6.x86_64,
    CPU: 8 vCPU, Frequency: 2.2GHz  and threads :16

RAM

24 GB

Storage configuration

100 GB for the server

15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)

Database considerations

BMC ProactiveNet can use the embedded Sybase ASA database or an Oracle database in any deployment:

  • An embedded Sybase database must run on the same system as the core server components. The embedded database is optimized for BMC ProactiveNet.
  • An Oracle database must run on a different system within the same subnet network.

Antivirus configuration

Before installing BMC ProactiveNet, disable the on-demand scan of the antivirus system.

Disk subsystems and database recommendations

The performance of the disk subsystem used for the BMC ProactiveNet database can significantly affect the scalability of your system. To optimize performance, BMC recommends the following guidelines:

  • Use RAID 10 or 01 on larger BMC ProactiveNet installations to better satisfy the higher demands on write I/O operations. BMC does not recommend using RAID 5.
  • Use SAN on medium and large deployments.
  • BMC performance testing for sizing was performed on UNIX and NTFS file system. Performance problems were observed using Veritas file systems, and BMC does not recommend those file systems for large deployments.
  • Use a larger number of physical disk drives (spindle count) than capacity disks. Because disk drive throughput performance has not increased at the same rate as disk capacity, you can achieve better performance with smaller disks.
  • For large environments, run a defragmentation process on the database file every six months.
  • Avoid extending raw data retention past recommended guidelines because this can impact I/O performance. For recommended guidelines, see the following topics:

CPU guidelines

Parallel CPUs usually improve user response time better than a single CPU with a higher clock speed.

Hardware requirements for BMC ProactiveNet Integration Service

When determining the size of your environment for data event management, and impact event management, consider the following hardware requirements for the BMC ProactiveNet Integration Service.

Note

If you are installing the BMC ProactiveNet Integration Service in a virtual environment, ensure to reserve CPU and memory resources.

Environment

Configuration Item

Data event management and impact event management

Small

Platform

  • Windows 2008 R2 (64-bit), Intel Core i7
    CPU: 2 vCPU, Frequency: 2.2 GHz, and Threads :16
  • SPARC Enterprise Servers,
    CPU: 2 CPUs, of 3 GHz, UltraSPARC T2 and above, and 16 threads
  • Linux
    2.6.32-358.18.1.el6.x86_64,
    CPU: 2 vCPU, Frequency: 2.2GHz, and threads :16

RAM

4 GB

Storage configuration

7200 RPM drive

50 GB of disk space

Medium

Platform

  • Windows 2008 R2 (64-bit), Intel Core i7
    CPU: 4 vCPU, Frequency: 2.2GHz, and Threads :16
  • SPARC Enterprise
    CPU: 4 CPUs, 3 GHz, UltraSPARC T2 and above, and 16 threads
  • Linux
    2.6.32-358.18.1.el6.x86_64,
    CPU: 4 vCPU, Frequency: 2.2GHz, and threads :16

RAM

8 GB

Storage configuration

7200 RPM drive

50 GB of disk space

Large

Platform

  • Windows 2008 R2 (64-bit), Intel Core i7
    CPU: 4 vCPU, Frequency: 2.2GHz, and Threads :16
  • SPARC Enterprise
    CPU: 4 CPUs, 3 GHz, UltraSPARC T2 and above, and threads:16
  • Linux
    2.6.32-358.18.1.el6.x86_64,
    CPU: 4 vCPU, Frequency: 2.2GHz, and threads :16

RAM

8 GB

Storage configuration

7200 RPM drive

50 GB of disk space

Notes

  • Each Integration Service process in an Integration Service computer requires 3 GB to 4 GB because you can run multiple processes on the same computer.
  • To avoid a performance issue on the BMC ProactiveNet Server, do not open the Administration Console or the Operations Console on the the BMC ProactiveNet Server. Open these consoles on a computer other than the computer on which the BMC ProactiveNet Server is running.
  • The computers on which the Administration Console or the Operations Console are installed and the computer in which the BMC ProactiveNet Server is installed must be running on the same network.
  • BMC does not recommend that you install any other product on the computer in which you have installed the BMC ProactiveNet Server.
  • BMC does not recommend that you install any other product on the computer in which you have installed the BMC ProactiveNet Integration Service, except stacking two more BMC ProactiveNet Integration Services.
  • When the load of the BMC ProactiveNet Server is distributed among Integration Services, BMC recommends a maximum of three Integration Services instances running on a single Integration Service host computer. No additional hardware is required on the Integration Service host computer. For more information, see Sizing-charts-for-data-and-event-management.

Related topics

 

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