Skip to content

Commit 0d3b092

Browse files
alkohlialkohli
committed
More changes
1 parent 820c0c2 commit 0d3b092

File tree

1 file changed

+0
-124
lines changed

1 file changed

+0
-124
lines changed

‎azure-stack/hci/update/update-via-powershell-23h2.md

Lines changed: 0 additions & 124 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,6 @@ When you apply a solution update, here are the high-level steps that you take:
3131
1. Make sure that all the prerequisites are completed.
3232
1. Identify the software version running on your cluster.
3333
1. Connect to your Azure Stack HCI cluster via remote PowerShell.
34-
<!--1. Use the [Environment Checker](../manage/use-environment-checker.md?tabs=connectivity) to verify that your cluster is in good health.-->
3534
1. Discover the updates that are available and filter the ones that you can apply to your cluster.
3635
1. Download the updates, assess the update readiness of your cluster and once ready, install the updates on your cluster. Track the progress of the updates. If needed, you can also monitor the detailed progress.
3736
1. Verify the version of the updates installed.
@@ -116,129 +115,6 @@ Before you discover the updates, make sure that the cluster was deployed using t
116115
117116
3. Make a note of the `StampVersion` on your cluster. The stamp version reflects the solution version that your cluster is running.
118117
119-
<!--## Step 2: Optionally validate system health
120-
121-
Before you discover the updates, you can manually validate the system health. This step is optional as the orchestrator always assesses update readiness prior to applying updates.
122-
123-
> [!NOTE]
124-
> Any faults that have a severity of *critical* will block the updates from being applied.
125-
126-
1. Connect to a server on your Azure Stack HCI cluster using the deployment user account.
127-
2. Run the following command to validate system health via the [Environment Checker](../manage/use-environment-checker.md).
128-
129-
```powershell
130-
$result = Test-EnvironmentReadiness
131-
$result | ft Name,Status,Severity
132-
```
133-
134-
Here's a sample output:
135-
136-
```console
137-
PS C:\Users\lcmuser> whoami
138-
rq2205\lcmuser
139-
PS C:\Users\lcmuser> $result=Test-EnvironmentReadiness
140-
VERBOSE: Looking up shared vhd product drive letter.
141-
WARNING: Unable to find volume with label Deployment
142-
VERBOSE: Get-Package returned with Success:True
143-
VERBOSE: Found package Microsoft.AzureStack.Solution.Deploy.EnterpriseCloudEngine.Client.Deployment with version 10.2303.0.31 at C:\NugetStore\Microsoft.AzureStack.Solution.Deploy.EnterpriseCloudEngine.Client.Deployment.10.2303.0.31\Microsoft.Azure Stack.Solution.Deploy.EnterpriseCloudEngine.Client.Deployment.nuspec.
144-
03/29/2023 15:45:58 : Launching StoragePools
145-
03/29/2023 15:45:58 : Launching StoragePhysicalDisks
146-
03/29/2023 15:45:58 : Launching StorageMapping
147-
03/29/2023 15:45:58 : Launching StorageSubSystems
148-
03/29/2023 15:45:58 : Launching TestCauSetup
149-
03/29/2023 15:45:58 : Launching StorageVolumes
150-
03/29/2023 15:45:58 : Launching StorageVirtualDisks
151-
03/29/2023 15:46:05 : Launching OneNodeEnvironment
152-
03/29/2023 15:46:05 : Launching NonMigratableWorkload
153-
03/29/2023 15:46:05 : Launching FaultSummary
154-
03/29/2023 15:46:06 : Launching SBEHealthStatusOnNode
155-
03/29/2023 15:46:06 : Launching StorageJobStatus
156-
03/29/2023 15:46:07 : Launching StorageCsv
157-
WARNING: There aren't any faults right now.
158-
03/29/2023 15:46:09 : Launching SBEPrecheckStatus
159-
WARNING: rq2205-cl: There aren't any faults right now.
160-
VERBOSE: Looking up shared vhd product drive letter.
161-
WARNING: Unable to find volume with label Deployment
162-
VERBOSE: Get-Package returned with Success:True
163-
VERBOSE: Found package Microsoft.AzureStack.Role.SBE with version 4.0.2303.66 at
164-
C:\NugetStore\Microsoft.AzureStack.Role.SBE.4.0.2303.66\Microsoft.AzureStack.Role.SBE.nuspec.
165-
VERBOSE: SolutionExtension module supports Tag 'HealthServiceIntegration'.
166-
VERBOSE: SolutionExtension module SolutionExtension at
167-
C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\CloudMedia\SBE\Installed\Content\Configuration\SolutionExtension is valid.
168-
VERBOSE: Looking up shared vhd product drive letter.
169-
WARNING: Unable to find volume with label Deployment
170-
VERBOSE: Get-Package returned with Success:True
171-
VERBOSE: Found package Microsoft.AzureStack.Role.SBE with version 4.0.2303.66 at
172-
C:\NugetStore\Microsoft.AzureStack.Role.SBE.4.0.2303.66\Microsoft.AzureStack.Role.SBE.nuspec.
173-
VERBOSE: SolutionExtension module supports Tag 'HealthServiceIntegration'.
174-
VERBOSE: SolutionExtension module SolutionExtension at
175-
C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\CloudMedia\SBE\Installed\Content\Configuration\SolutionExtension is valid.
176-
PS C:\Users\lcmuser> $result|ft Name,Status,Severity
177-
178-
Name Status Severity
179-
---- ------ --------
180-
Storage Pool Summary SUCCESS CRITICAL
181-
Storage Services Physical Disks Summary SUCCESS CRITICAL
182-
Storage Services Physical Disks Summary SUCCESS CRITICAL
183-
Storage Services Physical Disks Summary SUCCESS CRITICAL
184-
Storage Services Physical Disks Summary SUCCESS CRITICAL
185-
Storage Services Physical Disks Summary SUCCESS CRITICAL
186-
Storage Services Physical Disks Summary SUCCESS CRITICAL
187-
Storage Services Physical Disks Summary SUCCESS CRITICAL
188-
Storage Services Physical Disks Summary SUCCESS CRITICAL
189-
Storage Services Physical Disks Summary SUCCESS CRITICAL
190-
Storage Services Physical Disks Summary SUCCESS CRITICAL
191-
Storage Services Physical Disks Summary SUCCESS CRITICAL
192-
Storage Services Physical Disks Summary SUCCESS CRITICAL
193-
Storage Services Physical Disks Summary SUCCESS CRITICAL
194-
Storage Services Physical Disks Summary SUCCESS CRITICAL
195-
Storage Services Physical Disks Summary SUCCESS CRITICAL
196-
Storage Services Physical Disks Summary SUCCESS CRITICAL
197-
Storage Services Physical Disks Summary SUCCESS CRITICAL
198-
Storage Services Physical Disks Summary SUCCESS CRITICAL
199-
Storage Services Physical Disks Summary SUCCESS CRITICAL
200-
Storage Services Physical Disks Summary SUCCESS CRITICAL
201-
Storage Services Summary SUCCESS CRITICAL
202-
Storage Services Summary SUCCESS CRITICAL
203-
Storage Services Summary SUCCESS CRITICAL
204-
Storage Subsystem Summary SUCCESS CRITICAL
205-
Test-CauSetup SUCCESS INFORMATIONAL
206-
Test-CauSetup SUCCESS INFORMATIONAL
207-
Test-CauSetup SUCCESS INFORMATIONAL
208-
Test-CauSetup SUCCESS INFORMATIONAL
209-
Test-CauSetup SUCCESS CRITICAL
210-
Test-CauSetup SUCCESS INFORMATIONAL
211-
Test-CauSetup SUCCESS INFORMATIONAL
212-
Test-CauSetup SUCCESS INFORMATIONAL
213-
Test-CauSetup FAILURE INFORMATIONAL
214-
Test-CauSetup FAILURE INFORMATIONAL
215-
Test-CauSetup FAILURE INFORMATIONAL
216-
Storage Volume Summary SUCCESS CRITICAL
217-
Storage Volume Summary SUCCESS CRITICAL
218-
Storage Volume Summary SUCCESS CRITICAL
219-
Storage Volume Summary SUCCESS CRITICAL
220-
Storage Virtual Disk Summary SUCCESS CRITICAL
221-
Storage Virtual Disk Summary SUCCESS CRITICAL
222-
Storage Virtual Disk Summary SUCCESS CRITICAL
223-
Storage Virtual Disk Summary SUCCESS CRITICAL
224-
Get-OneNodeRebootRequired SUCCESS WARNING
225-
Test-NonMigratableVMs SUCCESS WARNING
226-
Faults SUCCESS INFORMATIONAL
227-
Test-SBEHealthStatusOnNode Success Informational
228-
Test-SBEHealthStatusOnNode Success Informational
229-
Storage Job Summary SUCCESS CRITICAL
230-
Storage Cluster Shared Volume Summary SUCCESS CRITICAL
231-
Storage Cluster Shared Volume Summary SUCCESS CRITICAL
232-
Storage Cluster Shared Volume Summary SUCCESS CRITICAL
233-
Test-SBEPrecheckStatus Success Informational
234-
235-
PS C:\Users\lcmuser>
236-
```
237-
238-
> [!NOTE]
239-
> In this release, the informational failures for `Test-CauSetup` are expected and will not impact the updates.
240-
241-
3. Review any failures and resolve them before you proceed to the discovery step.-->
242118
243119
## Step 2: Discover the updates
244120

0 commit comments

Comments
 (0)