Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Document Version Release Date Details 2 04/26/2018 Included the December Edition information in the Title and Descripton sections. 1 04/23/2018 Original Document Release. This document provides the details on changes to the SW-FW versions mentioned in the HPE ConvergedSystem 700 Firmware and Software Compatibility Matrix Update Guide for March 2017 to November 2017 and the HPE ConvergedSystem 700 Firmware and Software Compatibility Matrix Update Guide for June 2016 to November 2017. Both of these guides refers to the FWSW component versions and the filenames from the November 2017 FWSW compatibility matrix published in December 2017. This information is developed to highlight the differences in the SWFW versions and files names between the December 2017 edition and March 2018 edition of the November 2017 FWSW compatibility matrix and the enable update to the November 2017 FWSW compatibility matrix March 2018 edition. Below are the possible scenarios: a) CS700 VMware solution at or updated to the November 2017 FWSW matrix December 2017 Edition. b) CS700 VMware solution yet to update to the November 2017 FWSW matrix March 2018 edition (from March 2017 or June 2016 FWSW matrix and not updated to November 2017 FWSW matrix Dec 2017 edition).
Any of the following HPE ConvergedSystem 700 and HPE ConvergedSystem 700x are affected: HPE ConvergedSystem 700 1.0/1.1 Starter (751865-B21) HPE Converged System 700 1.0/1.1 Virtual Expansion (751866-B21) HPE ConvergedSystem 700x 1.0 for VMware [formerly HPE VirtualSystem VS3 2.2] (721223-B21) HPE ConvergedSystem 700x 1.1 for VMware (J0H72A) HPE ConvergedSystem 700 2.0 for VMware (K9T75A)
The update guides list the software and firmware versions and the respective files in the section called "Firmware and software versions for the CS700 November 2017 update". There are changes in these versions with November 2017 FWSW matrix March 2018 edition. Refer to Table 1 for the respective changes. Table 2, refers to the replaced file names to be substituted in the upgrade steps of individual components when referring to the March 2017 to November 2017 update guide. Table 3, refers to the replaced file names to be substituted in the upgrade steps of individual components when referring to the June 2016 to November 2017 update guide. Table 1 - Changes in the section "Firmware and software versions for the CS700 November 2017 update" of the update guides. Component Original version Replacement New version HPE OneView 3.10.07 HPE_OneView_3.10.07_Update_Z7550-96417.bin 3.10.08 HPE_OneView_3.10.08_Update_Z7550-96481.bin Custom Service Pack for ProLiant bundle Virtual Connect - 4.50 ROM Version DL360p Gen 8 - P71-2015.07.01 ROM Version BL460c Gen 8 - I31-2015.06.01 ROM Version DL360p Gen 9 - I36-2.52_10-25-2017 ROM Version BL460c Gen 9 - P89-2.52_10-25-2017 4.62 P71-2018.01.22 I31-2018.01.22 I36-2.56_01-22-2018 P89-2.56_01-22-2018 (These versions should be used to create a Custom SPP and use it for the update) HPE B-series SAN Network Advisor 14.2.1 na1421_hp_windows.zip 14.2.2 na1422_hp_windows.zip VMWare vCenter Server 5.5 VMware-VIMSetup-all-5.5.0-6520252- 20170901update03.iso VMware-VIMSetup-all-5.5.0-7957701-20170901-update03.iso VMWare vCenter Server 6.0 ( Windows) VMware-VIMSetup-all-6.0.0-7040641.iso VMware-VIMSetup-all-6.0.0-7977899.iso VMWare vCenter Server 6.0 ( Appliance) VMware-vCenter-Server-Appliance-6.0.0.30300-7037817-patch-FP.iso VMware-vCenter-Server-Appliance-6.0.0.30500-7977753-patch-FP.iso VMWare vCenter Server 6.5 (Windows) VMware-VIM-all-6.5.0-6816762.iso VMware-VIMall-6.5.0-8024368.iso VMWare vCenter Server 6.5 (Appliance) VMware-vCenter-Server-Appliance-6.5.0.12000-7119157-patch-FP.iso VMware-vCenter-Server-Appliance-6.5.0.15000-8024368-patch-FP.iso VMWare vSphere 6.0 NA ESXi600-201803001.zip VMWare vSphere 6.5 ESXi650-201712001.zip ESXi650-201803001.zip HPE OneView for VMware vRealize Operations HPEOneViewAdapter-2.1.1.6.pak HPEOneViewAdapter-2.1.3.1_signed.pak Windows VM patches ( Install this patch in the Windows VMs after the VMware tools update ) windows8.1-kb4056898-v2-x64_754f420c1d505f4666437d06ac97175109631bf2.exe Follow the section "Apply Microsoft security patch to Windows VMs" section in this doc HPE SN B-Series Fibre Channel Switch (SN6000B) V8.1.1a (v8.1.1a.zip) V8.1.2a (v8.1.2a.zip) HPE SN B-Series Fibre Channel Switch (SN3000B) V8.1.1a (v8.1.1a.zip) V8.1.2a (v8.1.2a.zip) HPE StoreFabric 8/24 Bundled FC Switch V7.4.2a (v7.4.2a.zip) V7.4.2b (v7.4.2b.zip) HPE 3PAR OS 3.2.2(MU4)+P50+P51+P56+P57 3PAR_Inform_OS_3.2.2_MU4_CLI_SNMP_SW_QR482-110192.iso 3.2.2(MU6)+P96+P99 3PAR_INFORMOS_3.2.2_MU6_CLI_SNMP_QR482-11287.iso 3PAR_INFORM_OS_RELEASE_3.2.2_MU6_P96_QR482-11300.iso OS-3.2.2.709-P99.iso HPE 3PAR Physical Service Processor 3PAR_Physical_SP_4.4_MU3_SW_QR516-11042.iso 3PAR_Physical_SP_4.4_MU6_SW_QR516-11062.iso HPE 3PAR Virtual Service Processor 3PAR_Virt_SP_4.4_MU3_VMware_ESX_SW_QR482-11178.iso 3PAR_Virt_SP_4.4_MU6_ESX_QR482-11317.iso Table 2 - HPE ConvergedSystem 700 Firmware and Software Compatibility Matrix Update Guide for March 2017 to November 2017 substitution table. Reference page in doc Section heading and step Original version Replacement New version P20 Updating HPE OneView step 3a 3.10.07.bin 3.10.08.bin P20 Custom Service Pack for ProLiant bundle Virtual Connect - 4.50 ROM Version DL360p Gen 8 - P71-2015.07.01 ROM Version BL460c Gen 8 - I31-2015.06.01 ROM Version DL360p Gen 9 - I36-2.52_10-25-2017 ROM Version BL460c Gen 9 - P89-2.52_10-25-2017 4.62 P71-2018.01.22 I31-2018.01.22 I36-2.56_01-22-2018 P89-2.56_01-22-2018 (These versions should be used to create a Custom SPP and use it for the update) P23 Disabling Track Fabric Change Step 2, 6, 10 and 13 HP B-series SAN Network Advisor 14.2.1 HP B-series SAN Network Advisor 14.2.2 P26 VMWare vCenter update scenario 1 Step 2 VMware-vCenter-Server-Appliance-6.0.0.30300-7037817-patch-FP.iso VMware-vCenter-Server- Appliance-6.0.0.30500-79 77753-patch-FP.iso P32 Uploading and mounting the VMware VIMSetup ISO update file step 3b VMware-VIMSetup-all-6.0.0-7040641.iso VMware-VIMSetupall- 6.0.0-7977899.iso P34 Updating HPE OneView for VMware vRealize Operations Step 5 HPEOneViewAdapter-2.1.1.6.pak HPEOneViewAdapter-2.1.3.1_signed.pak P46 Applying the ESXi patch Step 2 and Step 3 ESXi600-201611001.zip ESXi-6.0.0-20161104001-standard ESXi600-201803001.zip ESXi-6.0.0-20180304001-standard (After applying this patch, follow the section below to change the hardware version of the mentioned VMs.) P47 Updating VMware tools After VMware tools update, apply the windows patches on windows VMs windows8.1-kb4056898-v2-x64_754f420c1d505f4666437d06ac97175109631bf2.exe Follow the section "Apply Microsoft security patch to Windows VMs" section in this doc P49 Uploading Firmware using FTP Method Step 3, Step 8a, 8b and 8c V8.1.1a V8.1.2a P49 Uploading Firmware using USB Method Step 8a, 8b and 8c V8.1.1a V8.1.2a P51 Updating 3PAR Step 10 3PAR_Inform_OS_3.2.2_MU4_CLI_SNMP_SW_QR482-110192.iso 3PAR_INFORMOS_3.2.2_MU6_CLI_SNMP_QR482-11287.iso P54 Updating the Service Processor Step 6 3PAR_Physical_SP_4.4_MU3_SW_QR516-11042.iso 3PAR_Physical_SP_4.4_MU6_SW_QR516-11062.iso P54 Updating the StoreServ Array Step 6 3PAR_OS_3.2.2_EMU4_SW_QR482-11191.iso 3PAR_INFORM_OS_RELEASE_3.2.2_MU6_SW_QR482-11286.iso Table 3 - HPE ConvergedSystem 700 Firmware and Software Compatibility Matrix Update Guide for June 2016 to November 2017 substitution table. Reference page in doc Section heading and step Original version Replacement New version P8 June 2016 to November 2017 update overview 3.10.07 3.10.08 Update OneView from 3.00.07 to 3.10.08 P49 Updating Service Pack for ProLiant Virtual Connect - 4.50 ROM Version DL360p Gen 8 - P71-2015.07.01 ROM Version BL460c Gen 8 - I31-2015.06.01 ROM Version DL360p Gen 9 - I36-2.52_10-25-2017 ROM Version BL460c Gen 9 - P89-2.52_10-25-2017 4.62 P71-2018.01.22 I31-2018.01.22 I36-2.56_01-22-2018 P89-2.56_01-22-2018 (These versions should be used to create a Custom SPP and use it for the update. Refer the section below to create a custom SPP) P46 Disabling Track Fabric Change Step 2, 6, 10 and 13 HP B-series SAN Network Advisor 14.2.1 HP B-series SAN Network Advisor 14.2.2 P31 VMWare vCenter update scenario 1 Step 2 VMware-vCenter-Server-Appliance-6.0.0.30300-7037817-patch-FP.iso VMware-vCenter-Server- Appliance-6.0.0.30500-79 77753-patch-FP.iso P38 Uploading and mounting the VMware VIMSetup ISO update file step 3b VMware-VIMSetup-all-6.0.0-7040641.iso VMware-VIMSetupall- 6.0.0-7977899.iso P54 Uploading the VMware update manager ISO file Step 3b VMware-VIMSetup-all-6.0.0-7040641.iso VMware-VIMSetupall- 6.0.0-7977899.iso P61 Updating HPE OneView for VMware vRealize Operations Step 5 HPEOneViewAdapter-2.1.0.26.pak HPEOneViewAdapter-2.1.3.1_signed.pak P60 Applying the ESXi patch Step 2 and Step 3 ESXi600-201611001.zip ESXi-6.0.0-20161104001-standard ESXi600-201803001.zip ESXi-6.0.0-20180304001-standard (After applying this patch, follow the section below to change the hardware version of the mentioned VMs.) P47 Updating VMware tools After VMware tools update, apply the windows patches on windows VMs windows8.1-kb4056898-v2-x64_754f420c1d505f4666437d06ac97175109631bf2.exe Follow the section "Apply Microsoft security patch to Windows VMs" section in this doc P73 Uploading Firmware using FTP Method Step 3 V8.1.1a V8.1.2a P74 Uploading Firmware using USB Method Step 8a, 8b and 8c V8.1.1a V8.1.2a P76 Updating 3PAR Step 10 3PAR_Inform_OS_3.2.2_MU4_CLI_SNMP_SW_QR482-110192.iso 3PAR_INFORMOS_3.2.2_MU6_CLI_SNMP_QR482-11287.iso P78 Updating the Service Processor Step 6 3PAR_Physical_SP_4.4_MU3_SW_QR516-11042.iso 3PAR_Physical_SP_4.4_MU6_SW_QR516-11062.iso P79 Updating the StoreServ Array Step 6 3PAR_OS_3.2.2_EMU4_SW_QR482-11191.iso 3PAR_INFORM_OS_RELEASE_3.2.2_MU6_SW_QR482-11286.iso P80 Updating the StoreServ Array Step 17 3PAR_Inform_OS_Release_3.2.2_MU4_P50_QR482-11190.iso 3PAR_Inform_OS_Release_3.2.2_MU4_P51_QR482-11197.iso 3PAR_Inform_OS_Release_3.2.2_MU4_P56_QR482-11209.iso 3PAR_INFORM_OS_RELEASE_3.2.2_MU6_P96_QR482-11300.iso Apply the Microsoft Security Patch to Windows 2012 VMs 1. Open a remote desktop connection to CID Tab 13_SolMgt -> smgmt01 Solution Management IP Address. 2. Log in using the CID Tab 13_SolMgt -> smgmt01 Admin Username and Password. 3. Open the Registry Editor and set the following registry key: Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" Value="cadca5fe-87d3-4b96-b7fb-a231484277cc" Type="REG_DWORD" Data="0x00000000" 4. Open the command prompt and run the following three registry keys which will enable the fixes on the Windows VM. 5. Download the Microsoft patch file "windows8.1-kb4056898-v2 x64_754f420c1d505f4666437d06ac97175109631bf2.exe" from the link https://www.catalog.update.microsoft.com/Search.aspx?q=KB4056898 to a local folder. 6. Double click the above exe file and install it. 7. Perform the same activity for other windows VMs (tsvm01 and tsvm02) in the solution. Change the Virtual Machine Hardware Version only for Windows 2012 VMs 1. Open the vSphere Web Client to https://<CI Tab 12_vSphereSettings -> vCenter Server FQDN>/vsphere-client. 2. Log in using the CID Tab 12_vSphereSettings -> vCenter Single Sign-On Admin Username and Password. 3. Using the Virtual Machine H/W version table below, click the VMs and Templates to right-click each VM and select Edit Settings. 4. Click on Upgrade and check "Schedule VM Compatibility Upgrade". 5. Select the Compatible with "ESXi 6.0 and later" option. 6. In the Guest OS shutdown, select the option "only upgrade after normal guest OS shutdown" 7. Click OK 8. Close all the application and Power off VM and then power on (Cold reboot is required). 9. After the VM reboot, make sure that in the VM summary tab, the VM version should be displayed as 11. 10. Perform the same activity for other windows VMs (tsvm01 and tsvm02) in the solution. Virtual Machine H/W Version Change to smgmt01 8 11 tsvm01 8 11 tsvm02 8 11 Run the PowerShell module to validate that the protections are enabled 1. Download the Speculation control Zip file from the link: https://gallery.technet.microsoft.com/scriptcenter/Speculation-Control-e36f0050 2. Extract the contents to a local folder, for example C:\ADV180002. 3. Run the PowerShell module to validate that the protections are enabled. Start PowerShell, then (using the example above), copy and run the following commands: 4. The output of this PowerShell script will resemble the following: Enabled that the protections appear in the output as "True." Note: This security patch and hardware version change is applicable for MSFT Windows 2012 VMs deployed on compute server also. Creating the Custom SPP ISO using Smart Update Manager The files in the Custom SPP should match the files listed in the HPE ConvergedSystem 700 Firmware and Software Matrix - November 2017. To access the matrix, refer to the Hewlett Packard Enterprise website: http://www.hpe.com/info/cs700-docs Prerequisites Access to Windows-based computer(Local Desktop or Laptop) with Mozilla Firefox 34 or Google Chrome (39 and above). Downloaded copy of the appropriate base SPP ISO file for the firmware and software matrix you are updating to. To download the SPP from the Hewlett Packard Enterprise website, refer to: http://www.hpe.com/info/spp Procedure 1. Create the following folders on the local computer: I. C:\BaseSPP - To store the contents of BaseSPP ISO II. C:\Addons - To store the files of additional components. III. C:\CustomSPP - To store the Custom SPP. 2. On the local machine, with access to the downloaded ISO file, mount the ISO as a drive and copy the files from the ISO to a folder C:\BaseSPP 3. Download all the corresponding new software, firmware and driver component files to the folder C\Addons The following types of files should be included for each additional component. .rpm files for Linux .exe files for Windows .zip files for VMware 4. Open the folder C:\BaseSPP 5. To run the Smart Update Manager (SUM), double-click launch_sum.bat. A browser window with the SUM interface opens. 6. In the top left corner, click the Smart Update Manager 8.0.0. 7. Select Options > Baseline Library. The baseline takes approximately 30 minutes to load for the first time. Once the baseline is successfully loaded, "Baseline successfully added" is reported. 8. To add the additional packages, in the top left, select Add Baseline. 9. In the Add Baseline Options windows, Click Add Baseline. A pop-up window appears. Location type: Use the default location, "Browse SUM server path". Location Details: Browse to the root folder containing the updates, C:\Addons and click OK IMPORTANT: Select the root folder, Failure to select the root folder will result in the Custom SPP missing required components. When adding the component, select the directory path C:\Addons. Adding components to C:\Addons will ensure that they are packaged in to the Custom SPP ISO. To ensure that all files are correctly added to the baseline, copy any files outside of the root folder into the root folder, C:\Addons. 10. Click add. The additional packages are added to the baseline library. The process takes approximately 10 minutes to complete. Once the packages have been added successfully, "Baseline successfully added" is reported. 11. Repeat this process for any additional packages to be added. Once you have added all the necessary additional packages, verify that they were added correctly. 12. Click Close. 13. To create the custom SPP ISO, in the top right corner, click Actions > Create Custom. Create Custom Baseline screen pops up a. Description: Create a description with the following naming convention: SPP(date of base SPP)-CS700-(month and year). For Example: SPP2017101-CS700-Mar2018. b. Version: enter a one or two character version identifier. For example: 00, 01, 1A. c. Output Location: Select the folder C:\CustomSPP. This location is where the final SPP ISO and its contents will be contained. d. Check Make Bootable ISO File. e. Extracted Source ISO Location: Browse to the mounted drives root folder C:\BaseSPP f. Source Location: Leave as "current working directory". g. SUM Path: Leave the path C:\BaseSPP\packages 14. For Step 1 - Baseline Sources, select each baseline component to be added. 15. For Step 2 - Filters, do not check any of the boxes unless instructed to do so. 16. For Step 3 - Review, first click "Apply Filters" 17. Remove all the unnecessary components and verify that all the needed additional components are present. a. To determine which files are not required, search for the additional component by type will ensure you can see all versions of this component and what it affects. For example, for HPE iLO 4, search "Online ROM Flash Component for Linux - HPE Integrated Lights-Out 4" in the filters search bar. In this example, using a specific component name search for HPE iLO4 will help you avoid removing necessary updates for older versions. IMPORTANT: Only remove the older version of firmware for a specific model, generation and version. b. To add/remove components, search the file name and select or de-select the component as needed. 18. After removing all the unnecessary components, ensure that all required additional components are included by searching for each file name directly. 19. To create a custom SPP package, click "Create ISO and save Baseline". This process may take up to an hour. Do not refresh your browser window with SUM. Refreshing your browser will interrupt the process and may cause it to fail. 20. Once the process is complete, navigate to the folder C:\CustomSPP and view the contents. 21. To find the new SPP ISO, sort the files by type. 22. Rename the ISO using the same name as given in the Description field adding a timestamp (24-hour clock) to the end. - For example, SPP2017101-CS700-Mar2018-28Mar1530 23. Review that all required components are present. If a file is missing, you need to create a new custom SPP. Missing files cannot be added manually. IMPORTANT: The number of added-removed files is usually close to a 1 to 1 match, but generally, more components are removed than added. Though, it is not uncommon to have more added than removed. 24. In the top-right of the screen, click the User icon and logoff to exit SUM. 25. Ensure that the SUM Launcher script is closed and exit the command prompt. NOTE: One or more of the links above will take you outside the Hewlett Packard Enterprise web site. HPE does not control and is not responsible for information outside of the HPE web site. NOTE: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models. RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL: Proactive Updates Subscription Form. NAVIGATION TIP : For hints on navigating HPE.com to locate the latest drivers, patches, and other support software downloads for ProLiant servers and Options, refer to the Navigation Tips document . SEARCH TIP : For hints on locating similar documents on HPE.com, refer to the Search Tips Document .