Benchmark the Performance, Reliability, and Scalability of Dell EMC OpenManage Enterprise 3.2 in your data center environment This technical white paper provides information about best practices that you can use as the benchmark for using Dell EMC OpenManage Enterprise 3.2 to optimize the usage of servers and chassis. Abstract This technical white paper provides information about the best practices you can adopt while using the following features of Dell EMC OpenManage Enterprise 3.
Revisions Revisions Date Description Feb 2019 Initial release August 2019 Revision 1 Acknowledgements This technical white paper was produced by the following members of the Dell EMC server engineering team: Authors Nagaraj, K Pupul Mayank Sudhish Singh Soumyajeet Biswal Gabe Stern Support—Sheshadri PR Rao and Raghu Chozhan Viswanathan (InfoDev) The information in this publication is provided “as is.” Dell Inc.
Acknowledgements Contents Revisions.............................................................................................................................................................................2 Acknowledgements .............................................................................................................................................................2 Acronyms ....................................................................................................................
Acknowledgements 5.3 Test setup and results of the Configuration Inventory and Deployment feature in OpenManage Enterprise 3.2 (tested on a single MX7000 chassis) .........................................................................................................................24 5.4 Test results of the Configuration Inventory and Deployment feature in OpenManage Enterprise 3.2 (tested on a single MX7000 chassis) .........................................................................................
Acronyms Acronyms Acronym AD CLI DNS DIMM DRM DUP FC FCoE FIPS FQDD FTP GUI HDD iDRAC IOM iQN iSM LSB MAC OMEM PERC SNMP SSB VLAN WAN WWNN WWPN 5 Expansion Active Directory Command Line Interface Domain Name System Dual In-line Memory Module Dell EMC Repository Manager Dell Update Package Fibre Channel Fibre Channel over Ethernet Federal Information Processing Standards Fully Qualified Device Descriptor File Transfer Protocol Graphical User Interface Hard Disk Drive Dell EMC Integrated Dell Remote Access
Executive summary Executive summary Dell EMC OpenManage Enterprise is a web-based hardware monitoring and management console that provides a comprehensive view of Dell EMC servers, chassis, network switches, other third-party devices, and components on the enterprise network. It is designed for the next generation IT professionals with a focus on simplicity, automation, and unification of data center management.
1 Impact of hardware on the performance of OpenManage Enterprise 3.2 in PowerEdge servers and MX7000 chassis To optimize the setup and task schedule of your appliance, it is first necessary to understand how the hardware may affect performance. The appliance does most of the processing and stores all the data, so both the underlying hardware and the hardware allocated to the VM will be a limiting factor in the overall performance.
2 OpenManage Enterprise 3.2 features tested Longevity and reliability tests were performed for a duration of three weeks where specific features were used at regular intervals. The main focus of scalability and performance test was to collect and analyze various performance parameters of OpenManage Enterprise 3.2 for the following features: • • • • 2.
2.2 Load parameters defined in various tables The load parameters used for the test were to distinguish the performance of OpenManage Enterprise 3.2 under those parameters. • • • • 2.3 14th Generation servers—All the servers used for the feature test were 14G servers. Fully loaded appliance—The database was loaded with data by using events, tasks, and jobs such as configuration inventory and firmware update. After that, tests were performed for the specific features.
2.4 Test results for deployment of OpenManage Enterprise 3.2 Objective of this test is to verify the time taken to deploy Open Manage Enterprise 3.2 virtual appliance on an ESXi. OpenManage Enterprise 3.2 virtual appliance file size: • • • OVF Size: 920 MB VHD Size: 877 MB KVM Size: 877 MB ESXi setup information • • • • ESXi version–6.5.0 U1 Server–PowerEdge R940 Sockets–4 Cores per socket–24 Table 1: Time breakup during deployment of Open Manage Enterprise appliance on ESXI Sl. No.
3 Scalability and performance test results of OpenManage Enterprise 3.2 (on multiple PowerEdge servers) 3.1 Test setup and results of the Discovery and Inventory feature in OpenManage Enterprise 3.2 3.1.1 Recommendations for setting an environment to test the Discovery and Inventory feature in OpenManage Enterprise 3.2 3.1.2 Test environment and results of the Discovery and Inventory feature in OpenManage Enterprise 3.
Discovery and inventory of 8,000 servers by using WS-Man (Config I) Protocol used for discovery WS-Man Load Parameters Number of Servers Discovered Time taken for the first discovery, inventory and onboarding Time taken for rediscovery and onboarding Time taken for re-inventory Time taken for status-poll Table 2 Without Power Manger Plugin 8,000 devices 3 h 43 m 4h 3h5m 10 m With Power Manger Plugin 8,000 devices 3 h 48 m 4 h 2m 3 h 10 m 10 m Discovery and inventory of 3,000 servers by using WS-Man(Confi
Discovery and inventory of M1000e chassis Protocol used for discovery WS-Man Number of chassis discovered 250 Time taken for first discovery, inventory, and 19 m 02s onboarding Time taken for re-discovery 26 m 15s Time taken for re-inventory 10 m Time taken for status-poll 17 sec Time Taken for Complete Chassis Sub-Discovery 5 h 51 m Note—This technical white paper does not cover test results for SNMP‒based discovery and inventory of supported devices.
3.2 Test setup and results of the Firmware Upgrade feature in OpenManage Enterprise 3.2 3.2.1 Recommendations for setting an environment to test the Firmware Upgrade feature in OpenManage Enterprise 3.2 3.2.2 Test environment and results of the Firmware Upgrade feature in OpenManage Enterprise 3.2 14 Benchmark the Performance, Reliability, and Scalability of Dell EMC OpenManage Enterprise 3.
Firmware update of 100 servers Test Environment Number of servers updated Time taken for firmware update Time taken for firmware update on WAN environment (100 Mbps, 200 ms delay) Time taken for firmware update on WAN environment (10 Mbps, 500 ms delay) Test result 133 2 h 22 m 2 h 35 m 19 h 54 m Results for Memory utilization (in KB) while testing the firmware upgrade feature for 133 servers of Dell EMC OpenManage Enterprise 3.
3.3 Test setup and results of the Configuration Inventory feature in OpenManage Enterprise 3.2 3.3.1 • Recommendations for setting an environment to test the Configuration Inventory feature in OpenManage Enterprise 3.2 Recommendations for setting an environment to test the Configuration Inventory feature in OpenManage Enterprise 3.2 3.3.2 16 Test environment and results of the Configuration Inventory feature in OpenManage Enterprise 3.
Data about the total RAM consumed to test the Configuration Inventory feature of OpenManage Enterprise on multiple PowerEdge servers 3.4 Test setup and results of the Alert and Task Management feature in OpenManage Enterprise 3.2 • • • • • • • • 17 Reception of alerts is supported till 30 alerts per second continuously with no alert actions configured.
Memory utilized (In KB) to receive alerts when testing the Alerts feature of OpenManage Enterprise 3.2 on multiple PowerEdge servers Test Config Alert Frequen cy Total CPU Usage Total Memory Usage 18 Memory and CPU utilization for alerts in OpenManage Enterprise 3.
4 Scalability and performance test results of OpenManage Enterprise 3.2 (tested on a single PowerEdge server) 4.1 Test setup and results of the Discovery, Inventory, and Status Poll feature in OpenManage Enterprise 3.
4.2 Test setup and results of the Firmware Upgrade feature in OpenManage Enterprise 3.2 (tested on a single server) Firmware Update of a single PowerEdge server Test Environment Server Generation Time taken for firmware update DUP download time Firmware update time Post update inventory time 20 Test result 13G 27 m 39 m 3 m 11 s 14G 28 m 22 m 54 s 38 s Benchmark the Performance, Reliability, and Scalability of Dell EMC OpenManage Enterprise 3.
4.3 Test setup and results of the Configuration Inventory and Deployment feature in OpenManage Enterprise 3.2 Test setup and results of the Configuration Inventory and Deployment feature in OpenManage Enterprise 3.
5 Scalability and performance test results of OpenManage Enterprise 3.2 (tested on 20 MX7000 chassis) 5.1 Test setup and results of the Discovery, Inventory, and Status Poll feature in OpenManage Enterprise 3.2 (tested on 20 MX7000 chassis) Note—The Discovery, Inventory, and Status Poll tasks were performed when all the iDRACs in the chassis had IP address. This technical white paper does not cover the use cases for performing discovery of chassis where the sleds do not have IP addresses.
5.2 Test setup and results of the Firmware Upgrade feature in OpenManage Enterprise 3.2 (tested on a single MX7000 chassis) Test setup and results of the Firmware Upgrade feature in OpenManage Enterprise 3.2 Memory utilization while testing the Discovery, Inventory, and Status-poll features of the Dell EMC OpenManage Enterprise 3.2 on multiple Dell EMC M1000e chassis 23 Benchmark the Performance, Reliability, and Scalability of Dell EMC OpenManage Enterprise 3.
5.3 Test setup and results of the Configuration Inventory and Deployment feature in OpenManage Enterprise 3.2 (tested on a single MX7000 chassis) • • Test configuration: o Dell EMC MX7000 chassis o 2 Dell EMC MX840C sleds with four network cards and one FC card o 4 MX5108n IOMs Identity migration was performed from one Dell EMC PowerEdge MX840c server to another similar Dell EMC PowerEdge MX840c server.
5.4 Test results of the Configuration Inventory and Deployment feature in OpenManage Enterprise 3.2 (tested on a single MX7000 chassis) • • • The time taken to perform identity and VLAN deployment took 11 mins. This time is based on the identity attributes that were selected for deployment along with the three attributes per FQDD. The time taken to perform deployment increases slightly when more number of attributes are selected for performing a configuration operation.
6 Longevity Test results for OpenManage Enterprise 3.2 6.1 Longevity test configuration for OpenManage Enterprise 3.2 • • • • • • • • • • • 26 IPv4 and IPv6 were enabled in OpenManage Enterprise 3.2 Discovery and inventory of maximum supported number of devices were distributed in two weeks. Half the devices were discovered in the first week and next half in the second week. The OpenManage Enterprise 3.2 devices were discovered by using IPv6 addresses.
6.2 Longevity test results for OpenManage Enterprise 3.2 • • • • The time taken for performing scheduled discovery, inventory, and status poll remained approximately constant for a period of 15 days for the supported number of devices An uninterrupted service was observed while performing the Longevity test The time taken to open the GUI and access different pages increases slowly as more data is loaded in the appliance. The test data was captured after every third day.
All Devices>>Discovery All Devices>>Inventory All Devices>>Reports All Devices>>Audit 6.3 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 Test results of REST API in a longevity setup in OpenManage Enterprise 3.2 Test setup: • • • SL. No 28 8,000 Devices were discovered in Open Manage Enterprise 3.2. 50,000 alerts were present in database. OpenManage Power Manager Plugin was installed with 3,000 Devices added to the working set.
getdevicestatussumma 2 ry eventcatalogs 3 getreportdefs 4 gettimezones 5 getalldevices 6 getnetworkcurrentaddr 7 essconfiguration groupaudits 8 groupservice 9 mobilesubscriptions 1 0 getalljobs 1 1 gettemplates 1 2 getbaselines 1 3 getmibs 1 4 templatetypes 1 5 SubscriptionNotificatio 1 nService 6 getnetworkproxyconfig 1 uration 7 eventcategories 1 8 getnetworkaddressconf 1 iguration 9 querycontextsummarie 2 s0 getnetwork 2 1 29 https:///api/GroupService/Groups(500)/DeviceStatusS ummary?$t
globalexcludes 2 2 geatallleafdevices 2 3 templateviewtypes 2 4 geteventstatussummar 2 y5 eventseverities 2 6 getallalerts 2 7 gettimeconfigurations 2 8 operatorinfo 2 9 getconsolesettings 3 0 getSessions getwarrantySetting getallgroupheirarchy getInventoryInfo/OsNa me/OsVersion getapplicationserviceinf o 30 https:///api/DeviceService/GlobalExcludes?$top=9999 9999 https:///api/GroupService/Groups(500)/AllLeafDevices ?$top=99999999 https:///api/TemplateService/TemplateV
7 Additional references and troubleshooting topics 7.1 Role-based user privileges in Dell EMC OpenManage Enterprise 3.2 Dell EMC OpenManage Enterprise 3.
7.2 Dell EMC OpenManage Enterprise Firmware Update Support Matrix Dell EMC PowerEdge servers supporting device firmware management in Dell EMC OpenManage Enterprise 3.
7.3 Troubleshooting issues in Dell EMC OpenManage Enterprise when performing firmware update on target devices • • • • • 7.3.
Firmware on target device cannot be updated because the target device is not responding in Dell EMC OpenManage Enterprise 7.3.2.2 Resolution Process chart showing the resolution to firmware update issues because the target device is not responding 34 Benchmark the Performance, Reliability, and Scalability of Dell EMC OpenManage Enterprise 3.
7.3.3 Unable to update firmware on target device by using Dell EMC OpenManage Enterprise because Lifecycle Controller is in use 7.3.3.1 Issue Unable to update Dell EMC OpenManage Enterprise firmware because of an issue in Lifecycle Controller. Firmware on target device cannot be updated by using Dell EMC OpenManage Enterprise because of an issue in Lifecycle Controller 7.3.3.2 Resolution 1. Start the virtual console of the target appliance. a.
Firmware on target device cannot be updated by using Dell EMC OpenManage Enterprise because of an incorrect file is used 7.3.4.2 Resolution Try any one of the following: • • 7.3.5 Update the firmware by using the online versions. See Create online firmware catalog by using Dell EMC OpenManage Enterprise. Download the update package once again and retry the operation. Dell EMC OpenManage Enterprise is unable to create a firmware catalog 7.3.5.
Conclusion Dell EMC provides its customers with products that simplify and streamline their IT processes, freeing administrator’s time to focus on activities that help grow the business. This technical white paper provides comprehensive information about the test environment, recommendations, and test results in the form of neatly arranged infographics to make it easy for reading, scanning, and comprehension. To maximize utilization, special notes and cautions are specified, where necessary.
A Technical support and resources • • Dell.com/support is focused on meeting customer needs with proven services and support. To watch quick and short videos about handling the PowerEdge server components, visit the QRL video website. A.1 Related resources A.1.1 Contacting Dell EMC Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area.
• • • View and manage system alerts and alert policies. View hardware inventory and compliance reports. Monitor and report about warranty and licenses. Note—For information about supported browsers, see the Dell EMC OpenManage Enterprise Support Matrix available on the support site. Some of the security features of Dell EMC OpenManage Enterprise are: • • • • • • Role-based access that limits access to console settings and device actions.
