EMC Unified Infrastructure Manager/ Provisioning Version 4.1 Patch 02 P/ N 302-001-250 Rev 01 July 2014 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.emc.com
Table of Contents Revision history... 3 Overview... 4 Product description... 4 EMC Unified Infrastructure Manager Plug-in for VMware vcenter Orchestrator... 5 Environment and system requirements... 6 End of service dates and extended support... 6 Known problems and limitations... 7 Fixed problems... 8 Documentation...11 Installing UIM/P 4.1 P 02...11 Upgrading the UIM/P appliance to 4.1 P 02...11 Verifying the installation...12 Uninstalling UIM/P Version 4.1 P 02...13 Verifying the uninstall...13 Troubleshooting and getting help...14 2
Revision history Table 1 lists the revision history of this document. Table 1 Revision history Date Rev Description of change July 2014 01 GA version of document. 3
Overview These release notes contain supplemental information about Manager/ Provisioning 4.1 Patch 02 (UIM/ P 4.1 P 02). Product description Manager/ Provisioning (UIM/ P) provides the foundation for Infrastructure as a Service (IaaS) on Converged Hardware Systems. UIM/ P allows you to: Discover infrastructure assets to create UIM/ P resources. Build UIM/ P resources into Converged Hard ware Systems. Manage Converged Hardware System device configuration. Manage the infrastructure service lifecycle. Monitor the status of Converged Hardware Systems and man aged services, using Dashboard views that summarize resource utilization. 4
EMC Unified Infrastructure Manager Plug-in for VMware vcenter Orchestrator The Manager Plug-in for VMware vcenter Orchestrator 1.1.0.1 is compatible with UIM/ P 4.1 P 02. Note: See the Manager Plug-in for VMware vcenter Orchestrator version 1.1 Installation and Configuration Guide document for more information. 5
Environment and system requirements The Manager/ Provisioning Support Matrix provides information on supported environments and system requirements. End of service dates and extended support EMC has a standard software support duration policy which specifies that a major version will reach End of Service Life (EOSL) a minimum of 36 months following the General Availability (GA). EOSL may be followed by an Extended Support period during which customers may elect to pay an additional fee to extend their support coverage rather than migrate to a current software version. Once a software product reaches EOSL, EMC Technical Support is no longer available under base support/maintenance agreements. Customers interested in uninterrupted support must upgrade to a current release or contract for Extended Support (ES). EMC Online Support contains a list of documents that provide end-of-service and extended support information for EMC software and hardware products. To access these documents on EMC Online Support, do the following: 1. Go to https://support.emc.com/products Type the product name in the Find a Prod uct field and click the arrow button. The Service Life information, if available for a given product, is displayed on the left side of the associated product page, and states when the product was Generally Available (GA), when it will be out of Service, and if it has Extended Service coverage. 2. Click the Release and End of Life Dates link available on the Service Life information section to view existing Service Life information d ocumen ts. The EMC Software Release and End of Service Life Notifications d ocument provides EOSL dates for EMC software prod ucts. Note: This policy is in effect for select releases and will be phased in as new versions are made available. In cases where a software release is not eligible for Extended Support, the previous policy, which specifies product support and maintenance under Continuous Coverage Prod uct Maintenance (CCPM), terms still apply. For information on how to use EMC Online Support, click the Online Support FAQ link available at https://support.emc.com/. 6
Known problems and limitations Refer to the list of known problems and limitations in the Manager Release Notes. In addition, at the tim e of release, UIM/ P 4.1 Patch 02 has the known problems and limitations listed in Table 2. When applicable, a workaround for the issue is documented. Table 2 Known problems and limitations CQ Issue/Diagnosis Resolution/Workaround 616121 After successfully activating a vcenter service, an error is displayed if the service is synchronized too soon after activation. 616129 The version numbers for the EMC Unified Infrastructure Manager Plug-in for VMware vcenter Orchestrator workflown varies between 0.2.0, 1.0.0, and 1.0.1. 616300 The VMware Studio Virtual Appliance Management Infrastructure (VAMI) console does not upgrade properly when upgrad ing from UIM/ P 3.2.x or 4.0.x to UIM/ P 4.1.0, resulting in an No management services are configured error when launching the VAMI console after the UIM/ P upgrade. Workaround: Wait a short period of time after activation and then attempt to synchronize the service again. Workaround: Ignore the varying Plug-in version numbers. Workaround: Follow the steps found in Upgrading the UIM/ P appliance to 4.1 P 02. 7
Fixed problems Table 3 details the problems and limitations that have been fixed in this release. Table 3 Known problems and limitations CQ Issue Fix description Version fixed 614382 After enabling auto compliance, provisioning the service successfully, and deleting the VNIC from the UCS, no service compliance alerts are displayed. 615677 When using UIM/ P SAU to unmanage a shared storage service, a 404 error may occur. This error does not disrupt any UIM core functionality. 615617 Upon successful release of one or more blades, the UIM/ P Console may display an incorrect service alert that indicates the wrong expected state for the associated service profile. 615639 After a successful selective decommission of a d ata volume configured as part of a service, upon executing service compliance, the UIM/ P Console may display an incorrect service alert. 615537 For shared storage services, concurrent synchronization fails for the attached standard services. 615790 Errors for VPLEX services when a VPLEX fails to claim the storage volume are not properly handled. 615795 Services become inoperable when multiple planned shared storage services use the same stand ard service(s). 615859 Reconciling a VSAN deleted from a SAN switch causes a vblock refresh and provisioning failure. The service compliance alerts are now working properly. The error is no longer incorrectly displayed. The service alert is no longer incorrectly displayed. The service alert is no longer incorrectly displayed. Concurrent synchronization no longer incorrectly fails for shared storage services. The error handling for VPLEX services has been improved to properly handle failed storage volume claims. Services no longer become inoperable for this scenario. Reconciling a VSAN deleted from a SAN switch no longer causes these failures. 8
CQ Issue Fix description Version fixed 615913 Over a long period of time, pull commands sent to the device server begin to build up and time out, resulting in exceptions recorded in the daemon.log file. A connection issue was fixed with the device server that was resulting in the exception errors. 615999 Detaching a standard service from a VPLEX service, causes incorrect compliance alerts and results in the workflow for the VPLEX service status to be stuck in the In Progress state. 616039 FAST policies that are manually added to LUNs provisioned through UIM/ P cause elastic provisioning of new LUNs to fail. 616048 After an SAU storage refresh, a MemLock Thread blocking on lock id error is displayed causing the UIM user interface to freeze. 616050/ 616069 Issues logging into UIM/ P when DNS and Search Domain entries are not present in the UIM/ P appliance. 616113 When UIM/ P is deployed without a DNS and search domain, the hostname is missing form the /etc/hosts file. 616309 Unclaiming VPLEX volumes causes unexpected prompts to be displayed. 653093 VSAN values appear empty after provisioning local VPLEX services from a vsphere version 5.1 web client. 616621 VCE Vision scan times out after 30 minutes but displays "Completed" after the scan completes. Detaching a standard service from a VPLEX service no longer causes incorrect compliance alerts and the workflow is correctly set to the Provisioned state. A valid ation error will now be shown related to the out of band FAST policy change. A storage refresh through the Service Adoption Utility (SAU) is needed. After refreshing SAU storage, the memory lock is now properly released. The login issue for this scenario has been resolved. The hostname is now correctly saved in the /etc/hosts file when UIM/ P is deployed without a DNS and search domain. Unexpected prompts are no longer displayed when unclaiming VPLEX volumes. VSAN values no longer appear empty when using vsphere 5.1. A property visionos.run.scan.timeout.minutes has been added to the slmconfig.groovy file. The default value for the time out is 30 minutes. Follow the steps below to increase the time out limit. 4.1.0.2 9
CQ Issue Fix description Version fixed 1) SSH to the UIM/ P server. 2) Edit file / opt/ ionixuim/ slm/ config/ slmconfig.groovy 3) Edit the visionos.run.scan.timeout.minutes property. For example, to set the timeout to 50 mins, edit to visionos.run.scan.timeout.minutes=50 4) Save and exit the file. 616762 OpenSSL Heartbleed Vulnerabilities 616923/ 616951 Ethernet switches that have a VLAN list longer than 256 characters caused service provisioning to fail. 616917/ 616942 Provisioning of Vplex is failing when multiple standard services with the same name are attached to a VPLEX service. 616974 Shared Storage Service stuck in Workflow in Progress when operations are in progress on multiple attached standard services. 5) Restart the slm server. Use command 'service uim-slm-tomcat restart' without the quotes. OpenSSL was upd ated to a newer version to address the vulnerabilities. UIM now allows longer VLAN lists from Ethernet switches. UIM now does not allow multiple services to be created with the same name. When selectively detaching a standard service from a Shared Storage Service, all attached services will be locked (Workflow in progress) so that no operations are allowed on any of the attached services. 4.1.0.2 4.1.0.2 4.1.0.2 4.1.0.2 10
Documentation The most current d ocumentation is available on the EMC Online Support website: https://support.emc.com/ Installing UIM/ P 4.1 P 02 The patch media is provided in two forms: Install media to install a full UIM/ P appliance with 4.1 P 02 preinstalled. Refer to the Manager/ Provisioning Software Installation and Configuration Guide for detailed instructions. While installing the appliance, p rovide the URL for the 4.1 P 02 OVF file. Update media to upgrade a UIM/ P appliance to 4.1 P 02. See Upgrading the UIM/ P appliance to 4.1 P 02 for instructions. Upgrading the UIM/P appliance to 4.1 P 02 Upgrades to Version 4.1 P 02 can be performed directly on appliances running UIM/ P Version 3.2.x and higher. This procedure must be completed for each UIM/ P appliance. Note: All discovered VMAX storage array devices (prior to an upgrade) will be automatically rediscovered following an upgrade from UIM/ P 3.2.x. Be aware that communication with the storage array devices will occur during this process. Upgrading from UIM/ P version 4.0.x and higher, will not cause automatic rediscovery of the VMAX storage array devices. 1. Take a snapshot of the UIM/ P appliance, using vsphere Client: a. Open vsphere Client, and connect to the vcenter Server managing your appliance. b. Right-click the UIM/ P appliance, and select Snapshot > Take Snapshot. Note: A snapshot of the UIM/ P appliance is important in order to prevent loss of data and allow proper rollback if an error occurs during the upgrade. 2. Download the UIMP-4.1.0.2.xxx-Update-Media.iso file to the server where you are running vsphere Client. 3. Use vsphere Client to mount the UIMP-4.1.0.2.xxx-Update-Media.iso file on your UIM/ P 4.1.x appliance. 4. If you are upgrading from 3.2.x or 4.0.x, VMware Stud io Virtual Appliance Management Infrastructure (VAMI) must be updated to version 2.5. To update VMware Studio VAMI: a. On the UIM/ P appliance, change directories using the cd /opt/adg/adg_vami25 command. b. Update VMware Studio VAMI using the run./installvami25package.sh command. 5. In a supported browser, type the following URL into the address bar: https://<hostname>:5480, where <hostname> is the fully qualified hostname of your UIM/ P 4.1.x appliance. If you are upgrading from 4.1.0.0 and are unable to reach the login prompt, VMware Studio Virtual Appliance Management Infrastructure (VAMI) must be upd ated to version 2.5. To update VMware Studio VAMI: a. Download the InstallVami25PackageALL.zip file from https://support.emc.com/ b. Unzip the InstallVami25PackageALL.zip file on the affected virtual machine. c. Take a backup snapshot of the affected virtual machine. d. Update VMware Studio VAMI using the run./installvami25packageall.sh command. 6. Log in as the root user. 7. Click the Update tab. 8. Click the Check Updates button, to find upd ates on the mounted update media. 11
9. Click the Install Updates button. Installation can take up to 30 minutes to complete. You do not need to reboot the appliance or restart any services. Note: If an update failure occurs, a message is recorded in the / opt/ ionix-uim/ logs/ applianceupdate.log file. If the update fails because step #4 was not followed from th e 3.2.x and 4.0.x release, please revert to the snapshot taken in step #1 and follow the steps again. Note: A reboot may be required after updating the UIM/ P appliance. To reboot, click the System tab at the top of the UIM/ P appliance management web page, then click Actions, and then Reboot. The reboot may take 10 minutes to complete. 10. Log out of the console by selecting Logout user root. Note: To ensure your browser reload s any upd ated flexui files, restart the browser before accessing the UIM/ P console. Verifying the installation 1. In a supported browser, type the following URL into the address bar: https://<hostname>, where <hostname> is the fully qualified hostname of your UIM/ P appliance. 2. Log into the UIM/ P console. 3. Click the Help option on the UIM/ P menu bar. 4. Select the About option to open the About Unified Infrastructure Manager/ Provisioning wind ow. 5. Verify the version of this release is 4.1.0.2.xxx. 12
Uninstalling UIM/ P Version 4.1 P 02 To uninstall the patch, revert to the vsphere snapshot of the UIM/ P appliance: 1. Open vsphere Client, and connect to the vcenter Server managing your VMWare environment. 2. Right-click the UIM/ P appliance, and select Snapshot > Revert to Current Snapshot. Verifying the uninstall 1. Click the Help option on the UIM/ P menu bar. 2. Select the About option to open the About Unified Infrastructure Manager/ Provisioning wind ow. 3. Verify the UIM/ P version appears as it did before the patch was applied. 13
Troubleshooting and getting help EMC support, product, and licensing information can be obtained, as follows: Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Online Support website (registration required) at: https://support.emc.com/ Technical support For technical support, go to EMC Customer Service on the EMC Online Support site. To open a service request through EMC Online Support, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account. Copyright 2010 2014 EMC Corporation. All rights reserved. Published July, 2014 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. 14