@@ -53,6 +53,9 @@ If you already have the module installed, you can update using the following cmd
53
53
Update-Module -Name Microsoft.AzureStack.HCI.CSSTools
54
54
```
55
55
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
+
56
59
Ensure that you have the latest module loaded into the current runspace by removing and importing the module.
57
60
``` powershell
58
61
Remove-Module -Name Microsoft.AzureStack.HCI.CSSTools
@@ -71,15 +74,15 @@ Get-Command -Module Microsoft.AzureStack.HCI.CSSTools
71
74
72
75
73
76
### 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
75
80
76
81
77
82
``` powershell
78
- Invoke-AzsSupportDiagnosticCheck –ProductName <BaseSystem, Registration >
83
+ Invoke-AzsSupportDiagnosticCheck -Component <Component >
79
84
```
80
85
81
- Run all diagnostic checks by pressing ` CTRL+SPACE ` after the parameter ` ProductName ` .
82
-
83
86
84
87
### Collect data for support
85
88
To collect data using one of our pre-defined collection sets, run the following command:
@@ -109,7 +112,6 @@ New-AzsSupportDataBundle -ClusterCommands $clusterCommands `
109
112
```
110
113
111
114
## Example scenarios
112
-
113
115
To troubleshoot Azure Local, run the following commands:
114
116
115
117
### For deployment issues
@@ -127,18 +129,22 @@ Get-AzsSupportEceUpdateDetails
127
129
```
128
130
129
131
### 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 ) .
131
137
132
138
### For registration issues
133
139
134
140
``` powershell
135
- Invoke-AzsSupportDiagnosticCheck -ProductName Registration
141
+ Invoke-AzsSupportDiagnosticCheck -Component Registration
136
142
```
137
143
138
144
Here's an example of output for a registration issue:
139
145
140
146
``` output
141
- PS C:\temp> Invoke-AzsSupportDiagnosticCheck -ProductName Registration
147
+ PS C:\temp> Invoke-AzsSupportDiagnosticCheck -Component Registration
142
148
Starting known issue check for Azure Stack HCI: Registration.
143
149
Starting Azure Stack HCI base system validation.
144
150
Gathering information from all clustered nodes.
@@ -192,13 +198,13 @@ Data collection done . Please upload the file to the Microsoft Workspace.
192
198
### For base Azure Local system issues
193
199
194
200
``` powershell
195
- Invoke-AzsSupportDiagnosticCheck -ProductName BaseSystem
201
+ Invoke-AzsSupportDiagnosticCheck -Component BaseSystem
196
202
```
197
203
198
204
Here's an example of the output for base system issues:
199
205
200
206
``` output
201
- PS C:\temp> Invoke-AzsSupportDiagnosticCheck -ProductName BaseSystem
207
+ PS C:\temp> Invoke-AzsSupportDiagnosticCheck -Component BaseSystem
202
208
Starting known issue check for Azure Stack HCI: BaseSystem.
203
209
Gathering information from all clustered nodes.
204
210
We are preparing to collect diagnostic information from your environment
0 commit comments