SBE package update using PowerShell

Do the following steps to perform an offline solution update.

Create a directory on a CSV (cluster shared volume) that is accessible by all cluster nodes.
For example: C:\ClusterStorage\Infrastructure_1\SBE\Bundle_SBE_Dell_AS-HCI-AX_4.1.2405.2001.
Note: To prevent any failures, it is crucial to use unique folder names for each SBE package.
Download the SBE package and extract the latest SBE bundle .zip file.
To download the SBE package, do the following:
1. On the Dell Technologies Support page, scroll down and select Browse All Products > Infrastructure > Converged Infrastructure > Hyper-converged Systems > AX Nodes, and select the AX node for your system. When you click Select This Product, the AX node product page appears.
  
  Figure 31. Download the SBE package
2. Go to Drivers & Downloads.

Extract the contents from the SBE package zip file and copy them to the directory created in Step 1. The contents of this directory should look like this:

The following command shows the files directly extracted into the C:\ClusterStorage\Infrastructure_1\SBE\Bundle_SBE_Dell_AS-HCI-AX_4.1.2405.2001 directory.

Get-ChildItem -Path C:\ClusterStorage\Infrastructure_1\SBE\Bundle_SBE_Dell_AS-HCI-AX_4.1.2405.2001
Mode   LastWriteTime Length ` Name
----   ------------- ------ ----
-a---- 4/1/2024 7:28 AM 32008 Bundle_SBE_Dell_AS-HCI-AX_4.1.2405.2001.xml
-a---- 4/1/2024 7:27 AM 739058535 Bundle_SBE_Dell_AS-HCI-AX_4.1.2405.2001.zip
-a---- 4/1/2024 7:28 AM 4188 SBE_Discovery_Dell.xml

Load the SBE package update by running the following command on one of the cluster nodes:

Add-SolutionUpdate -SourceFolder C:\ClusterStorage\Infrastructure_1\SBE\SBE-AX-4.1.2405.2001

Check the state of the SBE package, it should be Ready.

Figure 32. SBE package status
Run health-check to ensure that critical severity tests have the Success status. You can use the following commands to run the health-check:
```
$result = Test-EnvironmentReadiness
$result | ft Name,Status,Severity
```
You can use the following command to show all tests that do not have the Success status and do not have the Informational severity level.
```
$result | Where-Object {($_.Status -ne "SUCCESS" -and $_.Severity -ne "INFORMATIONAL")}
```

Run the following command to start SBE package installation. This command returns the action plan ID.

Get-SolutionUpdate | Where-Object {$_.State -eq "Ready" -and $_.PackageType -eq "SBE"} | Start-SolutionUpdate

You can get the SBE package installation progress by using the output of the above command. Run the following command:

$ResourceID = “<enter the resourceID generated by Start-SolutionUpdate”
Get-SolutionUpdate -Id $ResourceID

Alternatively, you can run the following command to get the installation progress:

Get-SolutionUpdate | Where-Object PackageType -EQ "SBE" | Format-List ResourceID, Description, State, SBEVersion, UpdateStateProperties, HealthState

Figure 33. SBE package installation progress

You can also monitor the solution update using the following commands:

#Replace SolutionUpdateID with the Resource ID generated by Get-SolutionUpdate

$SolutionUpdateId = "redmond/SBE4.0.2402.2501"
 
$ResourceID = Get-SolutionUpdate -Id $SolutionUpdateId | Get-SolutionUpdateRun | Select-Object ResourceID
  
$ActionPlanInstanceID = ($ResourceID -split "/" -replace "}","")[2]
 
Start-MonitoringActionplanInstanceToComplete -actionPlanInstanceID  $ActionPlanInstanceID

Perform the following steps for an online solution update:

Ensure that your cluster has good Internet connectivity.
Run the following command to verify that the solution update is discovered update service:
```
Get-SolutionUpdate | ft DisplayName, State
```
Run the following command to install the solution update:
```
Get-SolutionUpdate | Start-SolutionUpdate
```

Your Browser is Out of Date

SBE package update using PowerShell