OpenManage Integration for VMware vCenter Quick Install Guide for vSphere 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 Installing OpenManage Integration for VMware vCenter.............................4 Installation introduction........................................................................................................................ 4 Prerequisites.................................................................................................................................... 4 Migration Path to migrate from 2.x to 3.0.................................................................................
Installing OpenManage Integration for VMware vCenter 1 Installation introduction This guide provides step-by-step instructions for installing and configuring of the OpenManage Integration for VMware vCenter (OMIVV). Once the installation is complete,see OpenManage Integration for VMware vCenter User's Guide available at dell.
NOTE: The OMIVV shows the VMware Tools as Running (Out-of-date) when deployed on ESXi 5.5 and above. You can upgrade the VMware tools after a successful deployment of the appliance or anytime later, if desired. NOTE: It is recommended that the OMIVV and vCenter server are located on the same network. Hardware Requirements Following are the hardware requirements for OMIVV.
d. Register the OMIVV with vCenter server using the Administration Console. NOTE: Registering using FQDN (Fully Qualified Domain Name) is not mandatory, but is highly recommended. For both and IP (Internet Protocol) and FQDN based registrations, the hostname of the vCenter should be properly resolvable by the DNS server. 2. Complete the steps in the Configuration Wizard. 3. Enable Dell events to set up event filter options on the Settings page 4.
first time a block is written to. Subsequent writes have the same performance as eager-zeroed thick disks. b. Thick Provision Eager Zeroed [Recommended] An eager-zeroed thick disk has all the space allocated and zeroed out at the time of creation. This increases the time it takes to create the disk, but results in the best performance, even on the first write to each block. c.
Figure 1. Console tab 7. In the Date and Time tab, select the Synchronize date and time over the network. The NTP Servers box is displayed. 8. Add valid NTP server details to which your vCenter is synchronized with. 9. Click on Time Zone, and select the applicable time zone and click OK. 10. To configure static IP to the OMIVV appliance, Click on Network Configuration or, skip to step 17. 11. Select Auto eth0, and then click Edit. 12.
Figure 2. Administration Console 19. In the Administration Console login window, enter the password, and then click Login. Figure 3. vCenter Registration Window from within the Administration Console 20. In the vCenter Registration window, click Register a new vCenter Server. 21. On the Register a New vCenter window, do the following: a.
b. Under Admin User Account, in the Admin User Name text box, enter the Admin user name. Enter the username as domain\user or domain/user or user@domain. The Admin user account is used by the OMIVV for vCenter administration. NOTE: One instance of OMIVV can support upto 10 vCenters which are part of the same vCenter SSO. Multiple independent instances of vCenters are currently not supported. NOTE: Registering using FQDN is not mandatory but highly recommended.
3. In vSphere Client, click Plug-in → Managed Plug-in. In the Plug-in Manager window verify the OMIVV is installed and enabled. Migration Path to migrate from 2.x to 3.0 Do the following to migrate from older version to the OMIVV 3.0 version: 1. Take a Backup of the database for the older release. 2. Power off the older appliance from the vCenter. NOTE: Do not unregister the Plug-in from the vCenter.
Recover OpenManage Integration for VMware vCenter if the older plug-in is unregistered If you have unregistered the plug-ins after taking backup of the database of the older version, perform the following steps before proceeding with the migration. NOTE: Unregistering the plug-in removes all the customizations that was implemented on the registered alarms by the plug-in. The following steps will not be able to restore the customization. However, it will re-register the alarms in their default state. 1.
2 Configuring OpenManage Integration for VMware vCenter After you do the basic installation of the OMIVV, it needs to be configured. This is typically done using the Configuration Wizard, but you can also do it using the Settings page options in the Dell Management Center. The user interface in both the pane is similar except in the wizard, you Save and Continue, whereas in the Settings options you click Apply. This section tells you how to configure using the wizard.
NOTE: With installations on hosts that are using 12th or later generation of the Dell PowerEdge servers, the OMSA agent installation is not required. For installations on 11th generation servers, OMSA agent is automatically installed during the deployment process. NOTE: You are not allowed to create a connection profile if the number of hosts added exceeds the license limit for creating a Connection Profile To create a new connection profile using the wizard: 1.
To configure events and alarms: 1. 2. In the Configuration Wizard, under Event Posting Levels, select one of the following: • Do not post any events - Blocks hardware events. • Post All Events - Posts all hardware events. • Post only Critical and Warning Events - Posts only critical or warning level hardware events. • Post only Virtualization-Related Critical and Warning Events - Posts only virtualization-related critical and warning events; this is the default event posting level.
NOTE: To make sure that the OMIVV continues to display updated information, it is recommended that you schedule a periodic inventory job. The inventory job consumes minimal resources and will not degrade host performance. To schedule an inventory job: 1. In the Configuration Wizard, in the Inventory Schedule window, do one of the following: • 2. To run inventory schedules, click On Selected Days. • To not run inventory schedules, select Do not run inventory on Dell hosts.
NOTE: OMIVV acts as a provisioning server. The Deployment credentials are used to communicate with iDRAC that uses the plug-in as a provisioning server in the Auto Discovery process. To configure the deployment credentials: 1. In the Deployment Credential window you can view or change the credentials. 2. To change these credentials, under Credentials for Bare Metal Server Deployment, do the following: a. In the User name text box, edit the user name. b. In the Password text box, edit the password. c.
Enabling The OMSA Link [Wizard] To launch OMSA within the OMIVV virtual appliance, the OMSA Web Server must be installed and configured. See Dell OpenManage Server Administrator Installation Guide for instructions on how to install and configure the Web Server. NOTE: OMSA is only required on Dell servers prior to 12th Generation. You can use OMSA to: • Manage vCenter elements (detailed sensor/component-level health information). • Clear command logs and system event logs (SELs).
6. The server will be auto discovered upon next server boot. After successful Auto-Discovery, the root user gets enabled, and the Enable Auto-Discovery flag gets disabled automatically. Configuring NFS Shares To use NFS shares with the OMIVV for backup and restore operations, firmware updates, and as a staging folder, there are certain configuration items that you must complete. CIFS shares do not require additional configuration. To configure NFS shares: 1.
3 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.
• The Dell Management Console : Information about the license can be seen from within the integration. Licensing information is available from the Dell Management console’s overview page, or if using the web client, from the OMIVV Licensing tab. • License Messaging: There are several informational, error, or warning messages that can be displayed. a. License expiring soon: Starting within 30 days of a license expiration, a message will be displayed informing how many days are remaining for that license.
Stacking licenses Starting from OMIVV version 2.1, OMIVV has the ability to stack multiple standard licenses to increase the number of supported hosts to the sum of the hosts in the uploaded licenses. An evaluation license cannot be stacked. The number of supported vCenters cannot be increased by stacking, and would require the use of a multiple appliances. There are some restrictions around the functionality of stacking licenses.
More Configuration Information 4 For a complete guide on OMIVV configuration, management, and deployment options, see OpenManage Integration for VMware vCenter User's Guide available at Dell.com/support/manuals.
