HPE StoreVirtual 3200 Storage Release Notes

Transcription

1 HPE StoreVirtual 3200 Storage Release Notes LeftHand OS 13.0 Part Number: Published: October 2016 Edition: 2

2 Copyright 2016, Hewlett Packard Enterprise Development LP 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.

3 Description These release notes describe the first release of the StoreVirtual 3200 Storage product, which contains the following software components: HPE LeftHand OS Software Version HPE StoreVirtual Management Console (SVMC) Version HPE StoreVirtual LeftHand OS Command Line Interface (CLI) Version (on-system only) HPE StoreVirtual REST API Version 2.0 HPE StoreVirtual Application Aware Snapshot Manager Version HPE LeftHand SNMP MIBs Version These release notes are current as of the published date. Platforms supported for this release Languages HPE StoreVirtual 3200 (array enclosure) HPE StoreVirtual 3000 (disk enclosure) 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. Firmware and software compatibility and interoperability Features Release supports both iscsi and Fiber Channel. SCVMM is not supported in version Support for SCVMM will be available in a future release. 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. Application Consistent Snapshots Create application consistent snapshots of VMware and Hyper-V VMs, and of Microsoft VSS-enabled applications. Network RAID Network RAID 0 and 10 are supported on the StoreVirtual Network RAID 0 is enabled by default and maintains data availability to applications if a drive or controller fails. Thin Provisioning Thin Provisioning allocates space only as data is written to that volume. Description 3

4 Space Reclamation Reclaim space on thinly and fully provisioned volumes used by Windows Server 2012 or later, and vsphere 5 or later. REST API The REST API provides a programmatic interface for configuring, managing, and maintaining the StoreVirtual 3200 storage system. SmartClone volumes Make multiple identical virtual copies (or clones ) of volumes without requiring additional storage space. Remote Copy (included in the Advanced Data Services Suite) Remote Copy is an asynchronous replication of data that copies snapshots between primary and remote locations. Remote copies are thin provisioned, so no space reservation at the remote location is required. Adaptive Optimization (included in the Advanced Data Services Suite) Adaptive Optimization (AO) intelligently moves data between tiers of storage with different performance characteristics within a single storage system. AO increases the efficient use of faster storage devices (such as SSDs). 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: Issues and workarounds Safely rebooting a storage controller Safely rebooting a storage controller includes failing over the controller before you reboot, and failing back when the controller comes back online. Failing over the storage controller 1. On the StoreVirtual menu, select Storage Systems. 2. On the navigation pane, select the storage system, and then select s Fail over storage controller on the content pane. 3. Select the storage controller from the list if more than one is listed. 4. Select the check box next to the storage controller status, and then click Yes, fail over storage controller. Rebooting the storage controller 1. On the StoreVirtual menu, select Storage Controllers. 2. On the navigation pane, select the storage controller, and then select s Power off or reboot on the content pane. 3. Click Reboot. 4. Enter the number of minutes for the system to wait before rebooting, and then click OK. 5. Review the warning message and then click Yes, reboot. 6. On the second confirmation message, select the confirmation box, and then click Yes, reboot. Failing back the storage controller 1. On the StoreVirtual menu, select Storage Systems. 2. On the navigation pane, select the storage system, and then select s Fail back storage controller on the content pane. 3. Select the storage controller to fail back, and then click OK. 4 System requirements

5 Adaptive Optimization (AO) Adaptive Optimization defaults to off before the license is applied After applying a license, data is written only to Tier 1, and Tier 0 displays zero usage. Volumes created before a license is applied are created with Adaptive Optimization set to Not Permitted. Applying a license does not change the AO setting on existing volumes. Reboot each storage controller. To reboot safely, see Safely rebooting a storage controller (page 4). Application Aware Snapshot Manager (AASM) Using AASM with Fibre Channel systems requires an iscsi initiator When configuring a Fibre Channel server, if you enter an IP address for the AASM server, you cannot save the server configuration. To create a Fibre Channel server using an AASM server IP address: 1. Configure an iscsi initiator on the application server. 2. In the SVMC server configured with the AASM server IP address, enter the iscsi IQN along with the Fibre Channel initiator information. 3. Save the server configuration. Unable to take a manual application-managed snapshot When using the Application Aware Snapshot Manager, you are unable to take a manual application-managed snapshot. To take the snapshot, create a snapshot schedule. You can create a schedule to take just one snapshot immediately. Application-managed snapshot schedule can fail for applications in a clustered environment When the snapshot schedule runs for application-managed snapshots, the following error is displayed: Error - Host volume list and schedule volume list differ The server ownership of volumes mounted in a clustered server environment may change over time due to events such as server failovers. This change in server ownership can cause the scheduled snapshot to fail. Issues and workarounds 5

6 Use the StoreVirtual 3200 CLI to create scheduled application-managed snapshots. See the HPE StoreVirtual 3200 Software CLI Reference Guide. Application-managed snapshot is actually a point-in-time snapshot In the SVMC Tasks pane, the status of a scheduled application managed snapshot may report success, but a point-in-time snapshot was taken. This can happen in a Windows/VSS environment when the volumes being snapped fail to quiesce in a timely manner. Verify the Application-Managed status of the snapshot on the Snapshot Overview pane of the SVMC. CLI (on-system only) Creating and exporting volumes using the CLI is slow Creating and exporting volumes using the CLI is very slow when attempted immediately after configuring a StoreVirtual 3200 Storage system. CLI performance is degraded during the initialization phase of configuring RAID on the storage system. This phase occurs immediately after a StoreVirtual 3200 Storage system is initially configured. Wait to begin creating and exporting volumes until RAID configuration has finished. If you started creating and exporting a volume, and it is taking longer than expected, wait and eventually the process will finish. The createcluster command fails with a time-out message The createcluster command fails with the message Timed out waiting for storage ready. If you run the createcluster command and specify the IP addresses of both controllers, the command fails. Specify only the IP address of controller A when running the createcluster command. If that fails, try running the command with the IP address of controller B. Server commands may not store name and target secret When you try to assign a server the chapname and targetsecret using the createserver or modifyserver command, those values are not stored. 6 Issues and workarounds

7 Using the commands createserver or modifyserver without specifying the value usechap=1 causes the related CHAP parameters not to be saved. Specify all the listed CHAP parameters when using the commands createserver or modifyserver: usechap=1 chapname=xxxx targetsecret=xxxx The CLI command creategroup sometimes stalls In rare cases, running the creategroup command from the CLI does not appear to finish, and it does not display an error. Avoid this issue by using one of the following methods: Use the Configuration Setup wizard in the SVMC Run the creategroup command from the REST API To resolve this issue, you must reimage the storage system. The CLI command assignvolumechap fails with an error message Configuring CHAP authentication for iscsi connections using the assignvolumechap CLI command fails with the following error message: CreateVolumeAccess Operation Failed: Multiple LUNs Per Target iscsi volumes' LUN must be non-zero. Ensure the LUN is set to a non-zero value and try again. To assign a volume to a server without using CHAP authentication, use the CLI command AssignVolumeToServer. To script server configurations with CHAP authentication, use the REST API. Configuration setup Complete the Configuration Setup if interrupted If the Configuration Setup is interrupted before it finishes, you must return to the Configuration Setup to complete the configuration. You might navigate away from the Configuration Setup page, or get interrupted by another demand. Also, clicking the StoreVirtual menu interrupts the process. Issues and workarounds 7

8 Return to the Configuration Setup using one of these methods: Use the browser Back button to return to the Configuration Setup window. Open the browser History and select the Configuration Setup page from the history list. Log out of the existing session and log back in. Depending on where you were in the process when you were interrupted, you may need to use the newly created Management Credentials to log back in. RAID configuration may fail A rare occurrence during Configuration Setup may cause the RAID configuration to fail with an error message. If you receive an error message that the RAID configuration has failed, the Configuration Setup has not finished. Log out of the SVMC and log in again. The Configuration Setup window opens, and you can run the Configuration Setup again. Misconfigured cabling prevents RAID configuration and upgrades If the HPE StoreVirtual 3200 cabling is misconfigured, RAID cannot be configured and upgrades cannot be applied. A Miscabled alarm is present in the storage system. Disk drives 1. Correct the cable configuration of the HPE StoreVirtual Reboot the storage system. Green activity LEDs do not work as expected during certain activities The green activity LEDs on disk drives do not blink correctly during the following two activities: Initializing a new volume on a RAID array Rebuilding data on an activated hot spare disk drive Due to a communication issue, the disk drive activity does not activate the green LEDs properly. No action is required. Failed drive alert shows incorrect drive information When a drive fails, the alert refers to the drive location using an internal representation of the drive location. The location in the alert may not match the failed drive listed on the Disks window in the SVMC. 8 Issues and workarounds

9 The disk information on the Disks window, and the disk drive ID LED in the storage system identify the correct disk drive. Disk failures cause volume to go offline In rare circumstances, if a specific combination of drives fails, quorum cannot be maintained and volumes become unavailable in a Network RAID 10 configuration. Under normal circumstances, the loss of two drives in a RAID 5 configuration, or three drives in a RAID 6 configuration, would not cause Network RAID 10 volumes to become unavailable. For help with this issue, contact Hewlett Packard Enterprise support through the Hewlett Packard Enterprise Worldwide website: 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. This delay is caused by the length of the software monitoring period which is set to 5 minutes. Wait up to 5 minutes to determine if the Locate icon will illuminate in the SVMC. Configured Disks Status is incorrect after renaming a storage system or a storage controller s When viewing the Storage System Overview pane, the Configured Disks Status is incorrect. All the disks are reported as belonging to one controller. No action is necessary. Wait for approximately 20 minutes for the system to finish updating. The disk status changes to the correct distribution of disks to controllers. 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. Verify the severity of the event by checking the event details in the SVMC. Issues and workarounds 9

10 Enclosures A disk enclosure from a 3PAR StoreServ installed into a StoreVirtual 3200 Storage system results in the enclosure status as unknown Installing a 3PAR StoreServ disk enclosure into a StoreVirtual 3200 Storage system results in the enclosure status reporting unknown in the SVMC and via REST. A 3PAR StoreServ enclosure is not compatible with the StoreVirtual array and should not be used. Shut down the storage system and remove the 3PAR StoreServ disk enclosure. Enclosure is in a degraded state due to a faulty temperature error message The Events pane displays an incorrect critical event, EID_TEMPERATURE_FAULTY, for the LOM-Sensor. This critical event sets a degraded state on the enclosure. System configuration changes like RAID creation and upgrades are prevented any time the controller reports a degraded state. To clear the issue, safely reboot the storage controller. See Safely rebooting a storage controller (page 4). Fibre Channel Fibre Channel port persists after removal from active zone In some circumstances, removing a Fibre Channel port from an active zone may not clear the port session from showing in the SVMC. If you intend to remove a port from the zone, you must unplug the port or move it to another zone to ensure that the session is displayed correctly in the SVMC. Additional Fibre Channel WWPNs not displayed in SVMC The StoreVirtual 3200 Storage system has two physical WWPNs per storage controller and two virtual WWPNs enabled by NPIV. The two WWPNs enabled by NPIV are not displayed in the SVMC. When configuring zones for the StoreVirtual 3200 Storage system, include both the physical and virtual WWPNs for each storage controller. 10 Issues and workarounds

11 Licensing Unavailable features display as licensed Network After applying the Advanced Data Services Suite license, additional features may display as licensed. This suite licenses only the following features: Remote Copy Adaptive Optimization Ignore additional features in the list of licensed features. Additional features will be available in a future release. Speed and duplex setting changes are not displaying in the SVMC When changing the speed and duplex settings for a network interface, the changes are not reflected in the SVMC. Due to a communication issue in the LeftHand OS, the updated settings are not communicated to the SVMC. This issue will be fixed in a future release. Setting the frame size is disabled in the SVMC Due to an issue with setting the frame size in the SVMC, that feature is not available in this release. This issue will be fixed in a future release. Edit bond dialog box displays duplicate IP addresses When editing a bond in the SVMC, the primary IP address of the bonded interface is listed as the IP address for both interfaces in the Interfaces to Bond table. Due to a reporting error, the individual interfaces are reported as both having the primary interface IP address. No action is necessary. The correct IP addresses are displayed in the IP Configuration section. Static IP address requires a default gateway entry When configuring an interface with a static IP address, and you leave the Gateway box empty, the configuration fails with the following error message: Issues and workarounds 11

12 Unable to update TCP/IP The supplied data in the request is missing or contains malformed data: defaultgateway bad datatype. The Gateway box is blank by default. If you are using a static IP address, the Gateway box requires an entry. If you are entering a static IP address and you do not have a gateway, enter Cannot disable an interface from a previously bonded configuration When a network bond is deleted, a subnet conflict occurs that prevents you from disabling one of the interfaces. When the bond is deleted, both interfaces remain enabled with static IP addresses with the same subnet mask. The attempt to disable an interface fails with the following error message: A subnet conflict between interface x and interface y exists please use a different subnet for each interface. To disable the interface: 1. On the StoreVirtual menu, select Storage Controllers. 2. On the navigation pane, select the storage controller and navigate to Storage Controllers Network. 3. Click s Edit TCP/IP. 4. In the General section, select the interface you want to disable. 5. Change the IP address of the interface to an IP address on a different network, and then click OK. The Edit TCP/IP dialog box closes. 6. Click s Edit TCP/IP. 7. Select the interface again, and change the Interface box to Disabled, and then click OK. Deleting a bond can result in the loss of the gateway configuration If you delete a bond, the network configuration information may be lost. If you are running the SVMC from a different subnet, you may lose access to the storage system. To prevent this issue, create the bond with the gateway specified. To fix this issue if you are running the SVMC from a different subnet and cannot connect to the SVMC using the controller IP, perform the following steps: 1. Open a web browser and connect to the SVMC via the other controller IP address. 2. On the StoreVirtual menu, select Storage Controllers. 3. On the navigation pane, select the controller that has the interface without a gateway. 4. Select s Edit TCP/IP. 5. Select the network interface to correct from the list. 12 Issues and workarounds

13 6. Enter the gateway information. 7. Click OK to save your changes. If you cannot open the SVMC using the IP address of the other controller, you can connect via the MGMT port, as you did when first configuring the storage system. 1. Connect an Ethernet cable to the MGMT port using one of the default IP addresses: eth2 on Controller 1 is set to the IP address eth2 on Controller 2 is set to the IP address Follow steps 2 through 7 to reconfigure the gateway on the controller that is missing the gateway setting. 3. Log out of the SVMC and disconnect the Ethernet cable. Modifying a bond may cause the storage controller to fail over After creating a bond on an iscsi storage system, if you edit the bond in the SVMC, the storage controller may fail over. To recover from failover, safely reboot the storage controller. See Safely rebooting a storage controller (page 4). Modifying certain network settings may cause interface to become unavailable temporarily A network interface will become unavailable when it is being modified. Data may become unavailable while the interface comes back online. The following actions will cause the interface to become unavailable: Changing, adding, or removing any of the following configurations IP address Subnet mask Gateway RAID Schedule such modifications when bringing the interface down will be the least disruptive. To avoid the interface shutdown, do not make the described modifications. RAID array remains degraded after hot spares rebuild After a disk drive fails and the disk drive designated as the hot spare is rebuilt, RAID remains in a degraded state. The RAID configuration remains degraded until the failed drives are replaced and the new drives rebuild. Issues and workarounds 13

14 Replace the failed drives. After the new drives rebuild, the degraded state clears. 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. You can ignore the incorrect drive count in the SVMC. When you replace the missing disk drive, the drive count returns to normal. Duplicate RAID selections presented when configuring RAID When choosing a non-recommended RAID configuration, the list of selections appears to have duplicate RAID configurations. The list of selections is missing configuration details about the number of RAID devices and the number of disks per device. Select the desired RAID configuration from the list, and then view the details in the table and summary sections in the dialog box. 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 removes the character from the name. Do not create remote volumes or snapshots with the # character in the name. Incorrect error message when creating a remote snapshot schedule When creating a remote snapshot schedule, if the remote volume type is set to Primary, the following error message is displayed: Unable to create remote snapshot schedule An HTTP failure occurred when sending an internal REST command to the storage controller at IP address "xx.xx.xx.xxx." The error returned from the HTTP call was: Change the volume type to Remote: 1. Open the SVMC and log in. 14 Issues and workarounds

15 2. From the StoreVirtual menu, select Volumes. 3. Select the volume you want to make remote. 4. Select s Edit. 5. Click Advanced Option. 6. Select Remote in the Type box. 7. Click OK. 8. Create the remote snapshot schedule. Using the CLI to create a remote snapshot fails After using the CLI to create a remote snapshot, the remote group association in the SVMC shows an error status and the outbound bandwidth is not set. Reporting Do not use the CLI to create remote snapshots. To recover, perform the following steps in the SVMC: 1. From the StoreVirtual menu, select Settings. 2. Select the Remote Associations tile, and then click the edit icon ( ) next to the remote group you want to edit. 3. Recreate the association by entering the information in the Edit Remote Association dialog. 4. Click OK to finish. Inconsistent reporting of storage pool utilization SNMP Storage pool capacity percentages in the SVMC may differ from the capacity reported in the events and alarms views. While the LeftHand OS performs more precise capacity calculations, those values are not reflected in the storage pool utilization report in the SVMC. Use the SVMC storage pool capacity report as a guide to approaching full capacity. The capacity alarms are triggered based on the more precise calculations of the LeftHand OS. 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 Issues and workarounds 15

16 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 To obtain the desired information, use the REST API or the SVMC. Updated SNMP OIDs will be available in a later release. Storage controller Servicing controller incorrectly presented in the SVMC A RAID device is owned by only one controller in the storage system. This servicing controller may be incorrectly presented in the SVMC. The misreporting of the servicing controller can happen if all three following conditions are met: RAID has been configured A management group has not been created yet One of the storage controllers fails You can ignore the information; the system will work as designed. The issue corrects itself once the failed controller is replaced. 16 Issues and workarounds

17 Powering off the storage controller in the SVMC is disabled In the s menu for a storage controller, the Power off or Reboot menu item only enables the Reboot option. To power off the storage controller, use an unfolded paper clip or other small pointed device to press the recovery/power button for one second. The recovery/power button is on the back of the storage controller module. For button location and behavior, see Component identification in the HPE StoreVirtual 3200 Storage Installation Guide. Locate LED only activates for logged-in controller When attempting to locate the second storage controller listed in the SVMC Storage Controller window, using the locate feature does not activate the ID LED on the storage system. When logging in to the SVMC, use the IP address of the storage controller you want to locate. The restore peer task reports complete too early After repairing a storage controller and using the restore peer process in the SVMC, the status bar jumps to 100% complete after a few minutes. However, the process is not complete and there are approximately 10 minutes remaining. During this remaining time, the new controller is not accessible, and the system still reflects the previous mismatched state. No action is necessary. Wait until the controller displays a green status of OK. Storage controller failover alarm is not cleared after failback is complete In rare cases, a failover alarm does not get cleared when both storage controllers are fully operational again. This failover alarm is generated when one controller is rebooted due to an upgrade or a controller replacement. The system fails over to the other controller, and then fails back when the first controller comes back up. In this case, both controllers are fully operational, and the SVMC windows report the controller statuses correctly. However, the alarm remains on the Active Alarms window. Verify that the failover event is over by checking the status of the storage controllers on the Storage Controllers window of the SVMC. Status will be OK. To clear the alarm, safely reboot the storage system. See Safely rebooting a storage controller (page 4). Failing over the storage controller with the VIP causes the VIP to go off line When repairing or replacing a storage controller, if you fail over the storage controller that holds the VIP, the VIP will go off line and you cannot log in to the SVMC using the VIP. Issues and workarounds 17

18 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. If the storage controller to be repaired holds the VIP, continue with the following steps. 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. 3. On the navigation pane, select the storage controller, and then select s Power off or reboot on the content pane. 4. Click Reboot. 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 Storage system report lists versions for all software and firmware components [informational] Software and firmware versions for the StoreVirtual 3200 Storage are displayed in the storage system report. The storage system report captures details about the hardware and software components of the storage system. 1. Select a storage system in the navigation pane. 2. Select the storage system report in the content pane. 3. Review the details of the storage system report to find the desired component version information. Creating a support bundle appears unresponsive Downloading a support bundle takes a long time to complete and the system seems unresponsive. This issue can occur during a heavy workload. Reduce workload when generating support bundles, or generate the bundle and let the process run. The support bundle will eventually finish and be available. 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 Issues and workarounds

19 This issue is caused by a reporting anomaly. 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. 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 storage system report and some error messages are not localized Users running a localized version of the SVMC will receive some error messages and the storage system report in English. Upgrades No action is required. This issue will be fixed in a future release. Resolve critical alarms during an upgrade During an update, a critical alarm may occur. A critical alarm stops the upgrade. For the upgrades to proceed, resolve the alarm. You may also need to reboot each storage controller and then try updating again. To reboot safely, see Safely rebooting a storage controller (page 4). Upgrade of second controller fails with error message After upgrading the first controller in a StoreVirtual 3200, the upgrade of the second controller aborts with the message: An error occurred while accessing the file "/mnt/mgmt/upgrades/ statusfile". The error code was "2". This error is displayed in the error details for the install step that failed. Issues and workarounds 19

20 Running heavy I/O on the storage system while upgrading may increase the likelihood for the conditions that cause this issue. Updating your systems during a period of low I/O may make this upgrade error less likely. If this issue occurs, perform the following steps: 1. Check the system to ensure that it is in a healthy state, with no critical alarms or other issues. 2. Verify that the first controller was successfully updated by checking the OS version on the Storage Controller window in the SVMC. 3. Restart the upgrade. The upgrade process automatically detects that the first controller has been upgraded and will only update the remaining controller. Using the SOCKS proxy, the SVMC cannot connect to the Software Updates site If you are using SOCKS as the proxy type, attempting to view the Software Updates page displays the following error: An I/O error occurred while downloading the file "upgrades_manifest.xml" from " The error returned was: :47:48 - If possible, use the HTTP proxy type. If you must use the SOCKS proxy type, perform the following steps: 1. Download the site bundle from the Hewlett Packard Enterprise download site. 2. Create an internal FTP site or an NFS share. 3. Extract the contents of the site bundle to the internal FTP site or NFS share. 4. In the SVMC, edit the Updates location by navigating to Settings Updates Edit. 5. From the Source of update files drop-down list, select the internal FTP site or NFS share. Upgrade while in Support Mode fails In the Tasks view, the task detail contains the following error message: One or more of the store processes are in the wrong state to perform the update on the controller with IP address aaa.bbb.ccc.ddd RAID is in a degraded state. 1. Review the health status and event information for details about the degraded RAID. 2. Resolve the degraded RAID issues and try the upgrade again. 20 Issues and workarounds

21 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 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. Support contacts 21