HPE 3PAR StoreServ File Controller WSS2016 v3 Release Notes a

Transcription

1 HPE 3PAR StoreServ File Controller WSS2016 v3 Release Notes a Part Number: C8S A Published: December 2016 Edition: 3

2 Contents Description...4 Product models...4 Operating systems...4 Languages...4 Enhancements...4 Security updates...4 Windows updates and hotfixes...5 Service Pack for ProLiant components... 5 Firmware updates...6 Workarounds... 8 Initial Configuration Tasks...8 Network Configuration Tool... 9 HPE System Dashboard...11 Services are not installed...11 Services are not running...12 Whitepaper link...12 System installation and recovery...12 Installation instructions Effective date...13 Documentation feedback Contents

3 2016 Hewlett Packard Enterprise Development LP Microsoft and Windows are trademarks of the Microsoft group of companies. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside HPE.com.

4 Description This release notes describe the release of version a for HPE 3PAR StoreServ File Controller v3 running Windows Storage Server 2016 Standard Edition. Product models HPE 3PAR StoreServ File Controller product model lists the 3PAR StoreServ FIle Controller v3 product model and its supported hardware platform. Table 1: HPE 3PAR StoreServ File Controller product model Product SKU Product model Hardware platform Q0F54A P9M57A HPE 3PAR StoreServ File Controller WSS2016 v3 Single Node HPE 3PAR StoreServ File Controller WSS2016 v3 Single Node Upgrade HPE Apollo r SFF CTO Chassis with HPE ProLiant XL190r Gen9 HPE Apollo r SFF CTO Chassis with HPE ProLiant XL190r Gen9 Operating systems Windows Storage Server 2016 Standard Edition. Languages English French Italian German Japanese Simplified Chinese Spanish Russian Enhancements HPE 3PAR File controller v3 support Windows Storage Server 2016 standard edition on the same hardware configuration of StoreEasy 3PAR File controller v3 with the exception of upgraded processor and memory. Default logon password changed to HPEStorage!. Security updates This release includes Microsoft Windows updates and security patches available on Windows update until 21 October

5 Windows updates and hotfixes Microsoft KB article number Microsoft KB article number Microsoft KB article number Microsoft KB article number KB KB KB KB Service Pack for ProLiant components The Service Pack for ProLiant (SPP) bundle provided with this release is SPP SPP supplement build components lists the Microsoft Windows Server 2016 supplement for SPP components that are post installed: Table 2: SPP supplement build components Supplement SPP supplement build components Version cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe HPE ProLiant Gen9 Chipset Identifier for Windows PFA Server Registry Update for Windows Server 2016 Headless Server Registry Update for Windows Server 2016 Integrated Management Log Viewer for Windows Server x64 Editions HPE Insight Management WBEM Providers for Windows Server x64 Editions HPE ProLiant Agentless Management Service for Windows X64 ilo 3/4 Channel Interface Driver for Windows Server 2016 ilo 3/4 Management Controller Driver Package for Windows Server 2016 HP Lights-Out Online Configuration Utility for Windows 2008/2012/2016 x64 Editions HP ProLiant Smart Array SAS/SATA Event Notification Service for for 64-bit Windows Server Editions HPE Insight Management Agents for Windows Server x64 Editions HPE Intel E1R Driver for Windows Server 2016 HPE Broadcom 1Gb Driver for Windows Server x64 Editions HP Broadcom 1Gb Multifunction Drivers for Windows Server x64 Editions (E) Table Continued Windows updates and hotfixes 5

6 Supplement SPP supplement build components Version cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe cp exe HP ProLiant Integrated Lights-Out Management Interface Driver for Windows Server 2012 HPE Emulex 10/20 GbE iscsi Driver for Windows Server 2016 HPE Emulex 10/20 GbE Driver for Windows Server 2016 HP ProLiant Smart Array SAS/SATA Controller Driver for Windows Server 2012 x64 Edition HPE ProLiant Smart Array HPCISSS3 Controller Driver for 64-bit Microsoft Windows Server 2012/2016 Editions Dynamic Smart Array B140i Controller Driver for 64-bit Microsoft Windows Server 2012/2016 Editions HP Dynamic Smart Array B120i/B320i SATA RAID Controller Driver for 64-bit Microsoft Windows Server 2012/2016 Editions HP ProLiant Smart Array Embedded SATA RAID Controller Driver for Microsoft Windows Server 2012 and Microsoft Windows Server 2012 R2 HPE StoreEver Tape Drivers for Microsoft Windows HPE System Management Homepage for Windows x64 Insight Diagnostics Online Edition for Windows x64 Editions HPE Smart Storage Administrator (HPE SSA) for Windows 64-bit HPE Smart Storage Administrator (HPE SSA) CLI for Windows 64-bit Matrox G200eH Video Controller Driver for Windows Server Firmware updates This section lists the firmware updates related to the SPP components. 6 Firmware updates

7 Table 3: Firmware updates File name Description Version cp exe (Recommended) cp exe (Recommended) cp exe (Recommended) cp exe (Optional) cp exe (Optional) Online ROM Flash Component for Windows (x64) - Smart Array H240ar, H240nr, H240, H241, H244br, P240nr, P244br, P246br, P440ar, P440, P441, P542D, P741m, P840, P840ar, and P841 Online ROM Flash Component for Windows - HP Host Bus Adapters H220, H221, H222, H210i and H220i Online ROM Flash Component for Windows (x64) - Smart Array P220i, P222, P420i, P420, P421, P721m, and P822 HPE Intel Online Firmware Upgrade Utility for Windows Server x64 Editions HPE Broadcom NX1 Online Firmware Upgrade Utility for Windows Server x64 Editions Table 4: HPE Broadcom NX1 Online Firmware Upgrade Utility for Windows Server x64 Editions NIC HP Ethernet 1Gb 2-port 330i Adapter (18D2) HP Ethernet 1Gb 2-port 330i Adapter (22BD) HP Ethernet 1Gb 4-port 331i Adapter (22BE) HP Ethernet 1Gb 4-port 331FLR Adapter HP Ethernet 1Gb 4-port 331T Adapter HP Ethernet 1Gb 4-port 331i Adapter (3372) HP Ethernet 1Gb 4-port 331i-SPI Adapter HP Ethernet 1Gb 2-port 332i Adapter (2133) HP Ethernet 1Gb 2-port 332i Adapter (22E8) HP Ethernet 1Gb 2-port 332T Adapter Boot Code Version PXE Version NCSI Version UEFI Version CCM Version N/A N/A

8 Workarounds General A warning appears during Cluster validation. Workaround: Install Driver component for HPE Intel E1R Network Adapter. UAC popup seen at times on launching ArrayRegistration.exe. Accept the same to proceed with registration. HPSReports 9.8 execution crashes in NFS RPC info. Workaround: Run RPC locator services from services.msc and then run HPSReports again. In HPE Notification System, while editing the value for a parameter, comparison, or name in an existing rule, a new rule is created with the same data. The changes made to the existing rule are not saved. Workaround: Manually delete the older rule. If you are logged in to the storage system as a domain user and open the Event Notifier Configuration Wizard, the following error message is displayed: Unable to restart the Event Notification service. Check the Event Log for more detailed information about this error. Workaround: Log in to the system as a local administrator (not a domain user) and open the wizard. If you attempt to change the desktop background, it is blocked due to a group policy on the system. Workaround: To change the desktop background, you must change the group policy settings: 1. Log in to the system as a user in the local administrators group. 2. Open a PowerShell or Command window and enter the gpedit.msc command in the command line. 3. In the Local Group Policy editor, select User Configuration Administrative Templates Desktop, and click Desktop. 4. Double-click the Desktop Wallpaper setting. 5. Select Disabled and then apply the setting change. 6. Log off and log in for the changes to be effective. On a non English HPE 3PAR StoreServ File Controller v3 system, two shortcut buttons representing the online help are displayed on the taskbar. Workaround: None. Initial Configuration Tasks Create virtual disk for file server wizard is not visible on top of ICT at times, but the wizard launches. Workaround Minimize ICT, the wizard is opened behind ICT window. Default cluster ICT opens post installation for standalone system. Workaround Do not use the Initial Configuration Task started in background, the installation will launch the correct ICT. After clicking YES in cluster option in primary node, accept EULA on primary node, the remote node does not automatically proceed. Workaround Manually accept EULA on remote node. The Initial Configuration Task window displays the following message: To complete configuration of the first node, log off and then log on again using a domain user account with local administrative permissions. This message appears after joining an HPE 3PAR File Controller v3 system to a domain, and then logging on to the system again as the local administrator. This occurs when you deploy HPE 3PAR File Controller v3 Storage in a cluster configuration or on a standalone server. To resolve this issue, perform the following: 8 Workarounds

9 1. Add a domain user as a member of the local Administrators group on the HPE 3PAR File Controller v3 Storage system. 2. Log off and log on again as the domain user. The Initial Configuration Tasks window opens automatically. 3. Complete the configuration tasks. While deploying HPE 3PAR File Controller v3 Storage as a two node cluster, after selecting a language and accepting the EULA, you may see a message box with the error: Found more than one node. Cannot establish communication with the second node. The message box has two buttons; Retry and Cancel. This may occur if you have ordered the StoreEasy 3000 Storage systems with optional network adapters and have cabled ports on those adapters to your network infrastructure. As shown in the Quick Start Guide, there is one network cable that must run between the Port 4 adapters on each of the two nodes. Keep this network cable in place, as well as the network cable to the ilo port, but disconnect all other network cables on the system where you received the error message. Then click Retry. You may reconnect the cables later after the second node is discovered. The Create virtual disks link in the Storage Configuration section launches the Virtual Disk wizard. While creating a new virtual disk, if you select Create a volume when this wizard closes, the Create Volume wizard is auto-launched after the virtual disk is created. On a non-english HPE 3PAR File Controller v3 Storage standalone system, the ICT may not display the Set local administrator password link. Change the password using one of the following methods: Connect to the server using ilo. From the ilo menu, select Keyboard CTRL-ALT-DEL. The option to change the password is displayed. Log in to the server. Navigate to Control Panel User Accounts. Select Change account type and then select Administrator. Select Change the password and enter the new password credentials. Click Change password. Network Configuration Tool If you select Do not configure network interface VLAN identifiers now after assigning VLAN IDs to Teams or adapters, the assigned IDs are not removed. Workaround: For all Teams and adapters, you must navigate through each VLAN page and select Do not add a VLAN ID to this Team. If you assign the same network subnet to more than one network interface on the same server, it might have unexpected results. Workaround: You must not configure more than one network interface with the same network subnet on a server. On clustered systems, if you click the remote node in the left navigation pane when the discovery is in progress, the tree view appears empty when the discovery completes. Workaround:To view the remote node, click the local node and then click the remote node. When assigning a range of VLAN IDs to a Team, if the incremental value is blank, NCT proceeds to the next page without any prompts, even if: There are invalid inputs. No VLAN ID is assigned to that particular Team. Workaround: Ensure that you specify the incremental value whenever you assign a range of VLAN IDs to a Team. If you click Previous after entering the details in the Team Configuration page, the Network Interface Settings page is displayed. However, when you navigate back to the Team Configuration page, 0 (zero) is displayed in Number of Teams. Network Configuration Tool 9

10 Workaround: Whenever you navigate from the Team Configuration page to the Network Interface Settings page, and then navigate back to the Team Configuration page, enter the appropriate value in Number of Teams. A Device Setup Information pop-up box might open after a successful Team creation. Workaround: The installation is automatic and user intervention is not required. Do not click Cancel to cancel the installation. Allow the installation to complete. The Configure VLAN IDs Now option is not disabled if you do not select any interfaces. Workaround: Always select the interfaces when you assign a VLAN ID. You cannot assign 0 (zero) to a VLAN ID that is assigned to a Team or interface. Workaround: A VLAN ID with value 0 cannot be assigned to a Team or interface. Therefore, HPE recommends that you assign a non-zero positive value to the VLAN ID. Team creation is not reflected in the tree view for remote nodes. Team creation reflects only for local nodes. Workaround: There is no known workaround for this issue. Systems with similar hardware configurations are configured using the NCT and by importing an existing NCTConfig.xml file. However, while applying the settings, if a conflict occurs between the NIC adapter names of the system and the NCTConfig.xml file, the following error message appears: Task has failed. Consider the following scenario: System1 configuration System2 configuration Ethernet (3.0.0) Ethernet1 (3.0.0) Ethernet1 (3.0.1) Ethernet (3.0.1) Ethernet2 (3.0.2) Ethernet2 (3.0.2) Ethernet4 (3.0.3) Ethernet3 (3.0.3) In this scenario, the NCTConfig.xml file is generated from System1 and needs to be imported to System2. A one-to-one mapping occurs between the NIC adapter names and the PCI Keys. During import, when the system tries to rename the NIC name Ethernet1 (3.0.0) to Ethernet (3.0.0), an error occurs because System2 already has a NIC adapter with NIC name Ethernet1 (3.0.1). Two NIC adapters on a system cannot have similar names. Therefore, importing the NCTConfig.xml file fails. Workaround: Perform the following steps: 1. Run the Get-NetAdapterHardwareInfo PowerShell command on System2. The PCI Key is read as Bus:Device:Function from the output. 2. Be sure that the listed NIC names do not match with those listed in the NCTConfig.xml file. Name matching must be done on the basis of PCI Key. 3. Make appropriate changes to the System2 NIC names using NCT or Control Panel if you find conflicting names with the NIC names listed in the imported NCTConfig.xml file. This is to make sure that while importing the XML file, the NIC adapters from System2 and the NCTConfig.xml file do not have conflicting names and the file importing does not fail. 10

11 System1 configuration (NCTConfig.xml) Ethernet (3.0.0) System2 configuration Ethernet1 (3.0.0) should be renamed to Ethernet (3.0.0) Ethernet1 (3.0.1) Ethernet2 (3.0.2) Ethernet2 (3.0.2) Ethernet4 (3.0.3) Ethernet3 (3.0.3) 4. Import the NCTConfig.xml. TIP: Ethernet (3.0.1) should be renamed to Ethernet1 (3.0.1) You can also configure System2 using the Network Configuration Tool without using the configuration details available in the NCTConfig.xml file. For more information, see the Administrator Guide. HPE System Dashboard Hardware failures are not displayed in the Event Logs tab of the Health page. The Event Logs tab may not always display the hardware failures. This happens because the event log has data related to all the events. The Event Logs tab displays only a fixed number of events from the list of known events. Therefore, to view any hardware failures, see the Alerts tab in the Health page. Changes made to the storage hardware is not reflected in dashboard Storage Drives page. Any change made to the storage hardware is reflected in the Storage Drives page only when the SMP cache is refreshed. The default interval for the next discovery set in configuration file is six hours. However, you can view the updates in the Storage Drives by executing the Update-StorageProviderCache - DiscoveryLevel Full PassThru command in an elevated command prompt with administrator privileges. If number of shares count is very high (for example, more than 250 or so), then it might take a long time to load and display the data in the Storage Shares tab. There is no known workaround for this. In a clustered setup with more than two nodes, if the primary node fails, the HPE System Dashboard displays information only for the current node. The 1/1 Systems in the menu bar indicates the same. Services are not installed If data is not displayed in System Dashboard or if one of the following error messages are displayed: The service HPE Network Discovery Service is currently not installed. Please refer to the troubleshooting section of the release note for more details. The service HPE Storage Discovery Service is currently not installed. Please refer to the troubleshooting section of the release note for more details. The service HPE System Health Discovery Service is currently not installed. Please refer to the troubleshooting section of the release note for more details. Click Start Control Panel Uninstall a program and make sure that the following components are installed: HPE StoreEasy Data Service HPE StoreEasy Dashboard HPE Management Web Services HPE System Dashboard 11

12 If any of these components are not installed, reinstall the System Dashboard using the installation file available at C:\nas\Components. Services are not running If one of the following error messages is displayed on System Dashboard, run the services.msc command and start the stopped services listed in the error message: The service HPE Network Discovery Service is currently paused or stopped. Please refer to the troubleshooting section of the release note for more details. The service HPE Storage Discovery Service is currently paused or stopped. Please refer to the troubleshooting section of the release note for more details. The service HPE System Health Discovery Service is currently paused or stopped. Please refer to the troubleshooting section of the release note for more details. Storage Management Provider service is not running on the system. Whitepaper link Whitepaper link does not open properly by default If the whitepaper link does not open properly by default, enable the Javascript settings for the page to open correctly. Open Internet Explorer. From the Tools menu, select Internet Options. Select Security tab, and click Custom Level button. NOTE: Ensure that the Internet Zone is selected. The Security Settigs - Internet Zone page opens. Select the Enable radio buttons for Active Scripting and Scripting of Java applets, and click OK. Click Apply and close the browser. System installation and recovery The Internet Printing Client features are not installed by default with the operating system. Workaround: Use Windows Server Manager to manually install these features: 1. Select Features and then click Add Features. 2. Select Internet Printing Client in the features list. 3. Click Next and complete the Add Features Wizard installation process. The time zone selected during the image process is not retained. The image process allows you to set the time zone; however, the time zone is always set to Pacific time when the operating system comes up for the first time. Workaround: Change the time zone after the system is fully imaged. Installation instructions Instructions for installing new systems are provided in the following documents: HPE 3PAR StoreServ File Controller WSS2016 v3 Quick Start Guide HPE 3PAR StoreServ File Controller WSS2016 v3 Administrator Guide These documents are available at 12 Services are not running

13 Effective date December 2016 Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page. Effective date 13