White Papers

14 Scalability and performance of Dell EMC OpenManage Essentials version 2.5
7 System update and server configuration management
Recommendations for using the System Update & Server Configuration feature based on the analysis of the
test results:
• For System Update or Server configuration deployment tasks, recommendation is to use 100 managed
systems at any given time.
• For better result and performance of server configuration management features such as Device
Compliance and Configuration Inventory, recommendations are as follows:
o Device Compliance
➢ Associate baseline with 500 devices at a time.
➢ If the managed device count is more than 500, create custom device groups for each set
of 500 devices, clone the existing baseline, and separately associate the other set of 500
devices group.
o Configuration Inventory
➢ Disable scheduled device configuration inventory if the number of managed out-of-band
devices are more than 500.
➢ Scheduled Configuration inventory task might run for a longer time than expected if
managed devices are more than 500 devices at a time.
➢ If the managed device count is more than 500, based on demand, the configuration
inventory can be triggered from device tree by selecting multiple intended devices or set
of devices added in a custom device group.
• Dell Repository manager is recommended as the catalog source for system update, because the
packages are downloaded at a faster rate. However, Dell Online FTP catalog can also be used.
• Separate system update tasks must be created for Windows and Linux targets in case of in-band
system updates.
• OME Enterprise Business configuration was used for the above analysis.
Note: The recommended minimum network bandwidth required for OpenManage Essentials in a WAN
environment is 10 Mbps (for Monitoring) and 20 Mbps (for Updates).
In OpenManage Essentials 2.5, the device configuration deployment by using the streaming functionality is
taking longer than deploying by using the file share setting. The following table lists the time taken for the
device configuration deployment tasks to complete in an environment with 1–100 devices by using the file
share and streaming functionality:
Table 7: Time taken by the device configuration deployment tasks
Number of
device(s)
Time required for configuration
deployment by using the file share
and iDRAC 2.41.40.40 when…
Time required for configuration
deployment by using the streaming
functionality and iDRAC 2.52.52.52 when…
Devices are turned
off
Devices are turned
on
Devices are turned
off
Devices are turned
on
1
2 minutes 30
seconds
1 minute 50
seconds
5 minutes 40
seconds
2 minutes 10
seconds
50
2 hours
1 hour 30 minutes
3 hours
2 hours
100
5 hours 20 minutes
3 hours 40 minutes
7 hours
4 hours 30 minutes