OpenManage Integration for VMware vCenter Version 2.
© 2014 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. For Deployment ............................................................................................ 7 Table 4. For Management ............................................................................................ 7 Table 5. Management Support ......
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.1 integrates into the new vSphere Web Client in addition to the traditional vSphere Desktop client. NOTE: OpenManage Integration for VMware vCenter is available at the following location: http://www.dell.com/vcenterplugin.
Server PowerEdge PowerEdge PowerEdge PowerEdge PowerEdge PowerEdge PowerEdge Version M910 M915 T110 T310 T410 T610 T710 2.5.0 2.6.0 1.8.2 1.8.2 1.9.0 6.1.0 6.1.0 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 R320 R420 R520 R620 R720 R720xd R820 R920 1.0.3 1.2.4 1.2.4 1.2.4 1.2.6 1.2.6 1.2.6 1.7.2 1.1.
Table 3. For Deployment 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 Table 4. 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.
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 OMSA OMSA OMSA OMSA OMSA OMSA OMSA OMSA OMSA OMSA OMSA OMSA OMSA 6.5 7.0 7.0 7.2 7.2 7.1 7.1 7.3 7.4 7.1 7.3 7.4 7.4 VIB VIB VIB VIB VIB VIB VIB VIB VIB VIB VIB For Hypervisor deployment, OpenManage Integration for VMware vCenter supports the following: Table 6. Hypervisor Deployment Versions Hypervisor version ESX 4.1 OMSA version OMSA 6.5 ESXi 4.
Supported Browsers You can access the Administration Portal and the OpenManage Integration using the following browsers: Microsoft Internet Explorer, version 9 and 10 Mozilla Firefox, version 22 and later Google Chrome, version 28 and later 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.
Model T320 T420 T620 Features PowerEdge 11th Generation Servers Table 9. Model R210, R310, T410 R210 II R410 R415 R510 R515 R610 R710 R715 R810 R815 R905 R910 M610 M710 M710D M910 M915 T610 T710 VMware Version Support VMware versions ESX Classic ESX Classic, ESXi Embedded Table 10.
Model M910 M915 R715 R815 Features PowerEdge 10th generation servers Table 11. Model R200 T300 R300 M600 M605 T605 M805 R805 R900 R905 M905 VMware version support VMware versions ESX Classic ESX Classic, ESXi Embedded Table 12. Model R200 T300 R300 M600 M605 T605 M805 R805 R900 M905 Feature support Features SNMP Alerts Hardware Inventory Power On Server Blink Server LED View/Clear SEL logs Link and Launch iDRAC Warranty Information PowerEdge 9th Generation Servers Table 13.
Model PE2900 III VMware versions ESX Classic, ESXi Embedded PE2950 I/II ESX Classic PE2950 III ESX Classic, ESXi Embedded PE2970 ESX Classic, ESXi Embedded PE6950 ESX Classic Table 14. Feature Support Model All supported PowerEdge 9th generation servers Features SNMP alerts Hardware Inventory Power On Server Blink Server LED View/Clear SEL logs Link and Launch iDRAC Warranty Information PowerEdge Chassis Table 15.
Port Information NOTE: In the OpenManage Integration, when deploying the OMSA agent using the Fix non-compliant vSphere hosts link available in the Compliance window, the OpenManage Integration starts the http Client service, enables port 8080, and releases the port for ESXi 5.0 and higher to download and install OMSA VIB. After the OMSA installation is completed, the service automatically stops and the port is closed. Table 16.
Port Number Protocols Port Type Maximum Encryption Level Direction Usage Configurable 8080 HTTP TCP In HTTP server; downloads the OMSA VIB and fixes noncompliant vSphere hosts Remote Mail Check Protocol IMP Logical Address Maintenance Multicast DNS Internet Printing Protocol (IPP) Trivial File Transfer SUN Remote Procedure Call (Portmap) Bootstrap Protocol Client No 50 RMCP UDP/TCP 128-bit Out 51 IMP UDP/TCP None N/A 5353 631 mDNS IPP UDP/TCP UDP/TCP None All Out 69 TFTP UDP 1
server and BIOS settings pages and when you select a deployment template with an affected hardware profile during deployment. To resolve this issue, use one of the corresponding BIOS versions listed in Table 1 and Table 2. The web client support added in OpenManage Integration for VMware vCenter, version 2.0 requires vCenter Server 5.5 or later. Prior versions of vCenter are only supported with the standard desktop client. When restoring a backup from 1.7 to 2.
Issue 4: The deployment jobs that are in state “In Waiting" are not cancelled after the job is aborted from Job Queue. Description: The deployment jobs that are in the state "In Waiting" are not cancelled after the job is aborted from Job Queue. These jobs move to the "In Progress" state and are not cancelled. However, these jobs are available in the Deployment wizard the servers are showing for OSD. Resolution/Workaround: This defect does not affect the functionality of the features.
Issue 9: Host Name is not proper (same name is appended) for some host systems. Description: The host name is either displayed as “Unknown” or the host name is appended with the part of the same host name. This issue occurs in certain iDRAC versions and is resolved in later iDRAC versions. Resolution/Workaround: Upgrade to the latest iDRAC firmware. Make sure you restart the system after the upgrade. Version Affected: 2.0 and later Issue 10: The Initial Configuration wizard is displayed continuously.
e. To unregister the Web Client and .NET client, enter one at a time for this key in the value field for string type. com.dell.plugin.OpenManage_Integration_for_VMware_vCenter_WebClient com.dell.plugin.OpenManage_Integration_for_VMware_vCenter f. Click on the invokeMethod link. g. Register the plug-in again with the same VMware vCenter. h. Redo Alarms and Events enabling if it was enabled earlier. i. Redo Customized Alarms if it was customized earlier. Version Affected: 2.
Resolution/Workaround: You should try to use unique names while creating connection profiles. Versions Affected: 2.0 Issue 17: Using OpenManage Integration to update an Intel Network card with the firmware version of 13.5.2 is not supported. Description: There is a known issue with Dell PowerEdge 12th generation servers and some Intel Network cards with the firmware version of 13.5.2.
catalog file from the repository. This occurs if the catalog file is not reachable at the time the background process runs. Resolution/Workaround: After resolving any catalog connectivity issues that may exist, you can re-initiate the background process by changing the firmware repository location, and then setting it back to the original location. Allow about 5 minutes for the background process to complete.
Description: Navigating away from the firmware update page by selecting another host in the datacenter tree causes the update to fail. The update fails by not entering Maintenance mode and the reboot tasks will fail to initiate. Resolution/Workaround: You must close the wizard before selecting any another host in the inventory. Version Affected: All Issue 24: The Service Tag is not displayed during a firmware update.
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 28: 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 29: 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 31: 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 34: 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 39: 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.
Issue 14 Issue 15 Unable to get the warranty data. Inventory collection is very slow because the TestConnection Code added to each host before inventory is started. In version 2.0, upgrading OMSA to the latest version for ESXI 5.5 was unsuccessful. Unable to obtain the System ID after upgrading to version 2.0. Use OMSA 7.3.0.2 instead of OMSA 7.3.0.0 for ESXi 5.5. Unable to run firmware update after upgrading to version 2.0. Incorrect instruction displayed in the restore menu causes customer confusion.
