Hpe Storevirtual 3200 Storage Release Notes (lefthand Os 13.1)

Transcript

HPE StoreVirtual 3200 Storage Release Notes (LeftHand OS 13.1) Part Number: 865552-004 Published: December, 2016 Edition: 4 © 2016 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 12.211 and 12.212, 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 Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries. Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated. Java® and Oracle® are registered trademarks of Oracle and/or its affiliates. UNIX® is a registered trademark of The Open Group. 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 13.1.00.0120 HPE StoreVirtual Management Console (SVMC) Version 13.1.0.20 HPE StoreVirtual LeftHand OS Command Line Interface (CLI) Version 13.1.00.0120 (on-system only) HPE StoreVirtual REST API Version 2.0 HPE StoreVirtual Application Aware Snapshot Manager Version 13.0.1.138 HPE LeftHand SNMP MIBs Version 13.1.00.0120 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 13.1. 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.1 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. Firmware and software compatibility and interoperability SCVMM is supported in version 13.1.00. View the complete StoreVirtual 3200 Storage compatibility and interoperability at HPE Single Point of Connectivity Knowledge (SPOCK) Storage: 3 1. Go to https://www.hpe.com/storage/spock. 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 13.1 and they are installed automatically through the Online Upgrade feature. • • Patch 130-002—This patch fixes a shutdown issue that led to the loss of crucial logs on storage systems running LeftHand OS version 13.0. Patch 130-003—This patch loads software that is required to complete the update to LeftHand OS 13.1. 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: http://www.hpe.com/storage/spock Enhancements • Network connectivity— Added support for 4x10GBase-T host connectivity. Network interface options are available for both SFF and LFF storage Fixes Application Aware Snapshot Manager (AASM) • • • • When using the AASM with Fibre Channel systems, you only need a Fibre Channel initiator when creating a Fibre Channel server. Previously, it was necessary to create an iSCSI initiator and configure it with the Fibre Channel initiator and iSCSI IQN information as a workaround. Application-managed snapshot schedules now complete successfully in a clustered environment. You are now able to take a manual application-managed snapshot. When the snapshot is a a point-in-time snapshot, it will no longer be reported as a successful applicationmanaged snapshot. Configuration setup • • • After fixing a miscabled StoreVirtual 3200 storage system, the Miscabled alarm clears and RAID configuration and updates can be completed. Failed drive alerts now show correct drive information. If a specific combination of drives fails, Network RAID 10 volumes no longer go offline. Fibre Channel • • • • 4 After removing a Fibre Channel port from an active zone, the SVMC accurately reflects the removal in the status of the port session. All Fibre Channel WWPNs are now displayed in the SVMC. Deleting a bond no longer causes the loss of the gateway configuration. Modifying a bond no longer causes the storage controller to fail over. Prerequisites Network • When configuring a static IP address, the Default Gateway box now defaults to 0.0.0.0. RAID • The list of non-recommended RAID configurations now includes the number of RAID devices and the disks per device as part of the RAID description. Remote Copy • When creating a remote snapshot schedule, if the remote volume type is set to Primary, the error message now presents the correct action to take. Storage controller • • • The Locate feature works correctly for both storage controllers listed in the SVMC Storage Controller window, regardless of which controller you are logged in to using the SVMC. After repairing a storage controller and using the restore peer process in the SVMC, the status bar now waits to reflect the process completion accurately. The storage controller failover alarm is now cleared after failback is complete. StoreVirtual Management Console (SVMC) • The localized versions of the storage system report and all error messages are included in the SVMC version 13.1. Software updates • Fixed an issue where updating the second controller could fail. Now there is more time during the update process for it to succeed when it gets to the second controller. 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. Procedure 1. Fail over the storage controller a. On the StoreVirtual menu, select Storage Systems. a. On the navigation pane, select the storage system, and then select Actions > Fail over storage controller on the content pane. b. Select the storage controller from the list if more than one is listed. a. 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 Actions > 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 Issues and workarounds 5 a. On the StoreVirtual menu, select Storage Systems. b. On the navigation pane, select the storage system, and then select Actions > Fail back storage controller on the content pane. c. Select the storage controller to fail back, and then click OK. Adaptive Optimization (AO) Adaptive Optimization defaults to off before the license is applied Symptom After applying a license, data is written only to Tier 1, and Tier 0 displays zero usage. Cause 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. Action Procedure • Reboot each storage controller. To reboot safely, see Safely rebooting a storage controller. CLI (on-system only) Creating and exporting volumes using the CLI is slow Symptom Creating and exporting volumes using the CLI is very slow when attempted immediately after configuring a StoreVirtual 3200 Storage system. Cause 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. Action Procedure • 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 Symptom The createCluster command fails with the message Timed out waiting for storage ready. Cause If you run the createCluster command and specify the IP addresses of both controllers, the command fails. 6 Adaptive Optimization (AO) Action Procedure • 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 Symptom When you try to assign a server the chapName and targetSecret using the createServer or modifyServer command, those values are not stored. Cause Using the commands createServer or modifyServer without specifying the value useCHAP=1 causes the related CHAP parameters not to be saved. Action Procedure 1. Specify all the listed CHAP parameters when using the commands createServer or modifyServer: a. useCHAP=1 b. chapName=xxxx c. targetSecret=xxxx The CLI command createGroup sometimes stalls Symptom In rare cases, running the createGroup command from the CLI does not appear to finish, and it does not display an error. Solution 1 Action Procedure • To avoid this issue, do one of the following: 1. Use the Configuration Setup wizard in the SVMC. 2. Run the createGroup command from the REST API. Solution 2 Action Procedure • To resolve this issue, you must reimage the storage system. The CLI command assignVolumeChap fails with an error message Server commands may not store name and target secret 7 Symptom 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. Solution 1 Action Procedure • To assign a volume to a server without using CHAP authentication, use the CLI command AssignVolumeToServer. Solution 2 Action Procedure • To script server configurations with CHAP authentication, use the REST API. Configuration setup Complete the Configuration Setup if interrupted Symptom If the Configuration Setup is interrupted before it finishes, you must return to the Configuration Setup to complete the configuration. Cause You might navigate away from the Configuration Setup page, or get interrupted by another demand. Also, clicking the StoreVirtual menu interrupts the process. Action Procedure 1. Return to the Configuration Setup using one of the following methods: a. Use the browser Back button to return to the Configuration Setup window. b. Open the browser History and select the Configuration Setup page from the history list. c. 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 Symptom 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. 8 Configuration setup Action Procedure • Log out of the SVMC and log in again. The Configuration Setup window opens, and you can run the Configuration Setup again. Disk drives Green activity LEDs do not work as expected during certain activities Symptom 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 Cause Due to a communication issue, the disk drive activity does not activate the green LEDs properly. Action Procedure 1. No action is required. Possible time delay when viewing the activated Locate icon in the SVMC Symptom 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 2.5–5 minutes may occur before the disk Locate icon displays blue in the SVMC. Cause This delay is caused by the length of the software monitoring period which is set to five minutes. Action Procedure 1. Wait up to five 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 Symptom When viewing the Storage System Overview pane, the Configured Disks Status is incorrect. All the disks are reported as belonging to one controller. Disk drives 9 Action Procedure 1. No action is necessary. Wait approximately 20 minutes for the system to finish updating. The disk status changes to the correct distribution of disks to controllers. Emails Warning email notifications are sent as informational emails Symptom When the severity for email notifications is set to Warning, some warning event emails may be received as informational notifications. Action Procedure 1. Verify the severity of the event by checking the event details in the SVMC. Enclosures A disk enclosure from a 3PAR StoreServ installed into a StoreVirtual 3200 Storage system results in the enclosure status as unknown Symptom 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. Cause A 3PAR StoreServ enclosure is not compatible with the StoreVirtual array and should not be used. Action Procedure 1. 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 Symptom 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. 10 Emails Action Procedure 1. To clear the issue, safely reboot the storage controller. See Safely rebooting a storage controller on page 5. An iSCSI volume that becomes unavailable for approximately 60 seconds or less may cause data unavailability Symptom 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. Cause 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. Action Procedure 1. 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-11CEBFC1-08002BE10318}\\Parameters. 3. Double-click LinkDownTime in the right-hand pane. 4. 5. 6. 7. The Edit DWord Value window opens. Enter a value of 120. Click OK. Save your changes and exit the Registry. Reboot the system. Licensing Unavailable features display as licensed Symptom After applying the Advanced Data Services Suite license, additional features may display as licensed. This suite licenses only the following features: 11 • • Remote Copy Adaptive Optimization Action Procedure 1. Ignore additional features in the list of licensed features. Additional features will be available in a future release. Network Speed and duplex setting changes are not displaying in the SVMC Symptom When changing the speed and duplex settings for a network interface, the changes are not reflected in the SVMC. Cause Due to a communication issue in the LeftHand OS, the updated settings are not communicated to the SVMC. Action Procedure 1. This issue will be fixed in a future release. Setting the frame size is disabled in the SVMC Symptom Due to an issue with setting the frame size in the SVMC, the feature is not available in this release. Action Procedure 1. This issue will be fixed in a future release. Edit bond dialog box displays duplicate IP addresses Symptom 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. Cause Due to a reporting error, the individual interfaces are reported as both having the primary interface IP address. 12 Network Action Procedure 1. No action is necessary. The correct IP addresses are displayed in the IP Configuration section. Cannot disable an interface from a previously bonded configuration Symptom When a network bond is deleted, a subnet conflict occurs that prevents you from disabling one of the interfaces. Cause 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. Action Procedure 1. 1. 2. 3. 4. 5. 6. 7. 8. To disable the interface: On the StoreVirtual menu, select Storage Controllers. On the navigation pane, select the storage controller and navigate to Storage Controllers > Network . Click Actions > Edit TCP/IP. In the General section, select the interface you want to disable. 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. Click Actions > Edit TCP/IP. Select the interface again, and change the Interface box to Disabled, and then click OK. Modifying certain network settings may cause interface to become unavailable temporarily Symptom A network interface will become unavailable when it is being modified. Data may become unavailable while the interface comes back online. Cause Changing, adding, or removing any of the following configurations will cause the interface to become unavailable: • • • IP address Subnet mask Gateway Action Procedure 1. Schedule such modifications when bringing the interface down will be the least disruptive. 2. To avoid the interface shutdown, do not make the described modifications. Cannot disable an interface from a previously bonded configuration 13 RAID RAID array remains degraded after hot spares rebuild Symptom After a disk drive fails and the disk drive designated as the hot spare is rebuilt, RAID remains in a degraded state. Cause The RAID configuration remains degraded until the failed drives are replaced and the new drives rebuild. Action Procedure 1. 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 Symptom 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. Action Procedure 1. You can ignore the incorrect drive count in the SVMC. When you replace the missing disk drive, the drive count returns to normal. Remote Copy Remote Copy fails when the remote volume has # in the name Symptom A remote volume with a # character in the name causes the remote copy operation to fail. Cause An issue with the LeftHand OS removes the character from the name. Action Procedure 1. Do not create remote volumes or snapshots with the # character in the name. Using the CLI to create a remote snapshot fails 14 RAID Symptom 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. Action Procedure 1. 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 ( ). 3. Recreate the association by entering the information in the Edit Remote Association dialog. 4. Click OK to finish. Reporting Inconsistent reporting of storage pool utilization Symptom Storage pool capacity percentages in the SVMC may differ from the capacity reported in the events and alarms views. Cause While the LeftHand OS performs more precise capacity calculations, those values are not reflected in the storage pool utilization report in the SVMC. Action Procedure 1. 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 SNMP OID values missing from MIB files Symptom 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 Reporting 15 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 Cause Updated SNMP OIDs will be available in a later release. Action Procedure 1. To obtain the desired information, use the REST API or the SVMC. Storage controller Servicing controller incorrectly presented in the SVMC Symptom A RAID device is owned by only one controller in the storage system. This servicing controller may be incorrectly presented in the SVMC. Cause The misreporting of the servicing controller can happen if all three following conditions are met: • • • 16 RAID has been configured A management group has not been created yet One of the storage controllers fails Storage controller Action Procedure 1. You can ignore the information; the system will work as designed. The issue corrects itself once the failed controller is replaced. Powering off the storage controller in the SVMC is disabled Symptom In the Actions menu for a storage controller, the Power off or Reboot menu item only enables the Reboot option. Action Procedure 1. 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. Failing over the storage controller with the VIP causes the VIP to go offline Symptom 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. Action Procedure 1. 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 holds the VIP, continue with the following steps. b. 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 Actions > 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. Restore peer operation is reported as not complete Powering off the storage controller in the SVMC is disabled 17 Symptom When doing a restore peer operation, the progress bar reports some percentage complete, and then changes to 0% complete. Cause The task does complete, but the task bar in the SVMC incorrectly reports the task as not complete. Action Procedure 1. 2. 3. 4. Refresh the SVMC browser. On the StoreVirtual menu, select Storage Systems. On the Overview section, review the status of the storage controllers. If necessary, try the Restore Peer process again. Storage system Storage system report lists versions for all software and firmware components [informational] Symptom Software and firmware versions for the StoreVirtual 3200 Storage are displayed in the storage system report. Cause The storage system report captures details about the hardware and software components of the storage system. Action Procedure 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 Symptom Downloading a support bundle takes a long time to complete and the system seems unresponsive. Cause This issue can occur during a heavy workload. Action Procedure 1. 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 18 Storage system Symptom 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. Cause This issue is caused by a reporting anomaly. Action Procedure 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 Symptom 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. Action Procedure 1. Ensure that the system clock of the StoreVirtual 3200 Storage system is set to a date before January 19, 2038. This issue will be fixed in a future release. Storage status displays Not Responding Symptom During a reboot of the SCVMM server, the provider status displays Not Responding in the SCVMM console. Action Procedure • • • • 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 Symptom 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. Hardware monitoring and SAS cable checking require the system clock setting before January 19, 2038 19 Cause The StoreVirtual 3200 Storage system does not support Windows Server Manager. Action Procedure 1. Mount the volume to the Windows host using SCVMM. Resolve critical alarms during an upgrade Symptom During an update, a critical alarm may occur. A critical alarm stops the upgrade. Action Procedure • • • 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 on page 5. Using the SOCKS proxy, the SVMC cannot connect to the Software Updates site Symptom 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 " https://downloads.hpe.com/pub/StoreVirtual/SVMC/". The error returned was: --2016-06-09 04:47:48—-https://downloads.hpe.com/pub/StoreVirtual/SVMC// upgrades_manifest.xml Action Procedure 1. 1. 2. 3. 4. 5. If possible, use the HTTP proxy type. If you must use the SOCKS proxy type, perform the following steps: Download the site bundle from the Hewlett Packard Enterprise download site. Create an internal FTP site or an NFS share. Extract the contents of the site bundle to the internal FTP site or NFS share. In the SVMC, edit the Updates location by navigating to Settings > Updates > Edit. From the Source of update files drop-down list, select the internal FTP site or NFS share. Update while in Support Mode fails Symptom In the Tasks view, the task detail contains the following error message: 20 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’ Cause RAID is in a degraded state. Action Procedure 1. Review the health status and event information for details about the degraded RAID. 2. Resolve the degraded RAID issues and try the update again. SVMC browser session lost during an online update Symptom If the storage controllers are rebooted during an online update, the SVMC browser session is logged out when the controller the user is logged in to is rebooted. Action Procedure 1. Log back in to the SVMC to continue viewing the update progress. Support contacts • • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:http://www.hpe.com/ assistance Receive support alerts announcing product support communications, driver updates, software releases, firmware updates, and customer replaceable component information, in your email by signing up at:http:// www.hpe.com/support/e-updates Related information The latest StoreVirtual documentation is available at: • • HPESC: http://www.hpe.com/info/StoreVirtual3200Manuals Storage Information Library: http://www.hpe.com/info/storage/docs 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 ([email protected]). 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. SVMC browser session lost during an online update 21