OpenManage Integration for VMware vCenter Version 5.
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. © 2010 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Release summary..........................................................................................................................4 Priority and recommendations............................................................................................................................................. 4 2 Compatibility............................................................................................................................... 5 Supported devices and platforms..............
1 Release summary The OMIVV 5.1 release supports vSphere 7.0 and firmware management using vSphere Lifecycle Manager. For information, see New and enhanced features. Version 5.1 Release date April 2020 Priority and recommendations Recommended: Dell EMC recommends applying this update during your next scheduled update cycle. The update contains feature enhancements or changes that help keep your system software current and compatible with other system modules (firmware, BIOS, drivers, and software).
2 Compatibility Supported devices and platforms For more information about supported devices and platforms, see the Hardware Requirements section in the OpenManage Integration for VMware vCenter Version 5.1 Installation Guide. Supported operating system ESXi version support • • • • v6.0 U3 v6.5, v6.5 U1, v6.5 U2, v6.5 U3 v6.7, 6.7 U1, v6.7 U2, v6.7 U3 v7.0 vCenter version support • • • v6.5 U2, v6.5 U3 v6.7, v6.7 U1, v6.7 U2, v6.7 U3 v7.0 NOTE: Use the latest patch build 13638625 or later for vCenter 6.
3 New and enhanced features • • • • 6 Support for vSphere 7.
4 Fixes This release provides fixes for the following issues: • • • • • • • • • • • • • • • • • • • 113924: When performing backup and restore, error message that is displayed is not informative in admin portal if the invalid username is entered. 124012: Testing iDRAC connectivity in a host credential profile using an incorrect password locks the iDRAC access to the appliance until the penalty time configured in iDRAC.
5 Important notes 1. The following are the important items to note before upgrading to OMIVV 5.1: a. From OMIVV 5.0 onwards, only VMware vSphere Client (HTML5) is supported and the vSphere Web Client (FLEX) is not supported. b. 11G servers are not supported. Only the 12G and later generations servers are retained after restore. c. Hardware profiles and deployment templates are not supported.
6 Known issues • Issue 1: iDRAC might not send an event when your system reboots. Description: Sometimes, the iDRAC might not send an event when your system reboots. In this case, OMIVV sends latest health update notification by polling mechanism and you receive the latest health update within an hour. • Version affected: 4.0 and later Issue 2: iDRAC license type and description are displayed incorrectly for non-compliant vSphere hosts.
• Issue 7: System Event Logs are not showing in OpenManage Integration for VMware vCenter when power supply redundancy is lost. Description: When the power redundancy is lost on the PowerEdge modular servers, the system logs get cleared. Version affected: 3.0 and later • Resolution/Workaround: None Issue 8: Chassis and server health is displayed as warning on the Chassis Summary page when server becomes critical.
Description: OS deployment is failing on 12th generation PowerEdge servers with the following error on the screen during POST: "Warning: Unable to boot to Service Partition." There is a BIOS issue to identify the network ISO when there is a local USB CD-ROM installed on the system and that USB CD- ROM is the only USB mass storage device plugged into the system. Version affected: 1.5.
the same fc.chassislot ID on the target server but fails. The System profiles searches for exact instance( FQDD) while applying the profile, which works successfully on rack servers (identical), but may have few restrictions in modular servers. For example, in FC640, the System profiles that are created from one modular server cannot be applied on other modular servers in the same FX chassis because of NIC level restrictions. Version Affected: OMIVV 4.
Description: The storage data may not be displayed for an MX host managed using the chassis credential profile and for a host present in the member chassis. Though the inventory data of other components is displayed, only the storage-related data is not displayed Resolution: Do one of the following: 1. Update the MX7000 chassis firmware version to 1.00.10. 2. Manage the host using iDRAC. 3. Reinstall the host in another slot of the same MX7000 chassis and retry the operation. • Version Affected: 4.
If you downgrade MX chassis firmware from higher version to lower using OMIVV, OMIVV shows the job as In Progress for a long time (up to 6 hrs) and eventually reports failure of downgrade operation. But, the downgrade operation is successfully completed. Resolution: Downgrade firmware using OME-Modular. Version Affected: 5.
7 Features and fixes in previous releases Version 5.0.1 Release Date January 2020 Features and enhancements The OMIVV 5.0.1 is a defect fix Release. Fixed issues This release provides fixes for the following issues: • • OMIVV becomes unresponsive after you configure alert management in the Admin Portal. Inventory might fail after you add ESXi 6.7 to host credential profile. Version 5.
• • • Enhancement in deployment mode to support for 2000 hosts with extra large mode Support for dual network adapter for OMIVV Dashboard to monitor host and chassis Fixed issues • • • • • • • • • 16 Fixed an issue where invalid data is displayed for physical disks and virtual disks at datacenter and cluster inventory intermittently. Fixed an issue where initial configuration wizard displayed even if you click Do Not Show Again option.
8 Limitations The following are the limitations for this release of OMIVV: • • • If the Dell Cloud server model C6320 contains H730 controller and micro SD card in the riser, the micro SD card might not be detected in some situations. This limits the OS deployment on the SD card. In the Dell Cloud server model C6320, deployment through LSI 2008 is not supported. OMIVV cannot access files from SMB version 3 based CIFS.
9 Instructions for installing Downloading the software package For more information about downloading OMIVV, see the Download OpenManage Integration for VMware vCenter topic in the OpenManage Integration for VMware vCenter Version 5.1 Installation Guide at www.dell.com/support. Installation prerequisites For the installation prerequisites, see the Prerequisite checklist topic in the OpenManage Integration for VMware vCenter Version 5.1 Installation Guide at www.dell.com/support.
10 Contacting Dell EMC Dell EMC 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 EMC for sales, technical support, or customer service issues, see www.dell.com/contactdell. If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or the product catalog.
