TEST PLAN: EATON INTELLIGENT POWER MANAGER INTEGRATION ON SIMPLIVITY OMNICUBE

Transcription

1 TEST PLAN: EATON INTELLIGENT POWER MANAGER INTEGRATION ON SIMPLIVITY OMNICUBE EATON Abstract This test plan document describes the objectives, scope, approach and focus of testing the Eaton Intelligent Power Manager (IPM), Eaton 5P UPS, and Eaton Managed epdu integrated into a proven SimpliVity OmniCube infrastructure. May 2015

2 Contents Document Control Date Author Version Change References May 30 th, 2015 Jeff Kennedy, Randy Maples, Vinay Jonnakuti 1.0 Initial document 2

3 Contents Contents Chapter 1 Introduction 5 Purpose... 5 IPM Software... 5 Chapter 2 Test Approach 7 Assumptions and Dependencies... 7 Features to be Tested... 7 Testing Strategy... 7 Pass/Fail Criteria... 7 Test Engineers and Technology Contacts... 8 Testing Materials (Hardware/Software Requirements):... 8 Test Set-Up Considerations... 8 Chapter 3 IPM Set Up and Installation for Testing 10 IPM and Maintenance Mode VMware Interfaces Install IPM on the Server Load IPM for the First Time Configure Scan Settings Establish Node Access to IPM Change the Administrator Password Create a New User Set Up Pop-Up Notifications Setup Notifications IPM Plug-in for vcenter Installation Requirements. Error! Bookmark not defined. Install IPM plug-in for vcenter Server Chapter 4 Testing IPM Integration with VSP 44 Test Results Summary Testing Details Appendix A IPM Pre-Installation Checklist 52 3

4 Contents Tables Table 1. Related Documents... 6 Table 2. Eaton Service and Support... 6 Table 4. List of Test Equipment... 8 Table 5. IPM Integration with Test Results Summary Table 6. IPM Pre-Installation Checklist

5 Chapter 1 Introduction Purpose This test plan document describes the objectives, scope, approach and focus of testing the Eaton Intelligent Power Manager (IPM), Eaton 5P UPS and Managed epdu G3 integrated into a SimpliVity proven hyperconverged infrastructure. The test will validate interoperability of Eaton's IPM software. Through a tab on the vcenter dashboard or through the IPM plug-in on the new vcenter web client, IPM will monitor and control power devices across the network and during power disruptions, shutdown low priority VMs, consolidate remaining VMs onto a single OmniCube, gracefully shutdown the OmniCube Virtual Controller (OVC), and initiate a graceful shutdown of the appliance. The Eaton 5P UPS and Managed epdu G3 will provide battery backup and distribution for business continuity during a power outage. This document contains three parts: test plan, deployment specifics, and test results. Section 3 details the hardware, software and environmental requirements for carrying out an efficient and smooth testing. Section 4 discusses IPM software installation and test deployment. Section 5 ends with a detailed description of the test cases that were executed and screenshots of the test results. IPM Software Product Overview Intelligent Power Manager is Eaton s power device supervision tool for IT environments. IPM simplifies power monitoring, management and deployment as VMware Ready certified software. The software provides direct integration with the VMware vcenter Server management platform, enabling users to administer backup power and power distribution assets, and receive real time alerts, via a tab within the same dashboard they use to manage their physical and virtual servers, and performance of other information technology (IT) assets. To simplify installation, IPM plugs into vcenter server, whether on the same server or remotely through another server within the same network. The software uses vsphere APIs and web services for the vcenter plug-in as well as to enable remote, agentless virtual machine and graceful host server shutdown. Eaton s IPM also reads ESXi host servers and allows configuration within the ESXi dashboard. Configuration includes placing the host in maintenance mode as well as graceful shutdown of VMs or host servers, without requiring shutdown agents on VMs or physical host servers. An additional feature of IPM allows for the prioritization and sophisticated load shedding of VMs and servers to extend battery run time in the case of a power disruption. 5

6 Related Documents The following documents are related to this test plan: Table 1. Related Documents Document Eaton IPM Users Guide Eaton IPM Quick Start Guide IPM demo IPM integrates into VMware vcenter demo Simplivity Product Portfolio Simplivty Hyperconverged Overview Relationship Installation guide for supervisory software Brief guide for supervisory software Video explaining features and benefits of IPM Video demonstrating IPM integration with VMware List of available OmniCube offerings OmniCube key features and differentiation Eaton Service and Support For questions on Eaton power management solutions or assistance with installing or using specific features, please contact Table 2. Eaton Service and Support Toll Free Option 2, Option 1 International Option 2, Option 1 [email protected] Table 3. SimpliVity Service and Support Toll Free International [email protected] 6

7 Chapter 2 Test Approach Assumptions and Dependencies Eaton provides IPM software, Managed epdu G3 and 5P UPS for testing Unit testing is done on a SimpliVity OmniCube solution Test environment is installed and configured prior to test execution which includes the Eaton 5P UPS connected to utility power Refer to Appendix A for the pre-installation checklist Features to be Tested The test approach is to verify these four functions of the Eaton IPM software in an OmniCube environment. Upon the 5P detecting a power outage, the UPS will communicate with IPM. IPM will 1. Send an event that triggers an alarm in the vcenter Server alarms page 2. Use vmotion to live-migrate all VMs on the physical host onto a different physical host to extend available back-up runtime for environment 3. Shutdown the hypervisor Testing Strategy To test, turn off a power outlet for 5 minutes and verify that the UPS signals IPM that it detects a power outage. At the defined length of power disruption, IPM will perform the operation being tested as listed above. Keep the power off while completes the VM load shed, live-migration, and shutdown actions. Testing duration is 10 minutes. Simulating a power failure can be achieved by doing one of the following 1. Unplug the UPS powering components for 10 minutes. 2. Simulate an outage by turning off the epdu outlet providing source power to the UPS for 10 minutes. Pass/Fail Criteria A test case will be determined to have been successfully executed and passed if and only if all conditions stated are satisfied. All inputs have to be exercised, environment has to be setup, and outputs must be read and verified as having the expected values. Else, the test case is declared failed. 7

8 The test will be considered successfully passed if, upon detection of a power outage by the UPS, IPM will: 1. Send an event that triggers an alarm in the vcenter Server alarms page 2. Use vmotion to live-migrate all VMs on the physical host onto a different physical host to extend available back-up runtime for environment 3. Shutdown the hypervisor Test Engineers and Technology Contacts The table below lists the personnel involved in the test efforts with their respective roles. Individual Title Company Randy Maples Lead Application Engineer Eaton Jeff Kennedy Technical Marketing Manager Eaton Vinay Jonnakuti Engineering Manager SimpliVity Jonathan Tang Engineering Manager SimpliVity Testing Materials (Hardware/Software Requirements): The test environment will be formed of: Table 4. List of Test Equipment Equipment Quantity Provided By Eaton 5P UPS, 208V, 1U Rack UPS 1 Eaton Eaton 0U Managed epdu G3 1 Eaton Eaton Intelligent Power Manager software v1.5 1 Eaton SimpliVity OmniCube CN SimpliVity Test Set-Up Considerations Cisco Catalyst 3750G PoE-24 support 1G copper RJ45 and 10G Fiber. Eaton UPS support 10M/100M copper RJ45 connection only. (No 1G copper RJ45 connection) 8

9 Eaton Managed epdu G3 support 10M/100M copper RJ45 connection only (No 1G copper RJ45 connection). Eaton Managed epdu G3 connected to Eaton UPS for power distribution. SimpliVity OmniCube CN-2200 connected to Eaton Managed epdu G3 In this lab, the main switch used is the Cisco Catalyst 3750G PoE-24. Since the Eaton 5P UPS does not support 1G connection, the Catalyst 3750G was used so that the UPS can communicate with SimpliVity OmniCube test environment. 9

10 Chapter 3 IPM Set Up and Installation for Testing Eaton s Intelligent Power Manager software Eaton s IPM can be configured to initiate VMware vmotion in the event of a power disruption or a critical environmental alarm like temperature over the high limit. VMware s vmotion will move the VMs on the affected server to other servers within the cluster and VMware s DRS will balance the load as best as possible. If there is a power outage affecting all the servers in a cluster, IPM will be able to turn groups of VMs off. Once a group of low priority VMs is shut down, VMware s Distributed Power Manager can be used to combine VMs on fewer servers and shutdown servers to extend battery runtime. In this case, Eaton s IPM repurposes VMware s DPM which is normally used to increase data center efficiency. VMware Plugin Capability SimpliVity with its unified global management can be used to manage the OmniCube from vsphere Client tab. Figure 1. SimpliVity tab in VMware ESXi host dashboard 10

11 IPM Plug-in for vcenter Installation Requirements Before registering IPM as a plug-in for vcenter Server, administrators must do the following: Install VMware vcenter Server and vsphere Client. Note that vcenter and IPM can be installed on the same server or on different ones. They can also be deployed on a physical server or a VM running on the VMware ESX/ESXi hypervisor. Install VMware administrative tools on every VM you will be managing via vcenter Server. IPM relies on these tools to shutdown VMs gracefully during power outages. Install IPM on the Server 1. To begin the installation of IPM, double-click on the Install IPM.exe files located on the desktop of the remote server. Figure 2. Install IPM.exe icon on the desktop 11

12 2. Once the installer launches, click Next on the Welcome screen to begin Figure 3. Welcome Screen 12

13 3. Click Accept to agree to comply with the end-user license agreement. Figure 4. End-User License Agreement 13

14 4. Do NOT modify the default installation folder. Simply click Install to continue. Figure 5. Installation Folder Screen 14

15 5. Click Finish to close the installer and open Intelligent Power Manager. Figure 6. Installation Finish Screen Load IPM for the First Time 1. After the installation is complete, IPM will open in Internet Explorer. On the far right side of the screen, enter the default username and password then press Enter or click Login to access the software. Username: admin Password: admin 15

16 Figure 7. Login Screen Note: When using the default admin password, IPM will give you the following warning which we will address in a later step. Figure 8. Login Warning Screen 2. The first time launched, IPM will open to the Auto Discovery view and should look similar to the image below. Figure 9. Quick Start Auto Discovery Screen Each time IPM is opened, it will run its Quick Scan function to locate any new Eaton hardware on the network. Quick Scan searches based on the Subnet/gateway of the machine hosting IPM. In this case, the VM s IP address is , the default gateway is , and the subnet mask is This means IPM will search IP addresses through Quick Scan checks each IP address for an Eaton proprietary handshake. o o If successful, the device is added to the Node List. If unsuccessful, Quick Scan moves on to the next IP address. Take notice that Quick Scan finds not only UPSs and epdus, but also other instances of IPM and IPP. 16

17 Configure Scan Settings 1. Click on the System section under Settings. Figure 10. Systems Settings Screen 2. Click on Edit scan settings in the right-side navigation window. Figure 11. Action List with Scan Settings Function 3. Configure the XML, SNMPv1, and SNMPv3 settings to reflect the standard administrator username and password for all UPS/ePDU hardware within the infrastructure. Ensure that Automatic Scan is enabled by checking the box. Enter the standard UPS/ePDU username (Ex. Admin ) Enter the standard UPS/ePDU password (Ex. rackadmin ) Enter the SNMPv1 community name (Ex. public ) If needed, enter the SNMPv3 authentication information. Click Save to continue. 17

18 Figure 12. Edit Scan Settings Screen Establish Node Access to IPM Once the scans are complete, you will now need to ensure access is enabled for each node. This is required for IPM to be able to push information back to the cards. 1. Make visible the Access column Hover the mouse over any column header to expose the column menu drop-down icon. Click on the down arrow to access the menu. Check the box beside Access. You will now be able to see which devices are linked correctly and which still need attention. 18

19 Figure 13. Node Access Column 2. Select the nodes that need to be updated. Then, click on Set node access parameters. Figure 14. Set Node Access Parameters Screen 3. Type the username and password for the network cards. Username: Admin Password: rackadmin Click Save to store values 19

20 Figure 15. Access Parameters Login Screen 4. Once access has been correctly established with each node on the list, the list will look something like this: Figure 16. Node List Screen 20

21 Change the Administrator Password 1. Click on User List in the Views navigation pane. Figure 17. Views Screen on Navigation Page 2. Click on the admin user profile under the user list in the center display window. Figure 18. User List Profile Screen 3. Click on Edit user in the right-side control panel. Figure 19. Edit User Actions 4. Enter and re-enter a new administrator password, then click Save to continue. 21

22 Figure 20. Edit User Screen Create a New User 1. Click on User List in the Views navigation pane. See Figure Click on Add user in the right-side control panel. See Figure Define the user s profile by entering the following: A login name A password and password confirmation A profile level The Admin profile has full read/write access the User profile has read-only access Then click Save to store the user Figure 21. Add User Screen 22

23 Set Up Pop-Up Notifications 1. Click on Actions in the Views navigation pane. See Figure Click on the pre-configured Notification action in the center actions pane. Figure 22. Actions Pane 3. Click on Edit selected action in the right-side control panel. Figure 23. Actions List 23

24 4. Click on the pencil icon to edit the Events List Figure 24. Edit Events List Screen 24

25 5. For Event Criticalities, leave only warning (yellow exclamation) and critical (red exclamation) checked. Click Save to continue. Figure 25. Edit Action Screen Note: for an unmonitored server installation, uncheck the box labeled Action active. No one will see these notifications on an unmonitored server. 25

26 Setup Notifications 1. Click on Actions in the Views navigation pane. See Figure Click on the pre-configured action in the center actions pane. See Figure Click on Edit selected action in the right-side control panel. See Figure Configure a daily to report all Warning Events from the day Click on the Pencil icon to the right of Events List to open the Select associated events pane. Figure 26. Edit Action Screen With Warning Alarms Selected Select Warning Alarms to limit the alarm category. Click OK to return to the action editor. Click on the Pencil icon to the right of Events Source to open the Source selection pane. 26

27 Figure 27. Source Selection Screen. Select Any source to allow any connected node to trigger this event. Otherwise, select a specific node or group. Click OK to return to the action editor. Figure 28. Edit Event Categories Screen Click the box beside Action active Name the action. Ex. Daily System Warnings. Specify as the action type. Enter the SMTP server information. The Subject and Message is pre-defined to populate based on the device that triggers the alarm. Set the Digest to Every day. Click Save to continue 27

28 Figure 29. Edit Action Screen 5. Use the action copy feature to copy the previous action to facilitate the creation of a second action. See Figure 23. Click on the Daily System Warnings action. Click Copy selected action 6. Enter a name for the new action. Figure 30. Copy this Action Screen 7. Click on the newly created on Critical Alarms action in the center actions pane. Figure 31. Expanded Actions Screen 8. Click on Edit selected action in the right-side control panel. See Figure Configure an immediate notification for Critical Alarms. See Figure 26. Click on the Pencil icon to the right of Events List to open the Select associated events pane. 28

29 Figure 32. Edit Actions Screen With Critical Alarms Selected Select Critical Alarms to limit the alarm category. Click OK to return to the action editor. Click on the Pencil icon to the right of Event categories to open the Edit event categories pane Check Alarms then click Save. 10. In the Edit Action screen (see Figure 27), do the following steps: Click the box beside Action active Specify as the action type. Enter the SMTP server information. The Subject and Message is pre-defined to populate based on the device that triggers the alarm. Set the Digest to Every Minute. Click Save to continue. Note: You can create as many notifications as you like. These examples provide a basic level of notification coverage for the majority of IPM users. 29

30 Install IPM plug-in for vcenter Server Enabling the Infrastructure Connectors Module To enable the Infrastructures Connectors module for virtualization (administrator access): Vinay Jonnakuti 3/11/15 10:27 AM Comment [1]: We should probably move this above 1. From the left-side Views panel of the Eaton IPM main interface window, select the Settings > System menu item. The System page displays (see Figure 33). Figure 33. System Settings Page 30

31 2. Click Edit modules settings in the right panel. The Edit modules settings dialog box displays (see Figure 34). Figure 34. Enable Infrastructure Connectors Setting for Virtualization 3. Ensure that the Infrastructure Connectors checkbox is selected (checked). 4. Click Save. When a user tries to add a connector by Settings->Infrastructure Connectors->Add a connector, the sequence if screens show options available, depending of the JRE prerequisite (see Figure 35). The unavailable options are italic and grayed-out. If any JRE is not installed on the system hosting Eaton IPM, only legacy virtualization connectors can be selected (legacy for VMware), but new connectors cannot be selected (New VMware vcenter or New VMware ESX/ESXi). If a JRE is installed on the system hosting Eaton IPM, new infrastructure connectors are available (see JRE Prerequisites on page 10 of the IPM User guide). Figure 35. Selectable and Non-selectable Connectors 31

32 Adding a vcenter Server Manager To add a new VMware vcenter: 1. From the Add a Connector dialog, select New VMware vcenter from the Product drop-down list (see Figure 36). A second Add a connector dialog displays for your product connector selection. Figure 36. Add a Connector Product Selection Dialog Add identification information for the selected connector (see Figure 6). Product: Select New VMware vcenter from the drop-down list Hostname or IP address: Type VMware vcenter Hostname or IP address Port: Type the port number Username: Type VMware vcenter Administrator Username Password: Type VMware vcenter Administrator Password vcenter Plugin: Select (check) the checkbox to install and configure the Eaton IPM Plug-in to vcenter 32

33 Figure 37. Add VMware vcenter 2. Click Save after the fields are updated. The VMware ESXi hosts are automatically added to the managed nodes. Adding a VMware ESX/ESXi Hypervisor List In the case where you do not have a vcenter server manager, add new VMware ESX/ESXi hosts individually. To add a new VMware ESX/ESXi Hypervisor list: 1. From the Add a Connector dialog, select New VMware ESX/ESXi from the Virtualization drop-down list. A second Add a connector dialog displays for your product connector selection. 2. Add identification information for the selected connector (see Figure 38) Product: VMware ESX/ESXi is already selected in the drop-down list. Hostname or IP address: Type VMware ESX/ESXi Hostname or IP address Username: Type VMware ESX/ESXi Administrator Username for the Administrator with admin rights on the ESXi Password: Type VMware ESX/ESXi Administrator Password 3. Click Save after the fields are updated. 33

34 Figure 38. Add VMware ESX/ESXi VMware vcenter Server will now: Register IPM Create a new tab in vcenter labeled Intelligent Power Manager (see Figure 39) Declare a series of new power-related events Create a new host alarm that is triggered when a power failure impacts this hypervisor Figure 39. Eaton Power Manager tab on vcenter dashboard In addition, IPM will: Build a comprehensive list of hypervisors in the VMware environment Create a new type of node that represents those hypervisors 34

35 Using the IPM plug-in for VMware vcenter Once the IPM plug-in for vcenter Server has been installed and registered, administrators can use it to view information about a host server s power source, define shutdown settings for VMs and create or modify a variety of power-related events. Viewing host server power information 1. In the Views pane, click Node List within the Views folder (see Figure 40). 2. Click VMware host (see figure 40). A list of VMware host devices appears in the Node List pane. 3. In the Node List pane, click the host device whose power information you wish to view. The information appears in the Selection view pane. Figure 40. To view host server power information, click Node List in the Views pane, then click VMware host and then click a node in the Node List pane. Configure Node Policies 1. In the Views pane, click Configuration Policies within the Management folder (see Figure 41). Click on Create new policy on the right side of the screen. Figure 41. Configuration Policies in Management. 35

36 2. Configure the Edit selected policy window as shown in Figure 42. Ensure that the Target node is, in fact, the IP address of OmniCube ESXi host 1. Click Save to complete the policy. Figure 42. Edit Selected Policy Window : OmniCube 1 36

37 3. Repeat step 2 for the second OmniCube. See Figure 43. Click Save to complete the policy. Figure 43. Edit Selected Policy Window: OmniCube 2 4. Click on Create new policy a third time and enter All Non-Omni VMs as the Configuration policy name. See Figure Click the pencil to the right of Target nodes. Figure 44. Create New Policy Window. 6. Select all VMs EXCEPT the OmniCube VCs. Also, only select VMs; do not select hardware. See Figure 45. Click Ok to complete target selection. 37

38 Figure 45. Add/Remove Target Nodes Window 7. Click Save to complete the policy. Configure Event Rules 1. In the Views pane, click Actions / Events within the Settings folder. See Figure 46. Click on Edit event rules on the right side of the screen. Figure 46. Action/Events Main View Pane Window. 38

39 2. Click Add under the Events List section then click New blank event to open the Advanced event definition window. See Figure 47. Figure 47. Advanced Event Definition Configuration. 3. Type Power Failure 20 sec delay in the Event Name* section. 4. Set Event severity to Warning. 5. Set Event mode to Trigger if all conditions are satisfied. 6. Click Add in the Event definition section to open the Rule definition applet. Configure a rule to match Figure 48. Click Ok to save the rule. Figure 48. Rule Definition Applet: 20 seconds 39

40 7. Create a second custom event by repeating steps 2-5, replacing Power Failure 20 sec delay with Power Failure 90 sec delay. 8. Click Add in the Event definition section to open the Rule definition applet. Configure a rule to match Figure 49. Click Ok to save the rule. Figure 49. Rule Definition Applet: 90 seconds 9. Click Ok at the bottom of the Advanced event definition window to save the created events. Configure Event Rules 1. In the Views pane, click Actions / Events within the Settings folder. See Figure 50. Click on Create new action on the right side of the screen. Figure 50. Action/Events: Main View Pane Window 2. Configure the action as shown in Figure 51. a. Ensure the action is marked as active. b. Event List: Select the Power Failure 20 sec delay event rule. c. Event Source: Select the UPS into which the OmniCube ESXi hosts are connected. d. Action type: Select VM migration action 40

41 e. VM to migrate: Select the All Non-Omni VMs group policy. f. The host target: Select the IP address of the OmniCube ESXi host 2. Figure 51. Edit Action Window: 20 second delay 3. Click Save to complete the action. 4. Create a second action by again clicking Create new action. 5. Configure the action as shown in Figure 52. a. Ensure the action is marked as active. b. Event List: Select the Power Failure 90 sec delay event rule. c. Event Source: Select the UPS into which the OmniCube ESXi hosts are connected. d. Action type: Select VM power action e. Power command: Select Guest shutdown. f. The VM target: Select the OmniCube VC virtual appliance controlling OmniCube ESXi host 1. g. Shutdown guest timeout: type

42 Figure 52. Edit Action Window: 90 second delay 6. Click Save to complete the action. 7. Create a third action by again clicking Create new action. 8. Configure the action as shown in Figure 53. a. Ensure the action is marked as active. b. Event List: Select the Power Failure 90 sec delay event rule. c. Event Source: Select the UPS into which the OmniCube ESXi hosts are connected. d. Action type: Select Host power action e. Host power command: Select Place host in standby mode. f. The VM target: Select the IP address for the OmniCube ESXi host 1. g. Shutdown guest timeout: type

43 Figure 53. Edit Action Window: 120 second timeout 9. Click Save to complete the action. Triggering events in vcenter Server through IPM Once vcenter Server and IPM are configured, a power outage to the UPS powering the host servers will: Send an event that triggers an alarm in the vcenter Server alarms page Live-migrate all VMs to a single OmniCube Gracefully shutdown the OmniCube VC on the vacated host Place the vacated host in standby mode to reduce power consumption 43

44 Chapter 4 Testing IPM Integration: OmniCube The following tests focus on individual features, functionalities and operational behavior of IPM to ensure that the software corresponds to its specifications. Test Results Summary Table 5. IPM Integration Test Results Summary Pre-Test Conditions IPM software and IPM plugin for vcenter installed Eaton 5P UPS connected to epdu outlet providing source power to the unit Test environment is installed and configured prior to test execution OmniCubes are pre-configured with HA enabled and powered by epdu. Workload 1 (10) VMs without workload, (1) IPM vapp, (2) OmniCube Virtual Controllers Workload 2 (20) VMs without workload, (10) with workload, (1) IPM vapp, (2) OmniCube Virtual Controllers Refer to Appendix A for the pre-installation checklist Test Procedure Comments Feature/ functionality to test: Expected Results Test Results To test, turn off the input power to the 5P for 10 minutes and verify that the UPS signals IPM that it detects a power outage. At the pre-defined length of power disruption (based on the parameters set), IPM will perform the VMware vmotion operation. Keep the power off while IPM finishes VM migration, OmniCube 1 Virtual Controller graceful shutdown, and OmniCube 1host graceful shutdown. Testing duration is 10 minutes. Needed to resolve two issues to complete testing: Place OmniCube 1 and OmniCube 2 into a cluster with both residing in HA mode. Simulate power outage time IPM triggers alarms when power outage is detected. Upon detection of a power outage by the UPS, IPM will send an event that triggers an alarm in the vcenter Server alarms page Pass. Figures 54 shows the UPS status alerts at the top and/or bottom of the screen. On battery condition alerts are shown on both top and bottom of the screen. 44

45 Pre-Test Conditions IPM software and IPM plugin for vcenter installed Eaton 5P UPS connected to epdu outlet providing source power to the unit Test environment is installed and configured prior to test execution OmniCubes are pre-configured with HA enabled and powered by epdu. Workload 1 (10) VMs without workload, (1) IPM vapp, (2) OmniCube Virtual Controllers Workload 2 (20) VMs without workload, (10) with workload, (1) IPM vapp, (2) OmniCube Virtual Controllers Refer to Appendix A for the pre-installation checklist Feature/ functionality to test: Expected Results Test Results: Feature/ functionality to test: Expected Results Test Results: Feature/ functionality to test: Expected Results Test Results: When loss of utility power is detected, IPM triggers live migration for virtual machines to consolidate them onto a signle OmniCube, then shuts down the unused OmniCubes during an outage Upon detection of a power outage by the UPS, IPM will shut down low priority VMs, live migrate remaining VMs to a single OmniCube, shut down the unused OmniCube Virtual Controller, then shut down the unused OmniCube ESXi hosts. Pass. Figure 54 shows OmniCube 1 live-migrating VMs when UPS detected loss of utility power and went on battery. Test showing shutdown completion of the OmniCube VC on OmniCube ESXi host 1, followed by successful host shutdown will all VM remaining operational. Upon detection of a power outage by the UPS, IPM initiate shutdown of OmniCube VC on OmniCube ESXi host 1 and then successfully shutdown the host. Pass. Figure 55 shows UPS on battery power and shutdown completion of OmniCube VC on OmniCube ESXi host 1. Figure 56/57 shows successful host shutdown of with all VMs remaining operational. Successfully bring OmniCube ESXi host 1 online once power is restored. Redistribute VM workload. OmniCube ESXi host 1 returns back online Pass. Figure 58 displays power lost to UPS which started the IPM timer to shutdown OmniCube ESXi host 1 is restored. The OmniCube ESXi host 1 is brought back online and VMs are redistributed accordingly. 45

46 Testing Details This test demonstrates how an OnmiCube 2+0 cluster can be consolidated into a single host to increase the available runtime without compromising VM performance. Once the UPS input power was removed (power outage simulation), IPM began a live migration of all VMs from OmniCube 1 to OmniCube 2. IPM then sent a shutdown command to the OmniCube Virtual Controller running on OmniCube 1. Once the OmniCube Virtual Controller shutdown is complete, OmniCube 1 was no longer supporting workloads at which time IPM was able to gracefully shutdown the physical host, decreasing the UPS load by 50% ultimately increasing the available runtime by 100%, effectively doubling the remaining runtime for OmniCube 2 and boosting business continuity. The following test was then done by opening the breaker feeding the Eaton 5P1500 into which the two OmniCube ESXi hosts were connected. The test (load evacuation from OmniCube 1 to OmniCube 2) was done by switching off the breaker to UPS , then allowing the automation scripts to execute. Figure 54. Test showing UPS on battery power causing VM migration off of OmniCube ESXi host 1. 46

47 Figure 55. Test showing shutdown completion of the OmniCube VC on OmniCube ESXi host 1. Figure 56. Test showing the host shutdown initiation. 47

48 Figure 57. operational. Test showing successful host shutdown with all VMs still Figure 58. Power restored to OmniCube ESXi host 1. The OmniCube ESXi host 1 is brought back online and VMs are redistributed accordingly 48

49 Performance During Testing This test demonstrates the expanded resiliency of the OmniCube platform in combination with Eaton s power management solution. Through IPM integration with VMware vsphere, Eaton is able to maximize OmniCube performance by extending backup runtime by approximately 50%, through integrated workload management. As a result, the OmniCube can maintain critical virtual machines for a longer period of time to avoid costly downtime and improve overall business continuity. Figure 59. UPS state before opening circuit breaker feeding the UPS. 49

50 Figure 60. ESXi host 1. UPS state immediately prior to the shutdown of OmniCube Figure 61. UPS state immediately after the shutdown of OmniCube ESXi host 1. (Note the increase in UPS runtime from 10 minutes 40 seconds to 21 minutes 9 seconds) 50

51 Figure 62. breaker. UPS state immediately after the closure of the UPS feeder Figure 63. host 1. UPS state immediately after the restart of OmniCube ESXi 51

52 Appendix A: IPM Pre-Installation Checklist Appendix A IPM Pre-Installation Checklist Verify the following steps before installing IPM. Consult the ReadMe file for upto-date system requirements. Table 6. IPM Pre-Installation Checklist Action Checked Hardware Verify that the UPS is connected to a power source. Verify that the equipment to be protected are connected to the UPS or epdu connected to the UPS/ Ensure that the network management card is installed in the UPS Verify presence of these systems. IPM installation requires Systems hosting the Eaton IPM Systems that display the Web-based graphical user interface (GUI) Operating Systems Check the operating system. IPM can be installed on Microsoft Windows 2000, Microsoft Windows XP, Microsoft Windows Vista 7, Microsoft Windows 7 and 8, and on Microsoft Windows Server 2003, 2008 (including R2 revision), and For better performances with multiple nodes, Eaton recommends a Microsoft Windows Server OS (that does not have the limitation of 10 simultaneous network connections) To avoid network or serial port access conflicts, do not install the Eaton IPM on a machine that also hosts: Network management systems Eaton Intelligent Power Protector (IPP) Eaton Enterprise Power Manager Eaton Network Shutdown Module Network Management Proxy Eaton UPS Management Software (This is the previous Eaton software for managing UPSs. If you were using it previously, remove it before installing the new Eaton IPM software.) 52

53 Appendix A: IPM Pre-Installation Checklist Action Checked System that Displays the Web-based GUI Check the system that displays the Web-based GUI. The IPM graphical interface can be accessed remotely using a simple Web browser. Access to this interface can be secured through Secure Socket Layer (SSL) connection and is also secured through login and password. The Eaton IPM graphical interface has been tested with: Google Chrome Mozilla Firefox Microsoft Internet Explorer (IE) version 7 and later NOTE: For optimal performance, Google Chrome or Firefox is recommended. For good performance, IE version 9 and later is recommended. IE6 performance is not optimal. Java Runtime Environment (JRE) Prerequisites Check JRE prerequisites. For all features correlated to the infrastructure connector (like VMware, OmniCube) a JRE must be installed on the system hosting Eaton IPM (see JRE Installation on page 15 of the Eaton IPM Users Guide). If this prerequisite is not installed, only virtualization features are available, such as the legacy API for VMware connectors. JRE Installation The installation of the JRE is Operating System platform-dependent. All new Eaton components have been developed and tested for the Java version 1.6 or later. After installing the correct JRE, the IPM must be reloaded, to take account this new environment. User Accounts Ensure that the installation account is an account with local administrator rights. Network To configure alerts, the alert service needs access to the Mail Server. Confirm the following details for the Server hosting the alert agent: The Server has a connection with the Mail Server The host name of the Mail Server 53

54 Appendix A: IPM Pre-Installation Checklist 2015 Eaton. All rights reserved. IB152001EN. Eaton, Intelligent Power Manager and epdu are registered trademarks of Eaton. SimpliVity, the SimpliVity logo and OmniCube are registered trademarks or trademarks of SimpliVity Corporation in the United States and other countries. All other trademarks are the property of their respective owners. 54