HPE StoreVirtual OS v13.5 Release Notes

Transcription

1 HPE StoreVirtual OS v13.5 Release Notes Part Number: Published: May 2017 Edition: 2

2 Contents Release notes...4 Description... 4 Platforms supported for this release... 4 Update recommendation...4 Supersede information...4 Languages... 4 Firmware and software compatibility and interoperability... 5 Prerequisites... 5 Enhancements... 5 System requirements... 5 Fixes... 6 Issues and workarounds... 6 Support contacts Related information...20 Documentation feedback Contents

3 2016, 2017 Hewlett Packard Enterprise Development LP Notices The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. 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 the Hewlett Packard Enterprise website. Acknowledgments Microsoft and Windows are either registered trademarks or trademarks of the Microsoft group of companies.

4 Release notes Description These release notes describe StoreVirtual OS version 13.5, which contains the following software components: HPE StoreVirtual OS Software Version HPE StoreVirtual Management Console (SVMC) Version HPE StoreVirtual OS Command Line Interface (CLI) Version (on-system only) HPE StoreVirtual OS REST API Version 2.1 HPE StoreVirtual Storage Application Aware Snapshot Manager Version HPE StoreVirtual SNMP MIBs for StoreVirtual OS Version HPE StoreVirtual DSM for Microsoft Windows MPIO Version (installs Microsoft certified DSM driver Version ), with support for: Windows Server 2016 Windows Server 2012 R2 Windows Server 2012 These release notes are current as of the published date. Platforms supported for this release HPE StoreVirtual 3200 (array enclosure) HPE StoreVirtual 3000 (disk enclosure) Update recommendation Hewlett Packard Enterprise recommends that all customers running an earlier version of software update to Version As a best practice, Hewlett Packard Enterprise recommends upgrading software during times of non-peak activity to minimize any potential application impact. Supersede information Version 13.5 supersedes all previous versions on StoreVirtual 3200 Storage. Languages The StoreVirtual 3200 Management Console supports the following languages: English Simplified Chinese Japanese Korean Spanish NOTE: The on-system CLI and the storage system Configuration Interface are not localized. 4 Release notes

5 Firmware and software compatibility and interoperability View the complete StoreVirtual 3200 Storage compatibility and interoperability at HPE Single Point of Connectivity Knowledge (SPOCK) Storage: 1. Go to 2. Log in with your HPE Passport. 3. In the section Explore Storage Operability with SPOCK, click the link for Explore StoreVirtual 3200 Storage interoperability. 4. Select StoreVirtual Storage Compatibility Matrix. Prerequisites The following patches are prerequisites for upgrading to StoreVirtual OS version 13.5 or later. These patches are installed automatically through the Online Update feature. Patch This patch resolves an issue on iscsi storage systems updating from LeftHand OS version 13.0 to StoreVirtual OS version 13.5 or later. Patch This patch fixes a shutdown issue that led to the loss of crucial logs on storage systems running LeftHand OS version Patch This patch resolves an issue on iscsi storage systems updating from LeftHand OS version 13.1 to StoreVirtual OS version 13.5 or later. Patch This patch delivers updated software components that are prerequisites for updating from LeftHand OS version 13.0 or 13.1 to StoreVirtual OS version Enhancements Scale-out A second StoreVirtual 3200 system may be added to a management group. Multi-Site SAN The Multi-Site SAN feature mirrors data synchronously between logical or physical sites automatically. Supported for two sites only in this release. Failover Manager A specialized version of the StoreVirtual OS software designed to operate as a manager and provide automated failover capability. The Failover Manager can operate in a two-site configuration without requiring a physical storage system in a third site. The Failover Manager provides quorum management if the network connection between two sites becomes unavailable. Multipathing with the StoreVirtual DSM For iscsi only, provides data path optimization and multipathing. Using the StoreVirtual DSM can reduce latency and improve performance. Split Networking The StoreVirtual OS supports separating certain types of traffic to support specific business needs. This split networking capability provides the flexibility to separate the management traffic and the iscsi traffic. Two traffic types can be assigned separate interfaces on the SAN: The management interface Used by user interface applications like the SVMC, the CLI, and SNMP to manage the storage configuration. The iscsi interface Used for iscsi communications with host systems. Rebranding LeftHand OS is now StoreVirtual OS. System requirements The StoreVirtual 3200 supports a wide variety of operating systems. For a complete list of supported operating systems, visit the Single Point of Connectivity Knowledge (SPOCK) Storage website: Firmware and software compatibility and interoperability 5

6 Fixes Disk drives Enclosure Licensing Network When viewing the Configured Disks Status on the Storage System Overview pane, the assignment of disks to storage controllers is correctly reported. Previously it was reported that a faulty temperature error message caused a degraded state on the enclosure. This issue does not occur in StoreVirtual OS release After applying the Advanced Data Services Suite license, the correct licensed features are listed in the SVMC. Setting the frame size in the SVMC is now enabled. When the speed and duplex settings are changed, the changes display in the SVMC. Now when a network bond is deleted, one of the interfaces can be disabled without incurring an error message about a subnet conflict. Modifying certain network settings no longer risks disrupting data availability. Performance reporting RAID After you clicked Download performance report from the storage pool performance page, the Download Report dialog did not open. The Fibre Channel performance stats were not working correctly in a series selection. Fixed an issue so that a rare RAID configuration error will no longer occur during configuration setup. Software updates The SOCKS proxy was re-enabled in the SVMC and now displays the Software Updates page correctly. Previously, an I/O error message displayed when you attempted to view the page. Updates can now be canceled to resolve critical alarms that might occur. The Tasks menu in the SVMC now has a Cancel option. Storage controller The storage controller cannot be powered off through the SVMC. The disabled Power Off button has been removed from the Storage Controller s menu. StoreVirtual Management Console After one or more series was selected to be shown on the performance chart, the check box was automatically cleared. Issues and workarounds 6 Fixes

7 Safely rebooting a storage controller About this task Safely rebooting a storage controller includes failing over the controller before you reboot, and failing back when the controller comes back online. 1. Fail over the storage controller a. On the StoreVirtual menu, select Storage Systems. b. On the navigation pane, select the storage system, and then select s > Fail over storage controller on the content pane. c. Select the storage controller from the list if more than one is listed. d. Select the check box next to the storage controller status, and then click Yes, fail over storage controller. 2. Reboot the storage controller a. On the StoreVirtual menu, select Storage Controllers. b. On the navigation pane, select the storage controller, and then select s > Power off or reboot on the content pane. c. Click Reboot. d. Enter the number of minutes for the system to wait before rebooting, and then click OK. e. Review the warning message and then click Yes, reboot. f. On the second confirmation message, select the confirmation box, and then click Yes, reboot. 3. Fail back the storage controller a. On the StoreVirtual menu, select Storage Systems. b. On the navigation pane, select the storage system, and then select s > Fail back storage controller on the content pane. c. Select the storage controller to fail back, and then click OK. CLI (on-system only) The CLI command createcluster fails with two storage systems in a management group If a management group has two StoreVirtual 3200 Storage systems, the CLI command to create a cluster (a storage pool) using both of those systems fails. Use the StoreVirtual Management Console to create the storage pool. Use the CLI as follows: 1. Using just one of the two storage systems, create a cluster using the createcluster command. 2. Use the modifycluster command to add the second storage system. Disk drives Safely rebooting a storage controller 7

8 An extra disk displays in the SVMC when a Failover Manager is added to a management group The list of disks in the SVMC Disk Drives navigation pane includes an extra virtual disk when a Failover Manager is added to the management group. The number of disks displayed on the Dashboard is one more than the actual number of disk drives in the storage systems. The Failover Manager creates a small OS disk when it is installed. This disk does not participate in data storage. No action is necessary. This disk does not impact the operation or capacity of the storage systems. Possible time delay when viewing the activated Locate icon in the SVMC When using the Locate feature in the SVMC to activate an LED for a disk, the Locate icon for that disk on the SVMC Disks pane displays blue. If you turn on the Locate feature for a disk while logged in to an SVMC session on one controller, and then open a session of the SVMC by logging in to the other controller, the Locate icon for that disk may not display blue immediately. A delay of minutes may occur before the disk Locate icon displays blue in the SVMC. s This delay is caused by the length of the software monitoring period which is set to five minutes. 1. Wait up to five minutes to determine if the Locate icon will illuminate in the SVMC. Warning notifications are sent as informational s When the severity for notifications is set to Warning, some warning event s may be received as informational notifications. 1. Verify the severity of the event by checking the event details in the SVMC. Failover Manager 8 An extra disk displays in the SVMC when a Failover Manager is added to a management group

9 Running the HPE StoreVirtual FOM Installer fails on Windows Server 2012 Running the HPE StoreVirtual FOM Installer.exe prompts you to unzip the files. Then a terminal window opens, but the Installer then fails to launch either the CLI or GUI installer with the following Windows System error: Error 740: The requested operation requires elevation The StoreVirtual FOM Installer requires Full Administrator privileges. Logging in to Windows Server 2012 or higher system, does not grant Full Administrator privileges automatically, unless the operating system has been configured to disable this protection. Elevate your privileges to Full Administrator before running the StoreVirtual FOM Installer. Hyper-V Cluster Firmware upgrade or disturbances with the controller may cause failover issues with pass-through volumes in a Hyper-V cluster environment A Hyper-V cluster configuration using pass-through or direct mapped volumes to a VM may experience issues with failing over the volume or VM, especially when experiencing heavy I/O. Hewlett Packard Enterprise recommends creating datastores from StoreVirtual OS volumes, and then sharing the datastores between multiple VMs to ensure high availability. An iscsi volume that becomes unavailable for approximately 60 seconds or less may cause data unavailability If a Windows host that is configured with iscsi on all available adapters experiences short multiple disconnections on different adapters, it loses the paths to the disks. The lengths of these short disconnections are less than one minute down and less than or equal to two minutes up. The Windows host does not recover from the disconnection in time and loses all paths to the volume. Extend the time that the host continues to retry the connection by modifying the LinkDownTime registry key, so that it has enough time to recover the paths. LinkDownTime determines how long requests will be held in the device queue and retried if the connection to the target is lost. The default value is 15 seconds. Running the HPE StoreVirtual FOM Installer fails on Windows Server

10 Change the Windows Registry setting for the default LinkDownTime to 120 seconds NOTE: Back up your registry before changing it. 1. Run regedit.exe. 2. Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE- BFC BE10318}\<Instance Number>\Parameters. 3. Double-click LinkDownTime in the right-hand pane. The Edit DWord Value window opens. 4. Enter a value of Click OK. 6. Save your changes and exit the Registry. 7. Reboot the system. Multipathing Read or read/write presentation mode is not visible in server The StoreVirtual Management Console (SVMC) does not reflect changes in the presentation mode (Read or Read/Write) of a volume. Solution 1 This issue occurs if the Windows host corresponding to the server has already established iscsi sessions on the target array. 1. To make any change in the presentation mode of the volume be reflected in the Windows host, first unexport the volume. 2. Export the volume to the corresponding server in the SVMC. Solution 2 This issue occurs if the Windows host corresponding to the server has already established iscsi sessions on the target array. 1. Disconnect all iscsi sessions from the Windows host to the target. 2. Reconnect the sessions. 10 Multipathing

11 This procedure will impact all volumes exported from the target to the Windows host. CHAP settings made in Windows iscsi initiator are not visible CHAP settings made in the Windows iscsi initiator are not visible in the StoreVirtual Management Console (SVMC). CHAP settings made in the Windows iscsi initiator may not be visible in the SVMC if the Windows host has already established iscsi sessions with the target. 1. In the Microsoft iscsi Software Target console tree, click iscsi Targets. 2. In the results pane, right-click the iscsi target, and then click Properties. 3. In the Properties dialog box, change the settings of the properties, and then click OK. Network Column headings may not display when creating or editing an Active-Passive Bond When creating or editing an Active-Passive bond, thetraffic Type and Bond Preferred Interface column headers may be missing from the Create Bond or Edit Bond dialog box. RAID When creating an Active-Passive bond, after adding interfaces to the Create Bond dialog box, select the radio button for the interface to be the Preferred Interface in the bond. When editing an Active-Passive bond, the radio buttons in the Interfaces to bond table indicate which interface is the preferred interface in the bond. To change the preferred interface, change the selected radio button in the table. Adding RAID to a storage system completes successfully although Tasks pane reports an error When adding a disk enclosure and configuring RAID to a storage system in a two-storage system management group, the Tasks pane reports that the task failed with the following error message: Error: The storage controller is busy performing an operation and is unable to process the request. Try the request again later. However, the RAID configuration actually completes successfully. CHAP settings made in Windows iscsi initiator are not visible 11

12 This error occurs when the SVMC is logged in through the storage system that is not adding the disk enclosure. Because adding RAID takes some time, the request to the remote storage system to update the Task status fails. To prevent the Task pane status from reporting an error, log in to the storage system that is scaling up to perform the Add RAID operation. If you experience this issue, verify that the RAID configuration completed successfully by reviewing the RAID arrays in the SVMC. Recreating RAID does not succeed after deleting the previous RAID configuration The existing RAID configuration is deleted, and an attempt is made to recreate RAID using the same drives. The RAID creation process does not succeed. NOTE: This issue does not apply to scale-up RAID. That is, RAID configured on added disks or a disk enclosure. 1. Reboot the storage controllers after deleting RAID. See Safely rebooting a storage controller. 2. Recreate the RAID using one of the following methods: Use the Configuration Setup. Navigate to Storage Systems > s > Add RAID in the SVMC. Removing a disk drive causes an incorrect drive count to display in the SVMC If a disk drive is removed from the storage system, the SVMC displays an incorrect drive count. The SVMC should, instead, indicate that a disk drive is missing and maintain the correct total count. 1. You can ignore the incorrect drive count in the SVMC. When you replace the missing disk drive, the drive count returns to normal. System status and repair behavior are inaccurate when a RAID set is failed in a twostorage system management group When the loss of a RAID set occurs, failed drives must be replaced and the controller must be reconfigured before lost data can be restored from a backup. 12 Recreating RAID does not succeed after deleting the previous RAID configuration

13 1. Call Hewlett Packard Enterprise Support for assistance with this issue. See Support contacts. Remote Copy Remote Copy fails when the remote volume has # in the name A remote volume with a # character in the name causes the remote copy operation to fail. An issue with the LeftHand OS version 13.x and StoreVirtual OS 13.5 removes the character from the name. 1. Do not create remote volumes or snapshots with the # character in the name. Reporting Inaccurate power supply failure status and temperature alarms If one of the two power supplies in a storage system is unplugged, Active Alarms incorrectly report a power supply failure and a critical temperature alarm. The same alarms are reported twice. In an enclosure, both storage controllers monitor the power supplies and both may report the same event. The storage controller monitoring does not distinguish between a missing power supply and a failed power supply, and will generate inaccurate messages. 1. To clear the alarms, plug in the second power supply. Error occurs when attempting to download a management group support bundle from two different SVMC sessions simultaneously In the following scenario: You are logged in simultaneously to two SVMC sessions in a two-node management group. In each SVMC session, you attempt to download the management group support bundle using Settings > General > s > Download support bundle. The downloads will not contain the necessary files. Remote Copy 13

14 The StoreVirtual OS does not support simultaneous duplicate requests at the management group level for downloading the support bundle. 1. Log in to one storage system. 2. Download the management group support bundle one time, using Settings > General > s > Download support bundle. Scale-out Adding or removing a storage system may take longer than expected Adding a storage system to an existing management group may take up to 15 minutes. Removing a storage system from a two-node management group may also take more time than expected. During the operation, the SVMC will not update and will not be available for other operations. There is no action necessary. The operation will complete successfully and the SVMC will become available again. Servers and Server Clusters Unable to assign a backup server to a volume that is assigned to application servers The SVMC provides no method by which to export a volume to a second server that is configured as a backup server. If a volume is mounted as a read-write volume to more than one server or server cluster, it runs the risk of becoming corrupted. The SVMC prevents exporting a volume to more than one server or server cluster to prevent this issue. SNMP Use either the StoreVirtual 3200 REST API or the StoreVirtual OS CLI. Both allow you to export a volume or snapshot to a server that is already exported to a server or server cluster. 14 Scale-out

15 SNMP OID values missing from MIB files The following set of SNMP OID values are not generated or found in the MIB browser, or they have a value of 0. clusvolumeinitiatoraddress clusvolumeinitiatoriqn clusvolumeinitiatorport clusvolumeinitiatorstate clusvolumesnapshotinitiatoraddress clusvolumeinitiatorstatsbytesread clusvolumeinitiatorstatscachehits clusvolumeinitiatorstatsiolatencyread clusvolumeinitiatorstatsiolatencywrite clusvolumeinitiatorstatsiosread clusvolumeinitiatorstatsioswrite clusvolumeinitiatorstatsqdepthwrite clusvolumeinitiatorstatus clusvolumesnapshotinitiatoraddress clusvolumesnapshotinitiatorport clusvolumesnapshotinitiatorstate clusvolumesnapshotinitiatorstatsbytesread clusvolumesnapshotinitiatorstatsbyteswrite clusvolumesnapshotinitiatorstatscachehits clusvolumesnapshotinitiatorstatsiolatencyread clusvolumesnapshotinitiatorstatsiolatencywrite clusvolumesnapshotinitiatorstatsiosread clusvolumesnapshotinitiatorstatsioswrite clusvolumesnapshotinitiatorstatsqdepthread clusvolumesnapshotinitiatorstatus infobootcontrollerbiosversion infocachebpstestoverdue infocachebpsvoltage The following OIDs are not found in the SNMP agent code, indicated by an error message. lhncpuconfig lhncpuutilization lhnserialnumber lhntemperature Updated SNMP OIDs will be available in a later release. 1. To obtain the desired information, use the REST API or the SVMC. Storage controller SNMP OID values missing from MIB files 15

16 Storage controller displays incorrect state when storage system is powered off A storage system is powered off. One storage controller displays a state of currently serving all the data, although the storage system state displays data is not available. No action is necessary. The storage system is actually off, and all the status messages will become regular when the storage system is powered back on. Failing over the storage controller with the VIP causes the VIP to go offline When repairing or replacing a storage controller, if you fail over the storage controller that holds the VIP, the VIP will go offline and you cannot log in to the SVMC using the VIP. If you have to remove a storage controller, perform the following steps in the SVMC: 1. On the StoreVirtual menu, select Storage Pool. 2. In the General section, look at the field labeled VIP holder. a. If the storage controller to be repaired does not hold the VIP, continue with the procedure to replace the controller module in the HPE StoreVirtual 3200 Storage User Guide. b. If the storage controller to be repaired holds the VIP, continue with the following steps. 3. On the StoreVirtual menu, select Storage Controller. 4. On the navigation pane, select the storage controller, and then select s > Reboot on the content pane. 5. Enter the number of minutes for the system to wait before rebooting, and then click OK. 6. Review the warning message, and then click Yes, reboot. 7. On the second confirmation message, select the confirmation box, and then click Yes, reboot. 8. After the storage controller has rebooted, verify that the VIP holder is now the other storage controller, that is, the controller that does not need removing. 9. Continue with failing over the storage controller to be removed, and the remaining procedures in the HPE StoreVirtual 3200 Storage User Guide. Storage system Activity pane does not display status of storage system repair operation After running repair on a storage system, the Activity pane does not display information about the success or failure of the repair operation. 16 Storage controller displays incorrect state when storage system is powered off

17 1. Manually refresh the storage system page and check the repair state. If the repair state is "in repair," then the repair operation was successful. RAID configurations with hot spares display drive count discrepancy In the Storage System window, a disk RAID configuration that includes hot spares has the total number of hot spares reported as owned by controller 1. This issue is caused by a reporting anomaly. 1. No action is necessary. The number of hot spares is reported correctly in the Configured disks status section. Hardware monitoring and SAS cable checking require the system clock setting before January 19, 2038 If the system clock is set after January 19, 2038, hardware monitoring and SAS cable checking will not function correctly. As a result, alerts may be generated and appear in the SVMC and in Remote Support. 1. Ensure that the system clock of the StoreVirtual 3200 Storage system is set to a date before January 19, This issue will be fixed in a future release. StoreVirtual Management Console (SVMC) The SVMC responds slowly if a storage controller or a storage system in a management group is unreachable on the network The SVMC details panes and feature dialogs respond slowly when trying to accomplish a task or find information in the SVMC. This issue occurs if any storage controller in a management group is unreachable on the network. In a twosystem management group, a storage system that is powered down for maintenance could cause this issue. RAID configurations with hot spares display drive count discrepancy 17

18 No action is necessary. SVMC performance returns to normal when all storage systems and storage controllers are accessible on the network. Localized online help is not available for release version 13.5 In the localized SVMC, clicking a help link for a new feature opens the Home page of the help. Due to a change in how the WebHelp must be configured, localized HPE StoreVirtual Management Console Online Help is not available for the 13.5 release. To access online help for the 13.5 enhancements, configure your browser to use English. The English online help is updated for release The localized HPE StoreVirtual Management Console User Guide will be available in PDF format approximately six weeks after the release. This User Guide contains the information available in the online help. Localized help files will be included in the next release. Unable to log in to the SVMC (spinning icon) When logging in to the SVMC, the log in hangs (the spinning icon appears). Access to the SVMC requires cookies to be enabled in the browser. 1. Enable cookies in the browser that you are using (for instructions, see your browser documentation). StoreVirtual OS The name LeftHand OS appears in the REST API interface and in the CLI Instances of LeftHand OS and LHOS are displayed in the REST API interface and in the CLI. The LeftHand OS has been rebranded to StoreVirtual OS. However, to maintain backward compatibility, the REST API interface and CLI continue to use LeftHand OS and LHOS. 18 Localized online help is not available for release version 13.5

19 No action is required. SCVMM Storage status displays Not Responding During a reboot of the SCVMM server, the provider status displays Not Responding in the SCVMM console. 1. To change the status to Responding, choose one of the following actions: Wait approximately 10 minutes for the status to change. Right-click the provider and select Refresh. Right-click the provider and select Rescan. Disk status for SAN copy capable is No When creating a volume in the SVMC, and then mounting it on a Windows host using Windows Server Manager or Disk Management, the disk status is No for SAN copy capable. The StoreVirtual 3200 Storage system does not support Windows Server Manager. 1. Mount the volume to the Windows host using SCVMM. Virtual Manager When starting a Virtual Manager in a two-storage system management group, not all the storage controllers are displayed in the SVMC Starting a Virtual Manager requires selecting a storage controller upon which to start the Virtual Manager. If you log in to the SVMC and navigate directly to Settings > Manager Status to start the Virtual Manager, then when presented with the list of storage controllers, not all storage controllers are listed. SCVMM 19

20 1. Exit the Start Virtual Managers dialog box. 2. Navigate to StoreVirtual > Storage Controllers. 3. Return to StoreVirtual > Settings > Manager Status > s > Start Virtual Manager. 4. When you navigate to the list of storage controllers, all four storage controllers are listed. Support contacts For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: Receive support alerts announcing product support communications, driver updates, software releases, firmware updates, and customer replaceable component information, in your by signing up at: Related information The latest StoreVirtual documentation is available at: HPESC: Storage Information Library: 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 (docsfeedback@hpe.com). 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. 20 Support contacts