Install Update 4 on your StorSimple device
Caution
ACTION REQUIRED: StorSimple Data Manager, StorSimple Device Manager, StorSimple 1200, and StorSimple 8000 have reached their end of support. End of support details were published in 2019 on the Microsoft Lifecycle Policy and Azure Communications pages. Additional notifications were also sent via email and posted on the Azure portal and StorSimple documentation site. Contact Microsoft Support for additional details.
Overview
This tutorial explains how to install Update 4 on a StorSimple device running an earlier software version via the Azure portal and using the hotfix method. The hotfix method is used when a gateway is configured on a network interface other than DATA 0 of the StorSimple device and you are trying to update from a pre-Update 1 software version.
Update 4 includes device software, USM firmware, LSI driver and firmware, Storport and Spaceport, OS security updates, and a host of other OS updates. The device software, USM firmware, Spaceport, Storport, and other OS updates are non-disruptive updates. The non-disruptive or regular updates can be applied via the Azure portal or via the hotfix method. The disk firmware updates are disruptive updates and can only be applied via the hotfix method using the Windows PowerShell interface of the device.
Important
- A set of manual and automatic pre-checks are done prior to the install to determine the device health in terms of hardware state and network connectivity. These pre-checks are performed only if you apply the updates from the Azure portal.
- We recommend that you install the software and other regular updates via the Azure portal. You should only go to the Windows PowerShell interface of the device (to install updates) if the pre-update gateway check fails in the portal. Depending upon the version you are updating from, the updates may take 4 hours (or greater) to install. The maintenance mode updates must also be installed via the Windows PowerShell interface of the device. As maintenance mode updates are disruptive updates, these will result in a down time for your device.
- If running the optional StorSimple Snapshot Manager, ensure that you have upgraded your Snapshot Manager version to Update 4 prior to updating the device.
Preparing for updates
You will need to perform the following steps before you scan and apply the update:
Take a cloud snapshot of the device data.
Ensure that your controller fixed IPs are routable and can connect to the Internet. These fixed IPs will be used to service updates to your device. You can test this by running the following cmdlet on each controller from the Windows PowerShell interface of the device:
Test-Connection -Source <Fixed IP of your device controller> -Destination <Any IP or computer name outside of datacenter network>Sample output for Test-Connection when fixed IPs can connect to the Internet
Controller0>Test-Connection -Source 10.126.173.91 -Destination bing.com Source Destination IPV4Address IPV6Address ----------------- ----------- ----------- HCSNODE0 bing.com 204.79.197.200 HCSNODE0 bing.com 204.79.197.200 HCSNODE0 bing.com 204.79.197.200 HCSNODE0 bing.com 204.79.197.200 Controller0>Test-Connection -Source 10.126.173.91 -Destination 204.79.197.200 Source Destination IPV4Address IPV6Address ----------------- ----------- ----------- HCSNODE0 204.79.197.200 204.79.197.200 HCSNODE0 204.79.197.200 204.79.197.200 HCSNODE0 204.79.197.200 204.79.197.200 HCSNODE0 204.79.197.200 204.79.197.200
After you have successfully completed these manual pre-checks, you can proceed to scan and install the updates.
Install Update 4 via the Azure portal
Perform the following steps to update your device to Update 4.
Note
Microsoft pulls additional diagnostic information from the device. As a result, when our operations team identifies devices that are having problems, we are better equipped to collect information from the device and diagnose issues.
To install an update from the Azure portal
On the StorSimple service page, select your device.
Navigate to Device settings > Device updates.
A notification appears if new updates are available. Alternatively, in the Device updates blade, click Scan Updates. A job is created to scan for available updates. You are notified when the job completes successfully.
We recommend that you review the release notes before you apply an update on your device. To apply updates, click Install updates. In the Confirm regular updates blade, review the prerequisites to complete before you apply updates. Select the checkbox to indicate that you are ready to update the device and then click Install.
A set of prerequisite checks starts. These checks include:
Controller health checks to verify that both the device controllers are healthy and online.
Hardware component health checks to verify that all the hardware components on your StorSimple device are healthy.
DATA 0 checks to verify that DATA 0 is enabled on your device. If this interface is not enabled, you must enable it and then retry.
The update is downloaded and installed only if all the checks are successfully completed. You are notified when the checks are in progress. If the prechecks fail, then you will be provided with the reasons for failure. Address those issues and then retry the operation. You may need to contact Microsoft Support if you cannot address these issues by yourself.
After the prechecks are successfully completed, an update job is created. You are notified when the update job is successfully created.
The update is then applied on your device.
The update takes a few hours to complete. Select the update job and click Details to view the details of the job at any time.
You can also monitor the progress of the update job from Device settings > Jobs. On the Jobs blade, you can see the update progress.
After the job is complete, navigate to the Device settings > Device updates. The software version should now be updated.
Verify that your device is running StorSimple 8000 Series Update 4 (6.3.9600.17820). The Last updated date should also be modified.
You will now see that the Maintenance mode updates are available (this message might continue to be displayed for up to 24 hours after you install the updates). Maintenance mode updates are disruptive updates that result in device downtime and can only be applied via the Windows PowerShell interface of your device.
Download the maintenance mode updates by using the steps listed in to download hotfixes to search for and download KB4011837, which installs disk firmware updates (the other updates should already be installed by now). Follow the steps listed in install and verify maintenance mode hotfixes to install the maintenance mode updates.
Install Update 4 as a hotfix
The recommended method to install Update 4 is via the Azure portal.
Use this procedure if you fail the gateway check when trying to install the updates through the Azure portal. The check fails as you have a gateway assigned to a non-DATA 0 network interface and your device is running a software version prior to Update 1.
The software versions that can be upgraded using the hotfix method are:
- Update 0.1, 0.2, 0.3
- Update 1, 1.1, 1.2
- Update 2, 2.1, 2.2
- Update 3, 3.1
The hotfix method involves the following three steps:
- Download the hotfixes from the Microsoft Update Catalog.
- Install and verify the regular mode hotfixes.
- Install and verify the maintenance mode hotfix.
Download updates for your device
You must download and install the following hotfixes in the prescribed order and the suggested folders:
| Order | KB | Description | Update type | Install time | Install in folder |
|---|---|---|---|---|---|
| 1. | KB4011839 | Software update | Regular Non-disruptive |
~ 25 mins | FirstOrderUpdate |
| 2A. | KB4011841 KB4011842 |
LSI driver and firmware updates USM firmware update (version 3.38) |
Regular Non-disruptive |
~ 3 hrs (includes 2A. + 2B. + 2C.) |
SecondOrderUpdate |
| 2B. | KB3139398, KB3108381 KB3205400, KB3142030 KB3197873, KB3197873 KB3192392, KB3153704 KB3174644, KB3139914 |
OS security updates package Download Windows Server 2012 R2 |
Regular Non-disruptive |
- | SecondOrderUpdate |
| 2C. | KB3210083, KB3103616 KB3146621, KB3121261 KB3123538 |
OS updates package Download Windows Server 2012 R2 |
Regular Non-disruptive |
- | SecondOrderUpdate |
You may also need to install disk firmware updates on top of all the updates shown in the preceding tables. You can verify whether you need the disk firmware updates by running the Get-HcsFirmwareVersion cmdlet. If you are running these firmware versions: XMGJ, XGEG, KZ50, F6C2, VR08, N002, 0106, then you do not need to install these updates.
| Order | KB | Description | Update type | Install time | Install in folder |
|---|---|---|---|---|---|
| 3. | KB3121899 | Disk firmware | Maintenance Disruptive |
~ 30 mins | ThirdOrderUpdate |
Important
- This procedure needs to be performed only once to apply Update 4. You can use the Azure portal to apply subsequent updates.
- If updating from Update 3 or 3.1, the total install time is close to 4 hours.
- Before using this procedure to apply the update, make sure that both the device controllers are online and all the hardware components are healthy.
Perform the following steps to download and install the hotfixes.
To download hotfixes
Perform the following steps to download the software update from the Microsoft Update Catalog.
Start Internet Explorer and navigate to http://catalog.update.microsoft.com.
If this is your first time using the Microsoft Update Catalog on this computer, click Install when prompted to install the Microsoft Update Catalog add-on.
In the search box of the Microsoft Update Catalog, enter the Knowledge Base (KB) number of the hotfix you want to download, for example 4011839, and then click Search.
The hotfix listing appears, for example, Cumulative Software Bundle Update 4.0 for StorSimple 8000 Series.
Click Download. Specify or Browse to a local location where you want the downloads to appear. Click the files to download to the specified location and folder. The folder can also be copied to a network share that is reachable from the device.
Search for any additional hotfixes listed in the table above (4011841), and download the corresponding files to the specific folders as listed in the preceding table.
Note
The hotfixes must be accessible from both controllers to detect any potential error messages from the peer controller.
The hotfixes must be copied in 3 separate folders. For example, the device software/Cis/MDS agent update can be copied in FirstOrderUpdate folder, all the other non-disruptive updates could be copied in the SecondOrderUpdate folder, and maintenance mode updates copied in ThirdOrderUpdate folder.
To install and verify regular mode hotfixes
Perform the following steps to install and verify regular-mode hotfixes. If you already installed them using the Azure classic portal, skip ahead to install and verify maintenance mode hotfixes.
To install the hotfixes, access the Windows PowerShell interface on your StorSimple device serial console. Follow the detailed instructions in Use PuTTy to connect to the serial console. At the command prompt, press Enter.
Select option 1, Log in with full access. We recommend that you install the hotfix on the passive controller first.
To install the hotfix, at the command prompt, type:
Start-HcsHotfix -Path <path to update file> -Credential <credentials in domain\username format>Use IP rather than DNS in share path in the above command. The credential parameter is used only if you are accessing an authenticated share.
We recommend that you use the credential parameter to access shares. Even shares that are open to “everyone” are typically not open to unauthenticated users.
Supply the password when prompted.
A sample output for installing the first order updates is shown below. For the first order update, you need to point to the specific file.
Controller0>Start-HcsHotfix -Path \\10.100.100.100\share \FirstOrderUpdate\HcsSoftwareUpdate.exe -Credential contoso\John Confirm This operation starts the hotfix installation and could reboot one or both of the controllers. If the device is serving I/Os, these will not be disrupted. Are you sure you want to continue? [Y] Yes [N] No [?] Help (default is "Y"): YType Y when prompted to confirm the hotfix installation.
Monitor the update by using the
Get-HcsUpdateStatuscmdlet. The update will first complete on the passive controller. Once the passive controller is updated, there will be a failover and the update will then get applied on the other controller. The update is complete when both the controllers are updated.The following sample output shows the update in progress. The
RunInprogresswill beTruewhen the update is in progress.Controller0>Get-HcsUpdateStatus RunInprogress : True LastHotfixTimestamp : LastUpdateTimestamp : 02/03/2017 2:04:02 AM Controller0Events : Controller1Events :The following sample output indicates that the update is finished. The
RunInProgresswill beFalsewhen the update has completed.Controller0>Get-HcsUpdateStatus RunInprogress : False LastHotfixTimestamp : 02/03/2017 9:15:55 AM LastUpdateTimestamp : 02/03/2017 9:06:07 AM Controller0Events : Controller1Events :Note
Occasionally, the cmdlet reports
Falsewhen the update is still in progress. To ensure that the hotfix is complete, wait for a few minutes, rerun this command and verify that theRunInProgressisFalse. If it is, then the hotfix has completed.After the software update is complete, verify the system software versions. Type:
Get-HcsSystemYou should see the following versions:
FriendlySoftwareVersion: StorSimple 8000 Series Update 4.0HcsSoftwareVersion: 6.3.9600.17820If the version number does not change after applying the update, it indicates that the hotfix has failed to apply. Should you see this, please contact Microsoft Support for further assistance.
Important
You must restart the active controller via the
Restart-HcsControllercmdlet before applying the next update.
Repeat steps 3-5 to install the Cis/MDS agent downloaded to your FirstOrderUpdate folder.
Repeat steps 3-5 to install the second order updates. For second order updates, multiple updates can be installed by just running the
Start-HcsHotfix cmdletand pointing to the folder where second order updates are located. The cmdlet will execute all the updates available in the folder. If an update is already installed, the update logic will detect that and not apply that update.
After all the hotfixes are installed, use the Get-HcsSystem cmdlet. The versions should be:
CisAgentVersion: 1.0.9441.0MdsAgentVersion: 35.2.2.0Lsisas2Version: 2.0.78.00
To install and verify maintenance mode hotfixes
Use KB4011837 to install disk firmware updates. These are disruptive updates and take around 30 minutes to complete. You can choose to install these in a planned maintenance window by connecting to the device serial console.
Note that if your disk firmware is already up-to-date, you won't need to install these updates. Run the Get-HcsUpdateAvailability cmdlet from the device serial console to check if updates are available and whether the updates are disruptive (maintenance mode) or non-disruptive (regular mode) updates.
To install the disk firmware updates, follow the instructions below.
Place the device in the maintenance mode. Note that you should not use Windows PowerShell remoting when connecting to a device in maintenance mode. Instead run this cmdlet on the device controller when connected through the device serial console. Type:
Enter-HcsMaintenanceModeA sample output is shown below.
Controller0>Enter-HcsMaintenanceMode Checking device state... In maintenance mode, your device will not service IOs and will be disconnected from the Microsoft Azure StorSimple Manager service. Entering maintenance mode will end the current session and reboot both controllers, which takes a few minutes to complete. Are you sure you want to enter maintenance mode? [Y] Yes [N] No (Default is "Y"): Y -----------------------MAINTENANCE MODE------------------------ Microsoft Azure StorSimple Appliance Model 8600 Name: Update4-8600-mystorsimple Copyright (C) 2014 Microsoft Corporation. All rights reserved. You are connected to Controller0 - Passive --------------------------------------------------------------- Serial Console Menu [1] Log in with full access [2] Log into peer controller with full access [3] Connect with limited access [4] Change language Please enter your choice>Both the controllers then restart into maintenance mode.
To install the disk firmware update, type:
Start-HcsHotfix -Path <path to update file> -Credential <credentials in domain\username format>A sample output is shown below.
Controller1>Start-HcsHotfix -Path \\10.100.100.100\share\ThirdOrderUpdates\ -Credential contoso\john Enter Password: WARNING: In maintenance mode, hotfixes should be installed on each controller sequentially. After the hotfix is installed on this controller, install it on the peer controller. Confirm This operation starts a hotfix installation and could reboot one or both of the controllers. By installing new updates you agree to, and accept any additional terms associated with, the new functionality listed in the release notes (https://go.microsoft.com/fwLink/?LinkID=613790). Are you sure you want to continue? [Y] Yes [N] No (Default is "Y"): Y WARNING: Installation is currently in progress. This operation can take several minutes to complete.Monitor the install progress using
Get-HcsUpdateStatuscommand. The update is complete when theRunInProgresschanges toFalse.After the installation is complete, the controller on which the maintenance mode hotfix was installed restarts. Sign in as option 1, Log in with full access, and verify the disk firmware version. Type:
Get-HcsFirmwareVersionThe expected disk firmware versions are:
XMGJ, XGEG, KZ50, F6C2, VR08, N002, 0106A sample output is shown below.
-----------------------MAINTENANCE MODE------------------------ Microsoft Azure StorSimple Appliance Model 8600 Name: Update4-8600-mystorsimple Software Version: 6.3.9600.17820 Copyright (C) 2014 Microsoft Corporation. All rights reserved. You are connected to Controller1 --------------------------------------------------------------- Controller1>Get-HcsFirmwareVersion Controller0 : TalladegaFirmware ActiveBIOS:0.45.0010 BackupBIOS:0.45.0006 MainCPLD:17.0.000b ActiveBMCRoot:2.0.001F BackupBMCRoot:2.0.001F BMCBoot:2.0.0002 LsiFirmware:20.00.04.00 LsiBios:07.37.00.00 Battery1Firmware:06.2C Battery2Firmware:06.2C DomFirmware:X231600 CanisterFirmware:3.5.0.56 CanisterBootloader:5.03 CanisterConfigCRC:0x9134777A CanisterVPDStructure:0x06 CanisterGEMCPLD:0x19 CanisterVPDCRC:0x142F7DC2 MidplaneVPDStructure:0x0C MidplaneVPDCRC:0xA6BD4F64 MidplaneCPLD:0x10 PCM1Firmware:1.00|1.05 PCM1VPDStructure:0x05 PCM1VPDCRC:0x41BEF99C PCM2Firmware:1.00|1.05 PCM2VPDStructure:0x05 PCM2VPDCRC:0x41BEF99C EbodFirmware CanisterFirmware:3.5.0.56 CanisterBootloader:5.03 CanisterConfigCRC:0xB23150F8 CanisterVPDStructure:0x06 CanisterGEMCPLD:0x14 CanisterVPDCRC:0xBAA55828 MidplaneVPDStructure:0x0C MidplaneVPDCRC:0xA6BD4F64 MidplaneCPLD:0x10 PCM1Firmware:3.11 PCM1VPDStructure:0x03 PCM1VPDCRC:0x6B58AD13 PCM2Firmware:3.11 PCM2VPDStructure:0x03 PCM2VPDCRC:0x6B58AD13 DisksFirmware SmrtStor:TXA2D20800GA6XYR:KZ50 SmrtStor:TXA2D20800GA6XYR:KZ50 SmrtStor:TXA2D20800GA6XYR:KZ50 SmrtStor:TXA2D20800GA6XYR:KZ50 SmrtStor:TXA2D20800GA6XYR:KZ50 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08 WD:WD4001FYYG-01SL3:VR08Run the
Get-HcsFirmwareVersioncommand on the second controller to verify that the software version has been updated. You can then exit the maintenance mode. To do so, type the following command for each device controller:Exit-HcsMaintenanceModeThe controllers restart when you exit maintenance mode. After the disk firmware updates are successfully applied and the device has exited maintenance mode, return to the Azure classic portal. Note that the portal might not show that you installed the maintenance mode updates for 24 hours.
Troubleshooting update failures
What if you see a notification that the pre-upgrade checks have failed?
If a pre-check fails, make sure that you have looked at the detailed notification bar at the bottom of the page. This provides guidance as to which pre-check has failed. The following illustration shows an instance in which such a notification appears. In this case, the controller health check and hardware component health check have failed. Under the Hardware Status section, you can see that both Controller 0 and Controller 1 components need attention.
You will need to make sure that both controllers are healthy and online. You will also need to make sure that all the hardware components in the StorSimple device are shown to be healthy on the Maintenance page. You can then try to install updates. If you are not able to fix the hardware component issues, then you will need to contact Microsoft Support for next steps.
What if you receive a "Could not install updates" error message, and the recommendation is to refer to the update troubleshooting guide to determine the cause of the failure?
One likely cause for this could be that you do not have connectivity to the Microsoft Update servers. This is a manual check that needs to be performed. If you lose connectivity to the update server, your update job would fail. You can check the connectivity by running the following cmdlet from the Windows PowerShell interface of your StorSimple device:
Test-Connection -Source <Fixed IP of your device controller> -Destination <Any IP or computer name outside of datacenter>
Run the cmdlet on both controllers.
If you have verified the connectivity exists, and you continue to see this issue, please contact Microsoft Support for next steps.
What if you see an update failure when updating your device to Update 4 and both the controllers are running Update 4?
Starting Update 4, if both the controllers are running the same software version and if there is an update failure, the controllers do not go into recovery mode. This situation can arise if the device software hotfix (1st order update) is applied to both the controllers successfully but other hotfixes (2nd order and 3rd order) are yet to be applied. Starting Update 4, the controllers will go into recovery mode only if the two controllers are running different software versions.
If the user sees an update failure when both controllers are running Update 4, we recommend that they wait a few minutes and then retry updating. If the retry does not succeed, then they should contact Microsoft Support.
Next steps
Learn more about the Update 4 release.
Feedback
Submit and view feedback for