Skip to content

Commit fa9956b

Browse files
committed
update commands
1 parent 083c381 commit fa9956b

File tree

1 file changed

+16
-10
lines changed

1 file changed

+16
-10
lines changed

azure-local/manage/support-tools.md

Lines changed: 16 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,9 @@ If you already have the module installed, you can update using the following cmd
5353
Update-Module -Name Microsoft.AzureStack.HCI.CSSTools
5454
```
5555

56+
> [!NOTE]
57+
> When you import the module, it will attempt to automatically update from PowerShell Gallery. You can also update manually using methods below.
58+
5659
Ensure that you have the latest module loaded into the current runspace by removing and importing the module.
5760
```powershell
5861
Remove-Module -Name Microsoft.AzureStack.HCI.CSSTools
@@ -71,15 +74,15 @@ Get-Command -Module Microsoft.AzureStack.HCI.CSSTools
7174

7275

7376
### Perform diagnostic checks
74-
To list all available diagnostic checks, run the following command:
77+
You can perform a diagnostic health check against the system to help detect common issues. The following components are available:
78+
- BaseSystem
79+
- Registration
7580

7681

7782
```powershell
78-
Invoke-AzsSupportDiagnosticCheck –ProductName <BaseSystem, Registration>
83+
Invoke-AzsSupportDiagnosticCheck -Component <Component>
7984
```
8085

81-
Run all diagnostic checks by pressing `CTRL+SPACE` after the parameter `ProductName`.
82-
8386

8487
### Collect data for support
8588
To collect data using one of our pre-defined collection sets, run the following command:
@@ -109,7 +112,6 @@ New-AzsSupportDataBundle -ClusterCommands $clusterCommands `
109112
```
110113

111114
## Example scenarios
112-
113115
To troubleshoot Azure Local, run the following commands:
114116

115117
### For deployment issues
@@ -127,18 +129,22 @@ Get-AzsSupportEceUpdateDetails
127129
```
128130

129131
### For storage issues
130-
Refer to TODO.
132+
```powershell
133+
Start-AzsSupportStorageDiagnostic
134+
```
135+
136+
For full guidance on troubleshooting storage related issues, refer to [Troubleshooting-Storage-With-Support-Diagnostics-Tool](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Storage/Troubleshooting-Storage-With-Support-Diagnostics-Tool.md).
131137

132138
### For registration issues
133139

134140
```powershell
135-
Invoke-AzsSupportDiagnosticCheck -ProductName Registration
141+
Invoke-AzsSupportDiagnosticCheck -Component Registration
136142
```
137143

138144
Here's an example of output for a registration issue:
139145

140146
```output
141-
PS C:\temp> Invoke-AzsSupportDiagnosticCheck -ProductName Registration
147+
PS C:\temp> Invoke-AzsSupportDiagnosticCheck -Component Registration
142148
Starting known issue check for Azure Stack HCI: Registration.
143149
Starting Azure Stack HCI base system validation.
144150
Gathering information from all clustered nodes.
@@ -192,13 +198,13 @@ Data collection done . Please upload the file to the Microsoft Workspace.
192198
### For base Azure Local system issues
193199

194200
```powershell
195-
Invoke-AzsSupportDiagnosticCheck -ProductName BaseSystem
201+
Invoke-AzsSupportDiagnosticCheck -Component BaseSystem
196202
```
197203

198204
Here's an example of the output for base system issues:
199205

200206
```output
201-
PS C:\temp> Invoke-AzsSupportDiagnosticCheck -ProductName BaseSystem
207+
PS C:\temp> Invoke-AzsSupportDiagnosticCheck -Component BaseSystem
202208
Starting known issue check for Azure Stack HCI: BaseSystem.
203209
Gathering information from all clustered nodes.
204210
We are preparing to collect diagnostic information from your environment

0 commit comments

Comments
 (0)