White Papers

A Technical support and resources
31 Benchmark the Performance, Reliability, and Scalability of Dell EMC OpenManage Enterprise 3.4 in your data
center environment | 14465
5. Longevity Test results for OpenManage Enterprise 3.4
5.1 Longevity test configuration for OpenManage Enterprise 3.4
For Longevity testing the appliance was loaded with below Data on Day 1:
• 8,000 devices were discovered and inventoried. Devices discovered were a mix of chassis and rack
servers (5,000 rack and remaining chassis and sleds.)
• At least 200 device groups were created with at least 100 devices in each (Groups created were a mix of
static and query groups).
• At least 40,000 alerts were sent to the console, with 35,000 of these events mapped to the discovered
systems.
• Firmware baseline was created using an online catalog and mapped to 6,000 devices.
• A few physical rack servers were discovered with OME advanced licenses.
• Created templates. Cloned the created templates so that there are at least 200 templates.
• Some of the templates were deployed on simulated servers.
• One template was deployed on at least 50 servers.
• Few alert policies were created that would send emails based on the alerts received.
• At least 5,000 jobs were created by running CLI commands on targets.
• The config inventory job was scheduled to run on at least 2,000 targets every 24 hours.
• A template was used to create a baseline and associated at least 2,000 servers to it.
• Open Manage Power Manager Plugin 1.2 was installed, and metric collection was enabled for 5,000
devices.
• Created a policy that will send the notifications to OMM mobile app.
Following steps were executed periodically from Day 2 onwards till 14th day:
• Executed a REST API script to get all the alerts in the appliance every hour.
• Executed a REST API script to get all the devices in the appliance every hour.
• Executed a REST API script to trigger compliance re-checks for the baseline.
• Generated 500 alerts every 2 hours. These alerts were part of an alert policy which triggered an email
action.
• Refresh inventory of 8,000 devices was scheduled to run every 12 hours.
• Performed one template deployment per day using the GUI on physical server.