Hardware requirements to support small, medium, and large environments

After you determine the size of your environment, consult the following topics for hardware requirements.

Notes

  • The recommended hardware requirements are valid, whether you use physical or virtual machines.
  • BMC recommends a tier 1 SAN storage (2 to 4 Gbps SAN dedicated channel) for the TrueSight Infrastructure Management Server.

Upgrade considerations for small to medium and medium to large environments

Based on whether you are upgrading from a small to medium or medium to large, you must update the following parameters in the pronet.conf file:

File pathSmall to MediumMedium to Large

(Windows)

pw\conf\pronet.conf

  • pronet.deployment.type=medium
  • pronet.instance.medium.max=60000
  • pronet.deployment.type=large
  • pronet.instance.large.max=250000

(Linux)

pw/conf/pronet.conf

  • pronet.deployment.type=medium
  • pronet.instance.medium.max=60000
  • pronet.deployment.type=large
  • pronet.instance.large.max=250000


Hardware requirements for the Infrastructure Management Server

Consider the following hardware requirements when you are planning the size of your environment.

Note

The RAM and storage requirements are for the Infrastructure Management processes and do not include the additional OS requirements.


With the embedded SAP SQL Anywhere database

EnvironmentComponentRequirement
Small

CPU

4 vCPU; Frequency 2.6 GHz and above

RAM

16 GB

Storage

200 GB

15000 RPM drive or a tier 1 SAN storage (2 to 4 Gbps SAN dedicated channel)

Available swap file size 1


8 GB

Medium

Platform

4 vCPU; Frequency 2.6 GHz and above

RAM

32 GB

Storage configuration

300 GB

15000 RPM drive or a tier 1 SAN storage (2 to 4 Gbps SAN dedicated channel)

Available swap file size 1
8 GB
Large

Platform

8 vCPU; Frequency 2.6 GHz and above

RAM

48 GB

Storage configuration

600 GB

15000 RPM drive or a tier 1 SAN storage (2 to 4 Gbps SAN dedicated channel)

Available swap file size 1
8 GB

1 Note: The free swap space is needed even after the installation is complete and while the Infrastructure Management is up and running.

With an external Oracle database

EnvironmentComponentRequirement
Small

CPU

4 vCPU; Frequency 2.6 GHz and above

RAM

16 GB

Storage

30 GB

15000 RPM drive or a tier 1 SAN storage (2 to 4 Gbps SAN dedicated channel)

Available swap file size 18 GB
Medium

Platform

4 vCPU; Frequency 2.6 GHz and above

RAM

24 GB

Storage configuration

50 GB

15000 RPM drive or a tier 1 SAN storage (2 to 4 Gbps SAN dedicated channel)

Available swap file size 18 GB
Large

Platform

8 vCPU; Frequency 2.6 GHz and above

RAM

40 GB

Storage configuration

100 GB

15000 RPM drive or a tier 1 SAN storage (2 to 4 Gbps SAN dedicated channel)

Available swap file size 18 GB

1 Note: The free swap space is needed even after the installation is complete and while the Infrastructure Management is up and running.

Hardware requirements for an Oracle database server

Consider the following hardware requirements for an Oracle database server when you are planning the size of your environment. For information about supported databases, see Supported databases for Infrastructure Management.

EnvironmentComponentRequirement
Small

Platform

4 vCPU; Frequency 2.6 GHz and above

RAM

16 GB

Storage configuration

170 GB for the database
15000 RPM drive or a tier 1 SAN storage (2 to 4 Gbps SAN dedicated channel)

Medium

Platform

4 vCPU; Frequency 2.6 GHz and above

RAM

32 GB

Storage configuration

250 GB for the database
15000 RPM drive or a tier 1 SAN storage (2 to 4 Gbps SAN dedicated channel)

Large

Platform

8 vCPU; Frequency 2.6 GHz and above

RAM

32 GB

Storage configuration

500 GB for the database
15000 RPM drive or a tier 1 SAN storage (2 to 4 Gbps SAN dedicated channel)

Database considerations

Infrastructure Management can use the embedded SAP SQL Anywhere database or an Oracle database in any deployment:

  • An embedded SAP SQL Anywhere database must run on the same system as the core server components. The embedded database is optimized for Infrastructure Management.
  • An Oracle database must run on a different system within the same subnet network.

Disk subsystems and database performance best practices

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

CPU guidelines

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

Guidelines and limitations for deployment

Follow these guidelines when planning the hardware deployment:

  • You can run multiple Integration Service processes on the same computer. Each Integration Service process on a computer requires 3 GB to 4 GB of memory.
  • The computers on which the Administration Console or the Operations Console are installed and the computer in which the TrueSight Infrastructure Management Server is installed should be running on the same network. To avoid a performance issue on the TrueSight Infrastructure Management Server, do not open the Administration Console or the Operations Console on the the TrueSight Infrastructure Management Server. Open these consoles on a computer other than the computer on which the TrueSight Infrastructure Management Server is running.
  • BMC recommends that the TrueSight Infrastructure Management server be a dedicated server with no other products installed on it.
  • BMC recommends a maximum of three Integration Service instances running on a single Integration Service host computer. For more information, see Sizing chart for multiple Integration Services running on the same Integration Service host.

Related topics

Was this page helpful? Yes No Submitting... Thank you

Comments