The single server hardware guidelines provide suggested sizing for your system
Servers are assumed to have at least four cores (3.0GHz or better) and are no more than four years old. As memory and usage increase, the number of CPU cores needs to increase. Dual-core CPUs can work for the most basic installations, but such configurations are not recommended.
Note:
These hardware requirements assume you have a host dedicated to the Cruz Operations Center application. Other applications may compete for ports or other resources and can impair the system’s performance. Therefore, do not run or install any other additional services. If this cannot be avoided, be sure to allocate additional resources to the server.
When estimating the size of a deployment, it is important to understand the application configurations in the target environment. For example, the most resource-intensive, demanding applications are Traffic Flow Analyzer (TFA), Event Management, and Performance Monitoring.
- Standalone single-server installations with minimal use of high-resource demanding applications: The minimum recommended hardware is 12-GB RAM, 6-core CPU (2.8-GHz or better), 200-GB 10,000-RPM disk. If the network you manage exceeds these parameters or your system monitors more devices than your hardware can handle, consult your Dorado sales representative about upgrading to a more robust or multi-server version.
- Distributed installation of a single component server, such as Application Server only, Mediation Server only, Database Server only, or Web Server only: The minimum hardware recommended is 10-GB RAM, four-core or more CPU (2.8-GHz or more), 400-GB 10,000-RPM disk.
- When using Cruz's Express Installation Wizard, the sizing is pre-set based on the target range for the number of managed devices. Ram in ( ) is the total memory resource that must be available for the software.
Note: these settings are for the software and do not include the base resources needed by the OS. (Refer to the sizing table.)
- 50 or less (8 GB RAM) = App = 3072m, Web 2048m
- 50 to 200 (12 GB RAM) = App = 4096m, Web 3072m
- 200 to 500 (16GB RAM) = App = 6144m, Web 4096m
- 500 to 1,000 (24GB RAM) = App = 10240m, Web 6144m
- Managed Devices: The number of devices under management. A device is under management if it has been discovered or created as a single standalone device with one or more management interfaces—examples: switch, router, Windows OS, IDRAC, firewall, etc.
- 64-bit Windows or Linux OS: 64 Bit Windows Server OS (2008, 2012, 2016, 2019) and Redhat/Centos (7.4, 7.6, 8.0) are supported.
- Users: Concurrent users are expected to be actively using the Web UI.
- Interface Monitor Targets (up to): The estimated number of network interfaces that can be monitored with the allocated resources using the default settings. Estimates are based on using the default monitor settings.
- TFA: The number of devices that can export TFA data to be consumed by the Cruz. Estimates are based on the licensing model where 10% of devices can be enabled as exporters. Due to the nature of TFA, the impact on system performance is highly variable. The stated recommended resources may not be able to support the stated TFA exporters without tuning or resource adjustments. Overall it is recommended that the number of TFA ports should not exceed 10% of the total ports in the environment or else additional resource and system sizing may be necessary.
- Application Tuning (Memory GB): The common compute resources that can be tuned for performance.
|
Managed Devices |
64-bit Window or Linux OS |
Users |
Interface monitor targets (up to) |
TFA |
Application Tuning (Memory GB)*** |
||||
|
RAM GB |
CPU / Cores |
Disc GB |
App |
Web |
DB |
||||
|
<50 |
12 |
4-6 |
100 |
5 |
2500 |
5 |
4 |
3 |
512 |
|
75 |
12-14 |
6-8 |
100 |
8 |
5000 |
5 |
4 |
3 |
512 |
|
100-175 |
12-16 |
6-8 |
100 |
10 |
10000 |
10 |
4 |
3 |
1 |
|
CruzOC OVA -Linux Virtual Appliance up to ~100 devices |
12 |
6 |
105 |
10 |
10000 |
5 |
6 |
3 |
1 |
|
175-250 |
14-16 |
6-8 |
100-150 |
15 |
25000 |
25 |
5 |
3 |
1 |
|
300-500 |
16-18 |
6-8 |
150-250 |
25 |
25000 |
50 |
6 |
4 |
2 |
|
500-1000 |
18-20 |
8-10 |
250-500* |
25 |
45000 |
100 |
10 |
5 |
2 |
|
1000-2000 |
22-32 |
10-12 |
500-700* |
25 |
60000 |
100 |
12 |
6 |
4 |
|
2000-3000 |
40-48 |
10-12 |
750* |
25 |
**75000 |
100 |
16 |
8 |
8 |
|
3000-5000 |
48-64 |
12-14 |
750-1TB* |
50 |
**75000+ |
100 |
16-24 |
12 |
8 |
|
5000-7500 |
64-80 |
12-16 |
1-2TB" |
50 |
**75000+ |
100 |
24-32 |
20 |
16 |
|
10000 |
80-128 |
16+ |
2-3TB* |
50 |
**75000+ |
100 |
32-44 |
24 |
16 |
* Consider SSD or similar performing disk array for best performance.
** DB throughput constraints may hinder performance with standard drives. Consider DB array and best practices to tune performance data collection and storage capacity.
*** Unallocated memory is consumed by the application server, web server, OS, and thread pool resources as non-hep memory.
UNLIMITED / HIGH AVAILABILITY (HA)
The product can support an unlimited RTM (device count) license where there is no limit on the number of managed devices in inventory. There are many factors to consider when sizing with an unlimited license.
For instance, an High Availability (HA) deployment should be considered for environments managing over 5000 elements. If you are considering HA or unlimited license, custom sizing will be provided by Dorado.
For more information on sizing, please see Verifying System Requirements in the user guide, located in the Doc section of the knowledge base or contact your account manager.