OpenManage Integration for VMware vCenter Version 2.
© 2015 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 BIOS/iDRAC Co-requirement for Lifecycle Controllers ........................................................... 5 Hardware and Software Requirements .............................................................................. 7 Supported Browsers ....................................................................................................
Tables Table 1. BIOS for Dell PowerEdge 11TH Generation Servers.................................................... 5 Table 2. BIOS for Dell PowerEdge 12TH Generation Servers.................................................... 6 Table 3. BIOS for Dell PowerEdge 13TH Generation Servers.................................................... 6 Table 4. iDRAC and Lifecycle Controller for Deployment ...................................................... 7 Table 5.
Introduction This document 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.3now supports PowerEdge 13th Generation Servers. Also the SNMP V2 traps are now supported in the OpenManage Integration for VMware vCenter. It also integrates into the new vSphere Web Client in addition to the traditional vSphere Desktop client.
Server Version PowerEdge M610 PowerEdge M610x PowerEdge M710HD 6.1.0 6.1.0 5.0.1 PowerEdge PowerEdge PowerEdge PowerEdge PowerEdge PowerEdge PowerEdge 2.5.0 2.6.0 1.8.2 1.8.2 1.9.0 6.1.0 6.1.0 M910 M915 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 R220 1.0.3 R320 1.2.4 R420 1.2.4 R520 1.2.4 R620 1.2.6 R720 1.2.6 R720xd 1.2.6 R820 1.7.
Table 4. iDRAC and Lifecycle Controller for Deployment Generation Version Dell PowerEdge 11th generation servers Dell PowerEdge 12th generation servers Dell PowerEdge 13th generation servers Table 5. iDRAC 3.35 for Modular, 1.85 for Rack or Tower 1.00.0 or later Lifecycle Controller 1.5.2 or later 2.00.0 or later 2.00.00.00 or later 1.0.0.
For the management, OpenManage Integration for VMware vCenter supports the following: Table 6. Hypervisor version ESX 4.1 ESXi 4.1 ESX 4.1 U1 ESXi 4.1 U1 ESX 4.1 U2 ESXi 4.1 U2 ESXi 4.1 U3 ESX 4.1 U3 ESXi 5.0 ESXi 5.0 U1 ESXi 5.0 U2 ESXi 5.0 U3 ESXi 5.1 ESXi 5.1 U1 ESXi 5.1 U2 ESXi 5.5 ESXi 5.5 U1 ESXi 5.5 U2 Management Support OMSA version OMSA 6.5 OMSA 6.5 VIB OMSA 6.5 OMSA 6.5 VIB OMSA 7.0 OMSA 7.0 VIB OMSA 7.2 VIB OMSA 7.2 OMSA 7.1 VIB OMSA 7.1 VIB OMSA 7.3 VIB OMSA 7.4 VIB OMSA 7.1 VIB OMSA 7.
Hypervisor version ESXi 5.1 OMSA version 7.4 ESXi 5.1 U1 7.4 ESXi 5.1 U2 7.4 ESXi 5.5 7.4 ESXi 5.5 U1 OMSA is not required on PowerEdge 12th Generation servers OMSA is not required on PowerEdge 12th and 13th Generation servers ESXi 5.5 U2 Notes Use the Dell Custom inclusions. Use the Dell Custom inclusions. Use the Dell Custom inclusions. Use the Dell Custom inclusions. Use the Dell Custom inclusions.
Supported ESXi Versions on Hosts The following ESXi versions are supported on the hosts managed by OpenManage Integration for VMware vCenter, version 2.3. Table 9. ESXi Versions Supported on Hosts 9th Generation ESX/ESXi Version ESX v4.1 Y Supported Platforms 10th 11th 12th Generation Generation Generation 13th Generation Y Y N N ESXi v4.1 Y Y Y N N ESX v4.1 U1 Y Y Y N N ESXi v4.1 U1 Y Y Y N N ESX v4.1 U2 Y Y Y Y N ESXi v4.1 U2 Y Y Y Y N ESX v4.
Features 9th Generation 10th Generation Platform 11th Generation 12th Generation 13th Generation Power On Server Bare Metal Hypervisor Deployment Y Y Y Y Y N N Y Y Y Hardware Configuration N N Y Y Y Blink Server LED Y Y Y Y Y View/Clear SEL logs Y Y Y Y Y Link and Launch iDRAC Change Configuration Settings Y Y Y Y Y N N Y Y Y Warranty Information Y Y Y Y Y Supported Features on PowerEdge Chassis The following features supported on the PowerEdge Chassis man
Port Number 443 443 4433 2049 40014004 5432 11620 Protocols Port Type Maximum Encryption Level Direction Agent HTTPS WSMAN TCP TCP 128-bit 128-bit In In/Out HTTPS NFS NFS TCP UDP/TCP UDP/TCP 128-bit None None In All All Postgres SNMP Agent TCP UDP 128-bit None All In Table 13.
Important Notes • OpenManage Integration for VMware vCenter only supports BIOS mode to auto-deploy hypervisor on the target server. Make sure that you have BIOS mode selected in the reference hardware profile prior to applying the Hypervisor profile. If there is no hardware profile selected, then make sure to manually configure the boot mode as BIOS and reboot the server prior to applying the hypervisor profile.
Resolution/Workaround: None. The plugin does not support software RAID. If the system has software RAID it will show incorrect disks. Version Affected: All Issue 2: The validations enforced for verifying format of CIFS credentials to access single DUP are not correct. Description: The username for the CIFS share in single DUP firmware update does not accept the format username@domain for the domain or username. Resolution/Workaround: Use the format domain/username or domain\username.
Version Affected: All Issue 7: Memory data displays a negative value for a host after successful inventory. Description: The Total Memory capacity displays as “0” and Memory Installable displays a negative value on the Host Memory overview page. This issue occurs because of some issue in the iDRAC. Resolution/Workaround: Restart the system and check if the issue is resolved. If issue is not resolved, you may have to reset the iDRAC.
Resolution/Workaround: None Version Affected: 2.0 and later Issue 12: Dell Integration plugin does not post events corresponding to fluid cache to the vCenter. Description: Events related to Fluid Cache are not posted to vCenter using the Dell Integration plugin. The plugin ignores the traps related to Fluid cache because the plugin is currently not monitoring the fluid cache. Resolution/Workaround: None Version Affected: 2.
Resolution/Workaround: The IP address of the 2.3 appliance must be the same as the 2.0 appliance for the plugin to work correctly after restore. Version Affected: 2.3 Issue 17: For an RPM upgrade appliance, Alarms and Events settings are not restoring after backup and restore. Description: If the appliance is backed up using the release 2.3 build 23 and then restored on a new appliance, the registered vCenter information and Alarms and Events settings on each vCenter are not restored.
Issue 19: While applying RAID from reference server, the physical disk order is not maintained as it is in the reference server. 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.
Issue 23: Firmware upgrade or downgrade of Broadcom NetXtreme II 10Gigabit Ethernet adapter (BCM57712) from firmware version of 6.2.x or earlier is not supported. Description: Using the OpenManage Integration to upgrade a Broadcom NetXtreme II 10Gigabit Ethernet adapter (BCM57712) from firmware version of 6.2.x or earlier, or downgrade to a firmware version of 6.2.x or earlier is not supported.
PowerEdge 12th generation servers. This is due to a defect in recent 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 27: Navigating away from a firmware update by selecting another host in the datacenter tree causes the update to fail.
Resolution/Workaround: Reset the iDRAC to fix the issue of iDRAC not being responsive, and then rerun the inventory. If the inventory is able to get the iDRAC IP, then the host will be associated with the correct connection profile. Version Affected: 1.6 and later Issue 31: A communication error message is displayed after clicking the Firmware link from vSphere Client.
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. You must restart the Internet Explorer browser. Version Affected: 1.5 and later Issue 32: After deploying ESX 4.1U3 (800380), OMSA is not configured. Description: ESX 4.
drop-down, and provided to help identify the network interfaces. The DHCP reservation and DNS entry should be created for the server prior to scheduling the deployment, and if properly configured, should set the hostname to the value from DNS. Version Affected: 1.6 and later Issue 34: 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.
Version Affected: 1.5.1 and later Issue 37: A firmware update fails with an error message saying that USC is in use and it must be retried after 30 seconds. Description: During a firmware update if the update fails with the error message “If USC is in use, wait until USC has exited and retry the action. Otherwise retry after 30 seconds to check if network connectivity caused this error.
Resolution/Workaround: Restart the appliance. Version Affected: 1.5 and later Issue 42: NFS mount remains mounted after successful deployment using ESXi 5.0. Description: After the hypervisor deployment is completed and the host is added to the vCenter tree, there is an entry in the Summary page under the data sources called “remoteinstall-location (inactive) (unmounted)” for the new host added. Resolution/Workaround: None. Version Affected: 1.
Resolved Issues The following issues were reported in earlier releases of the OpenManage Integration and have been resolved in this release: Issue Issue 1 Issue 2 Issue 3 Issue 4 Issue 5 Issue 6 Issue 7 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 Issue 24 Issue 25 Issue 26 Description Unable to access VMware vCenter using the FQDN or DNS short name.
Issue 27 The Dell icon is not displayed in the web client version of the OpenManage Integration for VMware vCenter. 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.
