Hardware requirements
The tables in this section use the following terminology:
Node—IMC servers, database servers, and devices managed by IMC are called nodes.
Collection unit—The number of collection units equals the total number of performance instances collected at 5-minute intervals. If the collection interval is greater than 5 minutes, the number of collection units decreases. If the collection interval is smaller than 5 minutes, the number of collection units increases.
For example, if performance instances listed in Table 2 are collected every 5 minutes, the number of collection units is the same as the number of performance instances, which is 24. If the collection interval is twice the 5-minute interval (10 minutes), the number of collection units is half the total number of performance instances, which is 12.
Table 2: Performance instances
Monitored item
Number
Performance index
Performance instance
CPU
1
CPU usage
1
Memory
1
Memory usage
1
Interface
10
Receiving rate
10
Sending rate
10
Device
1
Unreachability rate
1
Response time
1
Total
24
Java heap size—Java heap size that can be used by the IMC Web server.
To set the Java heap size for IMC:
On Windows, run the setmem.bat heap size script in the \client\bin directory of the IMC installation path.
On Linux, run the setmem.sh heap size script in the /client/bin directory of the IMC installation path.
Set heap size to a value in the range of 256 to 1024 for a 32-bit OS, or in the range of 256 to 32768 for a 64-bit OS. The java heap size cannot exceed the physical memory size.
To improve I/O performance, follow these guidelines:
When the number of the collection units is from 100 K to 200 K, install two or more disks and a RAID card with a cache of a minimum of 256 MB.
When the number of collection units is from 200 K to 300 K, install two or more disks and a RAID card with a cache of a minimum of 512 MB.
When the number of collection units is 300 K to 400 K, install four or more disks and a RAID card with a cache of a minimum of 1 GB.
Optimal hardware requirements vary with scale, other management factors, and are specific to each installation. Please consult Hewlett Packard Enterprise Support, or your local account teams for exact requirements. If service components are added to the IMC platform, be sure to read the release notes of each component.
Table 3: Hardware requirements for a 32-bit Windows operating system
Management scale | System minimum requirements | ||||||
|---|---|---|---|---|---|---|---|
Nodes | Collection units | Online operators | CPU | Server memory | Java heap size | Disk space for installation | Disk space for data storage |
0 to 200 | 0 to 5 K | 20 | 2 cores | 4 GB | 512 MB | 3 GB | 30 GB |
0 to 200 | 5 K to 50 K | 10 | 2 cores | 4 GB | 512 MB | 3 GB | 60 GB |
200 to 500 | 0 to 10 K | 30 | 4 cores | 6 GB | 1 GB | 3 GB | 50 GB |
200 to 500 | 10 K to 100 K | 10 | 4 cores | 6 GB | 1 GB | 3 GB | 100 GB |
Table 4: Hardware requirements for a 64-bit Windows operating system
Management scale | System minimum requirements | ||||||
|---|---|---|---|---|---|---|---|
Nodes | Collection units | Online operators | CPU | Server memory | Java heap size | Disk space for installation | Disk space for data storage |
0 to 200 | 0 to 5 K | 20 | 2 cores | 4 GB | 2 GB | 3 GB | 30 GB |
0 to 200 | 5 K to 50 K | 10 | 2 cores | 4 GB | 2 GB | 3 GB | 60 GB |
200 to 1 K | 0 to 10 K | 30 | 4 cores | 8 GB | 2 GB | 3 GB | 50 GB |
200 to 1 K | 10 K to 100 K | 10 | 4 cores | 8 GB | 2 GB | 3 GB | 100 GB |
1 K to 2 K | 0 to 20 K | 30 | 6 cores | 12 GB | 4 GB | 4 GB | 60 GB |
1 K to 2 K | 20 K to 200 K | 10 | 6 cores | 12 GB | 4 GB | 4 GB | 200 GB |
2 K to 5 K | 0 to 30 K | 40 | 8 cores | 24 GB | 8 GB | 5 GB | 80 GB |
2 K to 5 K | 30 K to 300 K | 20 | 8 cores | 24 GB | 8 GB | 5 GB | 250 GB |
5 K to 10 K | 0 to 40 K | 50 | 16 cores | 32 GB | 12 GB | 7 GB | 100 GB |
5 K to 10 K | 40 K to 400 K | 20 | 16 cores | 32 GB | 12 GB | 7 GB | 300 GB |
10 K to 15 K | 0 to 40 K | 50 | 24 cores | 64 GB | 16 GB | 10 GB | 200 GB |
10 K to 15 K | 40 K to 400 K | 20 | 24 cores | 64 GB | 16 GB | 10 GB | 600 GB |
Table 5: Hardware requirements for a 32-bit Linux operating system
Management scale | System minimum requirements | ||||||
|---|---|---|---|---|---|---|---|
Nodes | Collection units | Online operators | CPU | Server memory | Java heap size | Disk space for installation | Disk space for data storage |
0 to 200 | 0 to 5 K | 20 | 2 cores | 6 GB | 512 MB | 3 GB | 30 GB |
0 to 200 | 5 K to 50 K | 10 | 2 cores | 6 GB | 512 MB | 3 GB | 60 GB |
200 to 500 | 0 to 10 K | 30 | 4 cores | 8 GB | 1 GB | 3 GB | 50 GB |
200 to 500 | 10 K to 100 K | 10 | 4 cores | 8 GB | 1 GB | 3 GB | 100 GB |
Table 6: Hardware requirements for a 64-bit Linux operating system
Management scale | System minimum requirements | ||||||
|---|---|---|---|---|---|---|---|
Nodes | Collection units | Online operators | CPU | Server memory | Java heap size | Disk space for installation | Disk space for data storage |
0 to 200 | 0 to 5 K | 20 | 2 cores | 6 GB | 2 GB | 3 GB | 30 GB |
0 to 200 | 5 K to 50 K | 10 | 2 cores | 6 GB | 2 GB | 3 GB | 60 GB |
200 to 1 K | 0 to 10 K | 30 | 4 cores | 12 GB | 4 GB | 3 GB | 50 GB |
200 to 1 K | 10 K to 100 K | 10 | 4 cores | 12 GB | 4 GB | 3 GB | 100 GB |
1 K to 2 K | 0 to 20 K | 30 | 6 cores | 16 GB | 6 GB | 4 GB | 60 GB |
1 K to 2 K | 20 K to 200 K | 10 | 6 cores | 16 GB | 6 GB | 4 GB | 200 GB |
2 K to 5 K | 0 to 30 K | 40 | 8 cores | 24 GB | 8 GB | 5 GB | 80 GB |
2 K to 5 K | 30 K to 300 K | 20 | 8 cores | 24 GB | 8 GB | 5 GB | 250 GB |
5 K to 10 K | 0 to 40 K | 50 | 16 cores | 32 GB | 12 GB | 7 GB | 100 GB |
5 K to 10 K | 40 K to 400 K | 20 | 16 cores | 32 GB | 12 GB | 7 GB | 300 GB |
10 K to 15 K | 0 to 40 K | 50 | 24 cores | 64 GB | 16 GB | 10 GB | 200 GB |
10 K to 15 K | 40 K to 400 K | 20 | 24 cores | 64 GB | 16 GB | 10 GB | 600 GB |