Hardware Specifications

Data Platform

Data Platform Supported Hardware shows the hardware specifications for the Data Platform. The Database Server specifications are especially relevant to integrating the HPUD solution, rather than the specifications for the Data Platform Server and the User Console Server. This happens because the application servers and the database server are located on the same system in the recommended configuration. For storage, you should estimate one megabyte per scan file of additional storage requirements.

It is essential to consider the CPU, storage, and memory requirements for Data Platform Normalize, in addition to the existing CPU, storage, and memory requirements of the HP Data Flow Probe Server, as shown in HP Universal CMDB 10.21 Supported Hardware.

The Normalize specifications for sizing are also shown in Data Platform Supported Hardware. For an accurate comparison, you should replace Data Platform “devices” with HP “scan files” (as shown in Additional Data Flow Probe Hardware Requirements), and use this as the suggested hardware requirement for the HP Probe Server with Data Platform Normalize.

Data Platform Supported Hardware

Environment

Data Platform Server

User Console Server

Database Server

Small
(up to 2,000 devices)1According to HP, a small deployment is less than 7000 assets, while Data Platform characterizes a small deployment as less than 2000 assets. Note the disk discrepancy on the HP Probe Server hardware disk space for enterprise (75,000 assets) of 300 GB vs. Data Platform's 1.5 TB.

CPU: Xeon ES-2630 or similar, 2 cores
RAM: 4 GB
Storage capacity: 20 GB free space
Network connection: Gigabit
Disk I/O: 80 MB/sec
CPU: Xeon ES-2630 or similar, 2 cores
RAM: 8 GB
Storage capacity: 20 GB free space
Network connection: Gigabit
Disk I/O: 80 MB/sec
CPU: Xeon ES-2630 or similar, 2 cores
RAM: 16 GB
Storage capacity: 50 GB free space
Network connection: Gigabit
Disk I/O: 80 MB/sec

Medium
(up to 50,000 devices)

CPU: Xeon ES-2630 or similar, 4 cores
RAM: 8 GB
Storage capacity: 100 GB free space
Network connection: Gigabit
Disk I/O: 80 MB/sec
CPU: Xeon ES-2630 or similar, 4 cores
RAM: 16 GB
Storage capacity: 100 GB free space
Network connection: Gigabit
Disk I/O: 80 MB/sec
CPU: Xeon ES-2630 or similar, 4 cores
RAM: 32 GB
Storage capacity: 350 GB free space
Network connection: Gigabit
Disk I/O: 150 MB/sec

Large
(up to 300,000 devices)

CPU: Xeon ES-2630 or similar, 8 cores
RAM: 16 GB
Storage capacity: 200 GB free space
Network connection: Gigabit
Disk I/O: 80 MB/sec
CPU: Xeon ES-2630 or similar, 8 cores
RAM: 32 GB
Storage capacity: 200 GB free space
Network connection: Gigabit
Disk I/O: 80 MB/sec
CPU: Xeon ES-2630 or similar, 8 cores
RAM: 64 GB
Storage capacity: 1.5 TB free space
Network connection: Gigabit
Disk I/O: 250 MB/sec

 

HP Universal CMDB 10.21 Supported Hardware

Component

Requirement

Computer/Processor

Windows/Linux:

To fulfill the CPU requirements, you must have one of the following:

Intel Dual Core Xeon Processor 2.4 GHz or later
AMD Opteron Dual Core Processor 2.4 GHz or later

Recommended: The latest generation of Intel/AMD processors are recommended.

In addition to the above requirements, you must have the following number of CPU Cores, depending on your deployment configuration.

CPU Cores:

Deployment

Minimum

Recommended

Small

2 Cores

4 Cores

Standard

4 Cores

8 Cores

Enterprise

8 Cores

24 Cores

Note: As HP Universal CMDB performance is dependent upon processor speed, to ensure proper HP Universal CMDB performance, it is recommended that you use the fastest possible processor speed.

Memory

Deployment

Windows

Minimum

Recommended

Small

4 GB RAM

8 GB RAM

Standard

8 GB RAM

16 GB RAM

Enterprise

16 GB RAM

32 GB RAM (for more than 40 million CIs and relationships)

Memory Swap File

Windows: The virtual memory for Windows should be at least 1.5 times the size of the physical memory.

Linux: The Linux swap file size should be equal in size to the physical memory.

Free hard disk space

Small/Standard/Enterprise: At least 100 GB (for logs, memory dumps, and so on)
If the search functionality is enabled, more hard disk space is required.

For example,

4M CIs + relationships: 30G or more space would be needed for SOLR index files
20M CIs + relationships: Almost 50G space would be needed

Display

Windows: Color palette setting of at least 256 colors (recommended: 32,000 colors)

Note: The hardware requirements for HP Universal CMDB Configuration Manager are the same as those for Universal CMDB.

 

Additional Data Flow Probe Hardware Requirements

Component

Requirement

Computer/processor

Recommended: The latest generation of Intel/AMD processors (Intel Xeon CPUs or compatible) and the fastest possible processor speed.

CPU Cores:

Deployment

Minimum

Recommended

Small

4 Cores

8 Cores

Standard

4 Cores

8 Cores

Enterprise

8 Cores

24 Cores

Note: As HP Universal CMDB performance is dependent upon processor speed in order to ensure proper HP Universal CMDB performance it is recommended that you use the fastest possible processor speed.

Memory

Deployment

Windows

Minimum

Recommended

Small

4 GB RAM

8 GB RAM

Standard

8 GB RAM

16 GB RAM

Enterprise

12 GB RAM

24 GB RAM

Memory Swap File

Windows: The virtual memory for Windows should be at least 1.5 times the size of the physical memory.

Free hard disk space

Small/Standard: 100 GB (Note: 75 out of 100 GB disk space is required for scan files storage)
Enterprise: 300 GB (Note: 225 out of 300 GB disk space is required for scan files storage)

Display

Windows: Color palette setting of at least 256 colors (32,000 colors recommended)

Note:

A Small Deployment supports a biweekly scanner-based inventory of 7500 nodes or a daily discovery of 5000 nodes for application dependency mapping. Other combinations of scanner-based inventory nodes and application dependency mapping discovery nodes are also supported, according to the following formula: [The number of Inventory Discovery nodes] + 5 times [the number of application dependency mapping nodes] is less than or equal to 7500.
A Standard Deployment supports a biweekly scanner-based inventory of 25,000 nodes or a daily discovery of 5000 nodes for application dependency mapping. Other combinations of scanner-based inventory nodes and application dependency mapping discovery nodes are also supported, according to the following formula: [The number of Inventory Discovery nodes] + 5 times [the number of application dependency mapping nodes] is less than or equal to 25,000.
An Enterprise Deployment supports a biweekly scanner-based inventory of 75,000 nodes or a daily discovery of 10,000 nodes for application dependency mapping. Other combinations of scanner-based inventory nodes and application dependency mapping discovery nodes are also supported, according to the following formula: [The number of Inventory Discovery nodes] + 7.5 times [the number of application dependency mapping nodes] is less than or equal to 75,000.
For example, 15,000 inventory discovery nodes and 2000 application dependency mapping nodes, in a Standard deployment, would be supported.
The XML Enricher must be configured to match the deployment mode of the probe. For details, see the “How to Configure XML Enricher to Suit the Probe Deployment Mode” section in the HP Universal CMDB Data Flow Management Guide.