Skip to content

Commit 10a98d9

Browse files
committed
udpated text
1 parent 78a880c commit 10a98d9

File tree

1 file changed

+24
-5
lines changed

1 file changed

+24
-5
lines changed

azure-stack/hci/manage/suspend-resume-cluster-maintenance.md

Lines changed: 24 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ To suspend a cluster node follow these steps:
4444
> [!NOTE]
4545
> Running this command may take some time, depending on the number of VMs that need to be migrated.
4646
47-
1. Confirm that the node is successfully suspended
47+
1. Then, to confirm that the node is successfully suspended, run this command.
4848
4949
```powershell
5050
Get-clusternode
@@ -61,7 +61,7 @@ To suspend a cluster node follow these steps:
6161
ASRRlS3lRl5Ull Paused Node
6262
```
6363
64-
1. Remove the node from the active Arc VM Configuration to ensure that no new VMs are placed on the node. **This step can only be done using PowerShell**.
64+
1. Next, remove the node from the active Arc VM Configuration to ensure that no new VMs are placed on the node. **This step can only be done using PowerShell**.
6565
6666
```powershell
6767
Remove-MocPhysicalNode -nodeName “MachineName”
@@ -93,7 +93,7 @@ To resume a cluster node follow these steps:
9393
> [!NOTE]
9494
> Running this command may take some time, depending on the number of VMs that need to be migrated.
9595
96-
1. Confirm that the node is successfully resumed
96+
1. Then, to confirm that the node is successfully resumed, run this command:
9797
9898
```powershell
9999
Get-clusternode
@@ -110,8 +110,27 @@ To resume a cluster node follow these steps:
110110
ASRRlS3lRl5Ull Paused Node
111111
```
112112
113-
1. Add the node to the active Arc VM Configuration. **This step can only be done using PowerShell**.
113+
1. Next, add the node to the active Arc VM Configuration. **This step can only be done using PowerShell**.
114114
115115
```powershell
116116
Remove-MocPhysicalNode -nodeName “MachineName”
117-
```
117+
```
118+
119+
1. Verify that your storage pool is healthy. Run this command:
120+
121+
```powershell
122+
Get-Storagepool -friendlyname “SU_Pool1”
123+
```
124+
125+
Here's example output:
126+
127+
```console
128+
PS C : \programdata\wssdagent> get-storagepool -FriendlyName "SU1_Pool"
129+
130+
FriendlyName Operationalstatus HealthStatus IsPrimordial IsReadOnly Size AllocatedSize
131+
------------ ----------------- ------------ ------------ ---------- ---- -------------
132+
SUl_Pool OK Healthy False False 131.28 TB 1.8S TB
133+
```
134+
135+
> [!NOTE]
136+
> If the pool is not reported as healthy, check the status of the storage repair jobs using the `get-storagejob command`.

0 commit comments

Comments
 (0)