OpenManage Integration for VMware vCenter Version 2.
© 2013 Dell Inc. All rights reserved. Dell and its affiliates cannot be responsible for errors or omissions in typography or photography. Dell, the Dell logo, and PowerEdge are trademarks of Dell Inc. Intel and Xeon are registered trademarks of Intel Corporation in the U.S. and other countries. Microsoft, Windows, and Windows Server are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.
Contents Introduction .............................................................................................................. 5 OpenManage Integration for VMware vCenter Version 2.0. Quick Install .............................. 5 OpenManage Integration for VMware vCenter Version 2.0. User’s Guide .............................. 5 Context-sensitive help pages display by the user interface .............................................. 5 This Release Notes file ...........................
Tables Table 1. BIOS for Dell PowerEdge 11TH generation servers .................................................... 5 Table 2. BIOS for Dell PowerEdge 12TH generation servers .................................................... 6 Table 3. For deployment ............................................................................................. 6 Table 4. For management ........................................................................................... 7 Table 5. Management support ......
Introduction This file contains updated information for your OpenManage Integration for VMware vCenter and any other technical documentation included with OpenManage Integration for VMware vCenter software. The OpenManage Integration for VMware vCenter 2.0 integrates into the new vSphere Web Client in addidtion to the traditional vSphere Desktop client. NOTE: OpenManage Integration for VMware vCenter is available at http://www.dell.com/vcenterplugin.
Server Version PowerEdge M710HD 5.0.1 PowerEdge M910 PowerEdge M915 2.5.0 2.6.0 PowerEdge PowerEdge PowerEdge PowerEdge PowerEdge 1.8.2 1.8.2 1.9.0 6.1.0 6.1.0 T110 T310 T410 T610 T710 Table 2. BIOS for Dell PowerEdge 12TH generation servers System BIOS version T320 1.0.1 T420 1.0.1 T620 1.2.6 M420 1.2.4 M520 1.2.6 M620 1.2.6 M820 1.2.6 R320 R420 R520 R620 R720 R720xd R820 1.2.4 1.2.4 1.2.4 1.2.6 1.2.6 1.2.6 1.1.5 Table 3.
Table 4. For management Version iDRAC version for Dell PowerEdge 11th generation servers Lifecycle Controller for Dell PowerEdge 11th generation servers Lifecycle Controller for Dell PowerEdge 12th generation servers iDRAC version for Dell PowerEdge 12th generation servers Version number/Release date 3.35 for Modular, 1.85 for Rack or Tower 1.5.2 or later 1.0.0.3017 or later 1.00.
For Hypervisor deployment, we support the following: Table 6. Hypervisor deployment versions Hypervisor version ESX 4.1 OMSA version OMSA 6.5 ESXi 4.1 OMSA 6.5 VIB ESX 4.1 U1 OMSA 6.5 ESXi 4.1 U1 OMSA 6.5 VIB ESX 4.1 U2 OMSA/ 7.0 ESXi 4.1 U2 OMSA 7.0 VIB ESX 4.1 U3 OMSA/ 7.2 ESXi 4.1 U3 OMSA 7.2 VIB ESXi 5.0 OMSA 7.0 VIB ESXi 5.0 U1 OMSA 7.1 VIB ESXi 5.0 U2 OMSA 7.3 ESXi 5.1 OMSA 7.1 VIB ESXi 5.1 U1 OMSA 7.3 ESXi 5.5 OMSA 7.3.0.
Space required for provisioned storage The OpenManage Integration virtual appliance requires 37 GB of disk space for provisioned storage. PowerEdge 12th generation servers Table 7. VMware Version Support Model VMware versions ESX Classic, ESXi Installable R220 R320 R420 R520 R620 R720 R720XD R820 R920 M420 M520 M620 M820 T320 T620 Table 8.
PowerEdge 11th generation servers Table 9. VMware version support Model VMware versions ESX Classic ESX Classic, ESXi Embedded R210, R310, T410 R210 II R410 R415 R510 R515 R610 R710 R715 R810 R815 R905 R910 M1000e M610 M710 M710D M910 M915 T610 T710 Table 10.
PowerEdge 9th generation servers Table 13. VMware version support Model PE1950 PE1950 PE1955 PE2900 PE2900 PE2950 PE2950 PE2970 PE6950 VMware versions I/II III ESX ESX ESX ESX ESX ESX ESX ESX ESX I/II III I/II III Table 14.
Port information NOTE: When deploying the OMSA agent using the Fix non-compliant vSphere hosts link available from the Compliance window in the OpenManage Integration, the OpenManage Integration starts the http Client service and enables port 8080 and releases after ESXi 5.0 and higher to download OMSA VIB and install it. Once the OMSA installation is completed, the service automatically stops and the port is closed. Table 15.
Port Number Protocols Port Type UDP/TCP Maximum Encryption Level None 51 IMP 5353 631 Direction N/A mDNS IPP UDP/TCP UDP/TCP None All Out 69 TFTP UDP 128-bit All 111 NFS UDP/TCP 128-bit In 68 BOOTP UDP None Out Usage IMP Logical Address Maintenance Multicast DNS Internet Printing Protocol (IPP) Trivial File Transfer SUN Remote Procedure Call (Portmap) Bootstrap Protocol Client Configurable No No No No No No User notes OpenManage Integration for VMware vCenter only supports BI
This is a known issue from VMware and the resolution is in the VMware knowledge base article found here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displa yKC&externalId=2000476 or here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displa yKC&externalId=1035107 Incorrect warning is displayed on the vCenter Summary tab when the hypervisor was deployed and root password set to non-default as shown in the screen below.
If the proxy settings are provided in the configuration, then the proxy settings are used to access the Repository URL provided in the Administration Portal. However, if the URL to the Update Repository is an internal URL, then disable the proxy setting. If you do not disable the internal proxy setting, then the appliance attempts to connect to the URL with the proxy. SNMP community: The OpenManage Integration for VMware vCenter only supports the community name of Public.
Resolution/Workaround: If the user sees this behavior, go back to the step to select the bare metals and reselect the bare metals and continue with the wizard. Versions Affected: 1.5 and higher Issue 2: While applying RAID from reference server, the Physical disk order is not maintained as that on the reference server. Description: After deploying Hardware Profile profile the Virtula Disks are created on the physical server.
Note: When using the one-to-many firmware update, avoid selecting Intel network adapters that are at version 13.5.2, as this will fail and stop the update task from updating remaining servers. Version Affected: All Issue 6: Using the OpenManage Integration to upgrade a Broadcom NetXtreme II 10Gigabit Ethernet adapter (BCM57712) from firmware version of 6.2.x or less, or downgrade to a firmware version of 6.2.x or less is not supported.
Version Affected: All Issue 9: When Installing the OpenManage Integration for VMware vCenter I see the following error and cannot proceed. “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. Then once the virtual machine is created remap the networking to the VDS port group.
versions of the Lifecycle Controller firmware. This Lifecycle Controller defect will be addressed in a future Lifecycle Controller firmware release. Resolution/Workaround: None. Version Affected: All Issue 13: Navigating away from a firmware update by selecting another host in the datacenter tree causes the update to fail. Description: Navigating away from the firmware update page by selecting another host in the datacenter tree causes the update to fail.
Description: The registration of OpenManage Integration fails after upgrade to version 1.5.1 even if there is no earlier OpenManage Integration registered and the vCenter locale is one of the supported locales. The issue happens since some SQL scripts failed to execute during RPM update. Resolution/Workaround: It is recommended that you take backup before performing any RPM upgrade. Install the previous version of plugin prior to the upgrade and restore the DB.
Resolution/Workaround: Use the follow 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) [This may need to try higher value in your environment]. 5. Exit RegEdit. 6. Restart Internet Explorer. Note: Just opening a new Internet Explorer window is not enough. You must restart the Internet Explorer browser. 7.
generation servers at the time when inventory is run to determine if the OMSA is configured correctly. If OpenManage Integration was used to deploy ESX 4.1 base, u1, u2, u3, it installs and configures OMSA correctly. However, since SSH is not enabled, it shows the host as Not configured on the host compliance page. In addition, if ESX 4.1 was installed outside and OMSA was installed and configured using OpenManage Integration, and then the user turned off SSH later, the host shows as “Not configured.
due to failure of BIOS to boot from attached ISO. Resolution/Workaround: Manually install hypervisor on the machine. Version Affected: 1.5.1, 1.
Issue 24: OpenManage Integration gets a security error message. Description: Although the SSL Certificate is valid on a vCenter and user credentials are correct, a user encounters an error message saying , “There are either too many Virtual Management Console connections or an incorrect user name or password or session ID, or an incorrect SSL certificate. Please verify these items and try again.” Resolution/Workaround: This happens due to an invalid session in vCenter.
properly and try the firmware update again. Version Affected: 1.5.1, 1.6 and later Issue 27: Events from different vCenter posted to another vCenter from a shared OpenManage Integration Appliance. Description: This situation can occur when a bare-metal server that was deployed in one vCenter is rediscovered again as bare-metal server but then selected for a hypervisor deployed in another vCenter.
Issue 30: Rarely, an ESXi 4.1 U1 deployment fails on a PowerEdge server. Description: The ESXi deployment log shows failure installing OMSA. Resolution: This is a known VMware issue and VMware has provided a workaround to resolve the issue as seen here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&exte rnalId=1037190 Use these steps for a workaround: - Logon to ESXi 4.1 U1. Manually create a directory /tmp. Logoff from the ESXi host. Manually add the host to vCenter.
Issue 34: Hypervisor installation fails. Description: Hypervisor installation fails with the error The Job check status with ID of DCIM_OSConcreteJob:1 failed with the following error message: Mount network share failed – incorrect IP address or share name. Resolution: Restart the appliance. Version Affected: 1.5, 1.5.1, 1.6 and later Issue 35: NFS mount remains mounted after deploy is completed using ESXi5.
sometimes does not activate the button. Keyboard navigation is not supported at this time. Resolution: Use the mouse. Version Affected: All Issue 39: The ESXI install leaves behind a file after installation. Description: The ESXi install leaves behind a temporary file in the /store/resolv.conf (static IP only). Resolution: None, there is no impact to the functionality of the software. Version Affected: All Issue 40: Hosts are not in the Connection Profile shown from Health Status in Web Client page.
Issue 8 Issue 9 Issue 10 Issue 11 Issue 12 Issue 13 Issue 14 Issue 15 Issue 16 Issue 17 Issue 18 Issue 19 Issue 20 Issue 21 Issue 22 Issue 23 Custom Raid Configuration from UI is misleading. Hardware Profile for iDRAC/network settings has incorrect modifiable parameters. The Connection Profile of vCenter selected in Hypervisor Profile is not used for Deployment.
