OpenManage Integration for VMware vCenter Version 4.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction................................................................................................................................. 4 OpenManage Integration for VMware vCenter licensing.................................................................................................4 License requirements for hosts and vCenter servers................................................................................................. 4 Buying and uploading software license....................
1 Introduction This guide provides step-by-step instructions for installing and configuring OpenManage Integration for VMware vCenter (OMIVV) for use with PowerEdge servers. After the OMIVV installation, for information about all aspects of administration including—inventory management, monitoring and alerting, firmware updates, and warranty management; see OpenManage Integration for VMware vCenter User's Guide available at Dell.com/support/manuals.
Buying and uploading software license You are running a trial license until you upgrade to a full product version. Use the Buy License link from the product to navigate to the Dell website and buy a license. After you buy it, upload it using the Administration Console. NOTE: The Buy License option is displayed only if you are using a trial license. 1. In the OpenManage Integration for VMware vCenter, perform one of the following tasks: • • In the Licensing tab, next to Software License, click Buy License.
Evaluation License When an evaluation license expires, several key areas cease to work, and an error message is displayed. Adding hosts to connection profiles When you attempt to add a host to a connection profile, if the number of licensed 11th Generation or newer hosts exceeds beyond the number of licenses, adding extra hosts is prevented. Important notes for reference • • • From OMIVV 4.0 onwards, only VMware vSphere Web client is supported and the vSphere Desktop client is not supported.
BIOS, iDRAC, Lifecycle Controller versions The BIOS, iDRAC, and the Lifecycle Controller versions required to enable the features of OpenManage Integration for VMware vCenter are listed in this section. It is recommended that you use the Bootable ISO created by using Repository Manager, or Lifecycle Controller's Platform to update your servers to one of the following base versions before using OMIVV: Table 2. BIOS for PowerEdge 11th generation servers Server Minimum version PowerEdge R210 1.8.
Server Minimum version M820 1.2.6 or later R220 1.0.3 or later R320 1.2.4 or later R420 1.2.4 or later R520 1.2.4 or later R620 1.2.6 or later R720 1.2.6 or later R720xd 1.2.6 or later R820 1.7.2 or later R920 1.1.0 or later Table 4. BIOS for PowerEdge 13th generation servers Server Minimum version R630 1.0.4 or later T630 1.0.4 or later R730 1.0.4 or later R730xd 1.0.4 or later R430 1.0.2 or later R530 1.0.2 or later R830 1.0.2 or later R930 1.0.2 or later T130 1.0.
Table 6. iDRAC and Lifecycle Controller for deployment Generation Version iDRAC Lifecycle Controller PowerEdge 11th generation servers 3.35 for Modular, 1.85 for Rack or Tower 1.5.2 or later PowerEdge 12th generation servers 1.00.0 or later 1.0.0.3017 or later PowerEdge 13th generation servers 2.30.30.30 or later 2.30.30.30 or later PowerEdge 14th generation servers 3.00.00.00 3.00.00.00 Model BIOS iDRAC with Lifecycle Controller C6320 1.0.2 2.30.30.30 or later C4130 1.0.2 2.30.30.
Supported features on PowerEdge chassis This topic provides information about the supported features on the PowerEdge chassis. Table 9. Supported features on modular infrastructure Features M1000e VRTX FX2s SNMP Alerts Y Y Y Hardware Inventory Y Y Y Link and Launch CMC Y Y Y License Information N/A Y Y Warranty Information Y Y Y Health Reporting Y Y Y Space required for provisioned storage The OMIVV virtual appliance requires at least 44 GB of disk space for provisioned storage.
ESXi version support Server generation 11G 12G 13G 14G v5.1 U2 Y Y Y N v5.1 U3 Y Y Y (except M830, FC830, and FC430) N v5.5 Y Y N N v5.5 U1 Y Y N N v5.5 U2 Y Y Y N v5.5 U3 Y Y Y N v6.0 Y Y Y N v6.0 U1 Y Y Y N v6.0 U2 Y Y Y N v6.0U3 Y Y Y N v6.5 N Y Y Y v6.5U1 N Y Y Y The OpenManage Integration for VMware vCenter supports any of the following vCenter server versions: Table 11.
Table 12.
Port Number Protocols Port Type Maximum Encryption Level Direction Usage Configurable 69 TFTP UDP 128-bit In/Out Trivial File Transfer No 111 NFS UDP/TCP 128-bit In SUN Remote Procedure Call (Portmap) No 68 BOOTP UDP None Out Bootstrap Protocol Client No Prerequisite checklist Checklist before you start the product installation: • • • • • • Verify that you have user name and password for OMIVV to access the vCenter server.
Deploying OMIVV OVF using vSphere web client Ensure that you have downloaded and extracted the product .zip file, Dell_OpenManage_Integration_..zip from the Dell website. 1. Locate the OMIVV virtual disk that you downloaded and extracted, and run Dell_OpenManage_Integration.exe. The supported client OS version for extracting and running the exe is Windows 7 SP1 and later. The supported server OS version for extracting and running the exe is Windows 2008 R2 and later. 2.
Registering vCenter server by non-administrator user You can register vCenter servers for the OMIVV appliance with vCenter administrator credentials or a non-administrator user with the necessary privileges. To enable a non-administrator user with the required privileges to register a vCenter server, perform the following steps: 1. To change the privileges selected for a role, add the role and select the required privileges for the role or modify an existing role.
NOTE: Assign the following privileges, if you are using VMware vCenter 6.5 or upgrading to vCenter 6.5 or later: • • Host.Config • Advanced settings • Connection • Maintenance • Query patch • Inventory Security profile and firewall • • • • Add host to cluster Add standalone host Modify cluster NOTE: Ensure that you assign the modify cluster privilege, if you are using vCenter 6.5 or upgrading to vCenter 6.5 or later.
NOTE: For all vCenter operations, OMIVV uses the privileges of the registered user and not the privileges of the loggedin user. NOTE: If specific pages of OMIVV are accessed with no Dell privileges assigned to the logged-in user, the 2000000 error is displayed. Registering OpenManage Integration for VMware vCenter and importing license file Ensure that your licenses are ready for download at http://www.dell.com/support/licensing.
9. Click Time Zone and select the applicable time zone, and click OK. 10. To configure static IP to the OMIVV appliance, click Network Configuration, or skip to step 17. 11. Select Auto eth0, and then click Edit. 12. Select the IPV4 Settings tab, and select Manual in the Method drop-down. 13. Click Add, and then add a valid IP, Netmask, and Gateway information. 14. In the DNS Servers field, provide the DNS server detail. 15. Click Apply. 16.
Figure 3. vCenter registration window from Administration Console 20. In the vCenter Registration window, click Register a New vCenter Server. 21. In the Register a New vCenter Server window, perform the following substeps: a) Under vCenter Name, in the vCenter Server IP or Hostname text box, enter the server IP or host name, and then in the Description text box, enter a description. The description is optional.
Figure 4. OpenManage Integration for VMware vCenter successfully added to vCenter For all vCenter operations, OMIVV uses the privileges of a registered user and not the privileges of a logged-in user. For example: User X with the necessary privileges registers OMIVV with vCenter, and user Y has only Dell privileges. User Y can now log in to the vCenter and can trigger a firmware update task from OMIVV.
Migrating from earlier version to 4.1 You can start with a fresh deployment of the v4.1 OVF after uninstalling an earlier version and then migrate the data from earlier version (3.x) to 4.1 version by using backup and restore path. To migrate from an earlier version to the OMIVV 4.1 version, perform the following steps: 1. Take a backup of the database for an earlier (v3.x) release. For more information about backup, see OpenManage Integration for VMware vCenter User’s Guide available at Dell.
NOTE: Unregistering the plug-in removes all the customization that was implemented on the registered alarms by the plug-in. The following steps do not restore the customization. However, it re-registers the alarms in their default state. 1. Perform step 3 through step 5 in Migrating from earlier version to 4.1. 2. Register the plug-in to the same vCenter that you had registered in the earlier plug-in. 3. To complete the migration, perform step 6 through step 9 in Migrating from earlier version to 4.1.
2 Appliance configuration for VMware vCenter After you complete the basic installation of OMIVV and registration of the vCenters, the Initial Configuration Wizard is displayed when you click the OMIVV icon. You can proceed to configure the appliance by using one of the following methods: • • Configuring the appliance through the Initial Configuration Wizard. Configuring the appliance through the Settings tab in OMIVV.
Select a vCenter that is not configured yet or if you have added a vCenter to your environment. The vCenter selection page allows you to select one or more vCenters to configure settings. 3. To proceed with the Connection Profile Description dialog box, click Next. NOTE: If you have multiple vCenter servers that are part of the same single sign-on (SSO), and if you choose to configure a single vCenter server, repeat steps 1 through 3 until you configure each vCenter.
• Between 1 and 64 characters long • No nonprintable characters • No Invalid characters, such as " / \ [ ] : ; | = , + * ? < > @ Host domain requirements: • Between 1 and 64 characters long • First character must be alphabetical. • Cannot contain a space. • No Invalid characters, such as " / \ [ ] : ; | = , + * ? < > @ b. In Active Directory Password, type the password. The password is limited to 127 characters. c. In Verify Password, type the password again. d.
NOTE: The chassis gets discovered automatically after the inventory for all hosts is run. If the chassis is added to a chassis profile, the chassis inventory automatically runs. In an SSO environment with multiple vCenter servers, the chassis inventory runs automatically with every vCenter when the inventory for any vCenter is run at a scheduled time. NOTE: The settings in this page are reset to default each time the configuration wizard is invoked.
2. To enable all hardware alarms and events, select Enable Alarms for all Dell EMC Hosts. NOTE: The Dell EMC hosts that have alarms enabled respond to some specific critical events by entering in to maintenance mode and you can modify the alarm, when required. The Enabling Dell EMC Alarm Warning dialog box is displayed. 3. To accept the change, click Continue, or to cancel the change, click Cancel. NOTE: Ensure that you complete this step only if you select Enable Alarms for all Dell EMC Hosts. 4.
a) If you want to enable this setting, select the Enable warranty expiration notification for hosts. Selecting the check box enables warranty expiration notification. b) Under Minimum Days Threshold Alert, do the following: 1. In the Warning drop-down list, select the number of days before you want to be warned of the warranty expiration. 2. In the Critical drop-down list, select the number of days before you want to be warned of the warranty expiration. 5. Click Apply.
iDRAC credentials as provided in the connection profile. If you change the deployment credentials, all newly discovered systems from that point onwards are provisioned with the new credentials. However, the credentials on servers that are discovered prior to the change of deployment credentials are not affected by this change. NOTE: OMIVV acts as a provisioning server.
NOTE: To receive the Dell events, enable both alarms and events. 1. In the OpenManage Integration for VMware vCenter, on the Manage > Settings tab, under vCenter settings, expand Events and Alarms. The current vCenter Alarms for Dell EMC Hosts (Enabled or Disabled) or all vCenter alarms, and Event Posting Level are displayed. 2. Click the icon at the right side of Events and Alarms. 3. To enable all hardware alarms and events, select Enable Alarms for all Dell EMC Hosts.
b. In the Description text box, enter description, which is optional. Under the Credentials section: a. In the User Name text box, type the user name with administrative rights, which is typically used to log in to the Chassis Management Controller. b. In the Password text box, type the password for the corresponding user name. c. In the Verify Password text box, enter the same password you have entered in the Password text box. The passwords must match.
3 Accessing documents from the Dell EMC support site You can access the required documents in one of the following ways: • Using the following links: • • • • • • For Dell EMC Enterprise Systems Management, Dell EMC Remote Enterprise Systems Management, and Dell EMC Virtualization Solutions documents — www.dell.com/esmmanuals For Dell EMC OpenManage documents — www.dell.com/openmanagemanuals For iDRAC documents — www.dell.
4 Related Documentation In addition to this guide, you can access the other guides available at Dell.com/support. Click Choose from all products, then click Software and Security > Virtualization Solutions. Click OpenManage Integration for VMware vCenter 4.1 to access the following documents: • • • OpenManage Integration for VMware vCenter Version 4.1 Web Client User's Guide OpenManage Integration for VMware vCenter Version 4.1 Release Notes OpenManage Integration for VMware vCenter Version 4.
