OpenManage Integration for VMware vCenter Quick Installation Guide for vSphere Web Client Version 3.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. 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 © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Quick Start Installation........................................................................................ 5 Installation Introduction........................................................................................................................ 5 Prerequisites.......................................................................................................................................... 5 Hardware Requirements...............................................................
Replacement of Licenses ............................................................................................................. 25 Enforcement........................................................................................................................................25 Appliance Updates.........................................................................................................................25 Evaluation Licenses.................................................................
Quick Start Installation 1 Installation Introduction This guide provides step-by-step instructions for the installation and configuration of OpenManage Integration for VMware vCenter (OMIVV) on Dell servers. After the installation is complete, for information about all aspects of administration including: inventory management, monitoring and alerting, firmware updates, and warranty management, see the OpenManage Integration for VMware vCenter User's Guide available at dell.com/support/manuals.
Hardware Requirements OMIVV provides full support for several generation of Dell servers, with full feature support for servers with iDRAC Express or Enterprise. Extensive information on the platform requirements can be found in the OpenManage Integration for VMWare vCenter Release Notes available at Dell.com/support/ manuals. To verify that your host servers are eligible, refer to the tables in the OpenManage Integration for VMWare vCenter Compatibility Matrix available at Dell.com/support/manuals.
1. Install OMIVV. a. Be sure systems are connected and the vCenter server is up and running. b. Deploy the Open Virtualization Format (OVF) file that contains the OMIVV using the vSphere client or vSphere Web client.. c. Upload the license file. d. Register the OMIVV with vCenter server using the Administration Console. NOTE: Register using FQDN is highly recommended. For both IP / FQDN based registrations, the hostname of the vCenter should be properly resolvable by the DNS server. 2.
10. In the Select Name and Folder window, do the following: a. In Name, enter the name of the template. This name can contain up to 80 characters. b. In the Select a folder or datacenter list, select a location to deploy the template. 11. Click Next. The Select Storage window is displayed. 12. In the Select Storage window, do the following: a.
Figure 1. Console tab 5. To open the Administration Console for the product, open a Web browser and type the appliance's IP address or hostname. The IP address is the IP address of the appliance VM and not the ESXi host IP address. The Administration Console can be accessed by using the URL mentioned at the top of the console. For example: https://10.210.126.
Figure 2. Administration Console 6. In the Administration Console login window, enter the password, and then click Login. Figure 3. vCenter Registration Window from within the Administration Console 7. 10 In the vCenter Registration window, click Register New vCenter Server.
8. In the Register New vCenter Server window, do the following: a. Under vCenter Name, in the vCenter Server IP or Hostname text box, enter the server IP or hostname and then in the Description text box, enter the description that is optional. NOTE: Registering using Fully Qualified Domain Name (FQDN) is not mandatory but highly recommended. For both Internet Protocol (IP) and FQDN based registrations, the host name of the vCenter must be properly resolvable by the DNS server. b.
Installation Verification The following steps verify that the OMIVV installation was successful: 1. Close any vSphere Client windows and start a new vSphere Web Client. 2. Confirm that the OMIVV icon appears inside vSphere Web Client. 3. Make sure that vCenter can communicate with the OMIVV by attempting a PING command from the vCenter server to the virtual appliance IP address or hostname. 4. In vSphere Web Client, click Plug-ins → Managed Plug-ins. 5.
For more information, see the section Installation Verification in this guide to ensure the database migration is successful. 9. Run the Inventory on all the registered vCenters. NOTE: It is recommended that you run the inventory on all the hosts managed by the plug-in again after the upgrade. For more information, see the section Running Inventory Jobs for steps to run the inventory on demand. If the IP address of the new OMIVV version 3.
2 Understanding How to Configure or Edit the OpenManage Integration for VMware vCenter After you complete the basic installation of the OMIVV, the Initial Configuration Wizard is displayed when you click on the OMIVV icon. Use the Initial Configuration Wizard to configure the Settings on first launch. For subsequent instances use the Settings page. From the Initial Configuration Wizard you can create a connection profile, edit the settings of warranty, inventory, events and alarms.
• a specific vCenter • All available vCenters 1. In the Initial Configuration Wizard, click Next in the Welcome screen. 2. Select one vCenter or all vCenters from the vCenters drop-down list. Select an individual vCenter for those not configured yet or if you have added a new vCenter to your environment. The vCenter selection page allows you to select one or more vCenters to configure settings. 3. Click Next to proceed to the Connection Profile description page.
• For iDRACs already configured and enabled for Active Directory on which you want to use Active Directory, select the Use Active Directory ; otherwise skip down to configure the iDRAC credentials. – In Active Directory User Name , type the user name. Type the username in one of these formats: domain/username or username@domain. The user name is limited to 256 characters. Refer to Microsoft Active Directory documentation for user name restrictions. – In Active Directory Password , type the password.
b. First character must be alphabetical c. Cannot contain a space d. Invalid characters: " / \ : | , * ? < > ~ ! @ # $ % ^ & ' ( ) { } _ – In Active Directory Password, type the password. The password is limited to 127 characters. – In Verify Password, type the password again. – Perform one of the following actions: • * To download and store the Host certificate and validate it during all future connections, select Enable Certificate Check.
NOTE: Chassis gets discovered automatically after the inventory for all hosts is run. If the chassis is added to a chassis profile, then the chassis inventory automatically runs. In a SSO environment having multiple vCenters, the chassis inventory runs automatically with every vCenter when the inventory for any vCenter is run at a scheduled time. To schedule an inventory job: 1. In the Configuration Wizard, in the Inventory Schedule window, select Enable Inventory Data Retrieval if it is not enabled.
To configure events and alarms: 1. In the Initial Configuration Wizard, under Event Posting Levels, select one of the following: • Do not post any events - Block hardware events. • Post All Events - Post all hardware events. • Post only Critical and Warning Events - Post only critical or warning level hardware events. • 2. Post only Virtualization-Related Critical and Warning Events - Post only virtualization-related critical and warning events; this is the default event posting level.
NOTE: Chassis will be discovered and available to be associated with the Chassis Profile only after the successful inventory run of any modular host present under that chassis. 6. To select either an individual chassis or multiple chassis, select the corresponding check boxes next to the IP/Host Name column. If the selected chassis is already a part of another profile then a warning message is displayed, stating that the selected chassis is associated with a profile.
Additional Configuration Settings 3 The following configuration settings are optional. However, it can be used for monitoring the hosts in your VMware vCenter using the plug-in. • Warranty Expiration Notification • Firmware Update Repository • OMSA Web Server URL Warranty Expiration Notification Viewing Warranty Expiration Notification Settings 1. In the OMIVV, click Manage → Settings tab. 2. Under Appliance Settings, click Warranty Expiration Notification.
Firmware Update Repository In OMIVV, in the Settings tab, you can set the location from which the servers can receive firmware updates. This is a global setting. Firmware repository settings contain the firmware catalog location used to update deployed servers. Following are the locations: • Dell (ftp.dell.com) — Uses the firmware update repository of Dell (ftp.dell.com). The OMIVV downloads selected firmware updates from Dell repository.
NOTE: OMSA is only required on Dell PowerEdge 11th generation servers. 1. In OMIVV, click Manage → Settings. 2. Under vCenter Settings , to the right side of the OMSA Web Server URL, click Edit. 3. In the OMSA Web Server URL dialog box, type the URL. You must include the full URL including HTTPS and the port number. For example, https://10.0.0.1:1311 or https://omsaurl:1311 4. Select Apply these settings to all vCenters to apply the OMSA URL to all vCenters.
4 Licensing in OpenManage Integration for VMware vCenter This chapter provides details about licensing in OMIVV. There are no new licensing changes for 3.0. NOTE: The Licensing for OMIVV will not alter the number of vCenter connection licenses. The maximum number of vCenter licenses is 10. If you want to register multiple vCenters, all vCenters should be part of same SSO. Separate instances of vCenters are not supported in this OMIVV release. License Types With version 3.0 there are two types of licenses.
NOTE: The license file may come to you packaged inside a zip file. Be sure to unzip the zip file and upload only the license .xml file. The license file will likely be named based on your order number (i.e 123456789.xml) 4. The Upload License file should display a success message if the license upload was successful. Options After Uploading Licenses License file for new purchases When purchasing a new license, an e-mail will be sent from Dell containing the new license file.
Evaluation Licenses When an evaluation license expires, several key areas will cease to work, and display an error message. Adding Hosts to Connection Profiles When attempting to add a host to a connection profile, if the number of licensed 11th Generation or newer hosts is exceeded and beyond the license number, adding additional hosts is prevented.
