OpenManage Integration for VMware vCenter Version 3.
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 Release Type and Definition............................................................................................. 4 Version............................................................................................................................................................................... 4 Release Date.......................................................................................................................................................................
1 Release Type and Definition This document contains updated information for your OpenManage Integration for VMware vCenter (OMIVV) and any other technical documentation included with OpenManage Integration for VMware vCenter software. NOTE: You can access the technical artifacts of OpenManage Integration for VMware vCenter at, http:// en.community.dell.com/techcenter/systems-management/w/wiki/1961.
• The Auto discovery feature is not functional in this release. For more details about this, see OMIVV cannot act as a Provisioning Server during the Auto Discovery Process • In this release, RPM upgrade is not supported. You can deploy OMIVV OVF using either vSphere Client or vSphere Web Client and use Backup and Restore to upgrade from previous version of Spectre. • If you want to register multiple vCenter servers, all vCenter servers should be part of same single sign-on (SSO).
2 Known Issues The following section lists the open issues and resolutions with the OpenManage Integration for VMware vCenter: Issue 1: OMIVV cannot act as a provisioning server during the auto discovery process. Description: If OMIVV IP address is used as a provisioning server in the iDRAC settings for the newly added Dell servers, these Dell servers will not be auto discovered. The auto discovery process fails as OMIVV 3.
• http://kb.vmware.com/selfservice/search.do? cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2121701 • http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=D T_KB_1_1&externalId=2121689 • Dell OpenManage Integration for VMware vCenter 3.1 User's Guide for Web client Version Affected: 3.1 Issue 7: Firmware Update Wizard shows a message mentioning that the bundles are not retrieved from firmware repository.
Resolution/Workaround: Restart the system and check if the issue is resolved. If issue is not resolved, you may have to reset the iDRAC. Version Affected: All Issue 13: Chassis and server health is displayed as warning on the Chassis Summary page when server becomes critical. Description: When a critical entry is made to SEL logs, the health of the server (blade) changes to critical. This is correctly reflected on the Host Summary page. However, this is not reflected on the Chassis Summary page.
Resolution/Workaround: None Version Affected: 2.0 and later Issue 19: Hard disk option is not disabled in the Deployment wizard for all the servers that do not contain hard disk drives. Description: While navigating through the Deployment wizard, if the bare metal servers do not have any hard disk drive, then the hard disk option should be disabled on the Global Settings tab. However, the option is available for selection. Resolution/Workaround: None Version Affected: 2.
Description: After deploying Hardware Profile, the Virtual Disks are created on the physical server. However, the RAID levels are applied to the same order of the physical disks as in the reference server. Resolution/Workaround: None Versions Affected: All Issue 26: Sorting jobs with job name is incorrect in the firmware update Job Queue Description: The sort by name functionality in the firmware update Job Queue does not sorts the job queue appropriately. Resolution/Workaround: None Versions Affected: 1.
“Network card 'VirtualE1000' has a DVPort backing, which is not supported. This could be because the host does not support VDS or because the host has not joined a VDS.” Resolution/Workaround: Set the network interface to the VM Network during the OVF installation. After the virtual machine is created, remap the networking to the VDS port group. Version Affected: All Issue 31: The NIC connection status is not reflected correctly on Dell PowerEdge 12th generation servers.
Resolution/Workaround: Do the following steps to fix the issue: 1. Open RegEdit. 2. Navigate to the following location: KHEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings. 3. Add a new DWORD value for ReceiveTimeout. 4. Set the value to 30 seconds (30000). Try with higher value based on your environment requirements. 5. Exit RegEdit. 6. Restart Internet Explorer. NOTE: Just opening a new Internet Explorer window will not resolve this issue.
Version Affected: 1.6 and later Issue 37: Deployments failure error message displayed on R210 II machines. Description: Timeout issue on R210 II systems produces a hypervisor deployments failure error due to failure of BIOS to boot from attached ISO. Resolution/Workaround: Manually install hypervisor on the machine. Version Affected: 1.5.1 and later Issue 38: OpenManage Integration gets a security error message.
one of the registered vCenter was added to another registered vCenter. In this case the host on first vCenter appears as disconnected. Resolution/Workaround: Remove the host from the first vCenter where it is now showing as disconnected. Version Affected: All Issue 42: The NIC selected as the management NIC during the deployment process is not set as active management NIC after deployment.
Description: The overall health information is displayed Healthy on summary page for VRTX chassis that has a storage component as Warning. Resolution/Workaround: Storage component health status is shown correctly as Warning. Version Affected: VRTX firmware version 2.0 Issue 49: Fan information is showing as N/A for a chassis when a Fan is removed Description: Fan inventory information is displayed as N/A on Monitor page for M1000e chassis when a fan is removed from a slot. Resolution/Workaround: iDRAC GUI.
3 Installation Prerequisites For installation Pre-requisites, see the “OpenManage Integration for VMware vCenter 3.2 Installation Guide”.
4 Installation Procedure For complete installation instructions, see the "OpenManage Integration for VMware vCenter 3.2 Installation Guide".
5 Accessing documents from Dell support site You can access the required documents in one of the following ways: • Using the following links: – For all Enterprise Systems Management documents — Dell.com/SoftwareSecurityManuals – For OpenManage documents — Dell.com/OpenManageManuals – For Remote Enterprise Systems Management documents — Dell.com/esmmanuals – For OpenManage Connections Enterprise Systems Management documents — Dell.
6 Contacting Dell NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog. 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. To contact Dell for sales, technical support, or customer service issues: 1. Go to Dell.com/support. 2. Select your support category. 3.
