Skip to content

Commit 8522dfd

Browse files
btray900btray900
authored
Additional comment updates
1 parent e93c3cc commit 8522dfd

File tree

1 file changed

+83
-20
lines changed

1 file changed

+83
-20
lines changed

‎articles/operator-nexus/howto-baremetal-run-data-extract.md

Lines changed: 83 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -101,32 +101,37 @@ Script execution result can be found in storage account:
101101
https://cm2p9bctvhxnst.blob.core.windows.net/bmm-run-command-output/dd84df50-7b02-4d10-a2be-46782cbf4eef-action-bmmdataextcmd.tar.gz?se=2023-04-14T01%3A00%3A15Zandsig=ZJcsNoBzvOkUNL0IQ3XGtbJSaZxYqmtd%2BM6rmxDFqXE%3Dandsp=randspr=httpsandsr=bandst=2023-04-13T21%3A00%3A15Zandsv=2019-12-12
102102
```
103103

104+
__Example list of hardware support files collected__
105+
106+
```
107+
Archive: TSR20240227164024_FM56PK3.pl.zip
108+
creating: tsr/hardware/
109+
creating: tsr/hardware/spd/
110+
creating: tsr/hardware/sysinfo/
111+
creating: tsr/hardware/sysinfo/inventory/
112+
inflating: tsr/hardware/sysinfo/inventory/sysinfo_CIM_BIOSAttribute.xml
113+
inflating: tsr/hardware/sysinfo/inventory/sysinfo_CIM_Sensor.xml
114+
inflating: tsr/hardware/sysinfo/inventory/sysinfo_DCIM_View.xml
115+
inflating: tsr/hardware/sysinfo/inventory/sysinfo_DCIM_SoftwareIdentity.xml
116+
inflating: tsr/hardware/sysinfo/inventory/sysinfo_CIM_Capabilities.xml
117+
inflating: tsr/hardware/sysinfo/inventory/sysinfo_CIM_StatisticalData.xml
118+
creating: tsr/hardware/sysinfo/lcfiles/
119+
inflating: tsr/hardware/sysinfo/lcfiles/lclog_0.xml.gz
120+
inflating: tsr/hardware/sysinfo/lcfiles/curr_lclog.xml
121+
creating: tsr/hardware/psu/
122+
creating: tsr/hardware/idracstateinfo/
123+
inflating: tsr/hardware/idracstateinfo/avc.log
124+
extracting: tsr/hardware/idracstateinfo/avc.log.persistent.1
125+
[..snip..]
126+
```
127+
104128
### Collect MDE Agent Information
105129

106130
Data is collected with the `mde-agent-information` command and formatted as JSON
107131
to `/hostfs/tmp/runcommand/mde-agent-information.json`. The JSON file is found
108132
in the data extract zip file located in the storage account. The script executes a
109133
sequence of `mdatp` commands on the designated baremetal machine.
110134

111-
__Example JSON object collected__
112-
113-
```
114-
{
115-
"diagnosticInformation": {
116-
"realTimeProtectionStats": $real_time_protection_stats,
117-
"eventProviderStats": $event_provider_stats
118-
},
119-
"mdeDefinitions": $mde_definitions,
120-
"generalHealth": $general_health,
121-
"mdeConfiguration": $mde_config,
122-
"scanList": $scan_list,
123-
"threatInformation": {
124-
"list": $threat_info_list,
125-
"quarantineList": $threat_info_quarantine_list
126-
}
127-
}
128-
```
129-
130135
This example executes the `mde-agent-information` command without arguments.
131136

132137
```azurecli
@@ -151,6 +156,25 @@ Script execution result can be found in storage account:
151156
https://cmzhnh6bdsfsdwpbst.blob.core.windows.net/bmm-run-command-output/f5962f18-2228-450b-8cf7-cb8344fdss63b0-action-bmmdataextcmd.tar.gz?se=2023-07-26T19%3A07%3A22Z&sig=X9K3VoNWRFP78OKqFjvYoxubp65BbNTq%2BGnlHclI9Og%3D&sp=r&spr=https&sr=b&st=2023-07-26T15%3A07%3A22Z&sv=2019-12-12
152157
```
153158

159+
__Example JSON object collected__
160+
161+
```
162+
{
163+
"diagnosticInformation": {
164+
"realTimeProtectionStats": $real_time_protection_stats,
165+
"eventProviderStats": $event_provider_stats
166+
},
167+
"mdeDefinitions": $mde_definitions,
168+
"generalHealth": $general_health,
169+
"mdeConfiguration": $mde_config,
170+
"scanList": $scan_list,
171+
"threatInformation": {
172+
"list": $threat_info_list,
173+
"quarantineList": $threat_info_quarantine_list
174+
}
175+
}
176+
```
177+
154178
### Collect MDE Support Diagnostics
155179

156180
Data collected from the `mde-support-diagnostics` command uses the MDE Client Analyzer tool to bundle information from `mdatp` commands and relevant log files. The storage account `tgz` file will contain a `zip` file named `mde-support-diagnostics-<hostname>.zip`. The `zip` should be sent along with any support requests to ensure the supporting teams can use the logs for troubleshooting and root cause analysis, if needed.
@@ -190,6 +214,8 @@ Script execution result can be found in storage account:
190214

191215
After downloading the execution result file, the support files can be unzipped for analysis.
192216

217+
__Example list of information collected by the MDE Client Analyzer__
218+
193219
```azurecli
194220
Archive: mde-support-diagnostics-rack1compute02.zip
195221
inflating: mde_diagnostic.zip
@@ -209,7 +235,7 @@ Archive: mde-support-diagnostics-rack1compute02.zip
209235
### Hardware Rollup Status
210236

211237
Data is collected with the `hardware-rollup-status` command and formatted as JSON to `/hostfs/tmp/runcommand/rollupStatus.json`. The JSON file is found
212-
in the data extract zip file located in the storage account.
238+
in the data extract zip file located in the storage account. The data collected will show the health of the machine subsystems.
213239

214240
This example executes the `hardware-rollup-status` command without arguments.
215241

@@ -234,6 +260,43 @@ Script execution result can be found in storage account:
234260
https://cmkfjft8twwpst.blob.core.windows.net/bmm-run-command-output/20b217b5-ea38-4394-9db1-21a0d392eff0-action-bmmdataextcmd.tar.gz?se=2023-09-19T18%3A47%3A17Z&sig=ZJcsNoBzvOkUNL0IQ3XGtbJSaZxYqmtd%3D&sp=r&spr=https&sr=b&st=2023-09-19T14%3A47%3A17Z&sv=2019-12-12
235261
```
236262

263+
__Example JSON Collected__
264+
265+
```
266+
{
267+
"@odata.context" : "/redfish/v1/$metadata#DellRollupStatusCollection.DellRollupStatusCollection",
268+
"@odata.id" : "/redfish/v1/Systems/System.Embedded.1/Oem/Dell/DellRollupStatus",
269+
"@odata.type" : "#DellRollupStatusCollection.DellRollupStatusCollection",
270+
"Description" : "A collection of DellRollupStatus resource",
271+
"Members" :
272+
[
273+
{
274+
"@odata.context" : "/redfish/v1/$metadata#DellRollupStatus.DellRollupStatus",
275+
"@odata.id" : "/redfish/v1/Systems/System.Embedded.1/Oem/Dell/DellRollupStatus/iDRAC.Embedded.1_0x23_SubSystem.1_0x23_Current",
276+
"@odata.type" : "#DellRollupStatus.v1_0_0.DellRollupStatus",
277+
"CollectionName" : "CurrentRollupStatus",
278+
"Description" : "Represents the subcomponent roll-up statuses.",
279+
"Id" : "iDRAC.Embedded.1_0x23_SubSystem.1_0x23_Current",
280+
"InstanceID" : "iDRAC.Embedded.1#SubSystem.1#Current",
281+
"Name" : "DellRollupStatus",
282+
"RollupStatus" : "Ok",
283+
"SubSystem" : "Current"
284+
},
285+
{
286+
"@odata.context" : "/redfish/v1/$metadata#DellRollupStatus.DellRollupStatus",
287+
"@odata.id" : "/redfish/v1/Systems/System.Embedded.1/Oem/Dell/DellRollupStatus/iDRAC.Embedded.1_0x23_SubSystem.1_0x23_Voltage",
288+
"@odata.type" : "#DellRollupStatus.v1_0_0.DellRollupStatus",
289+
"CollectionName" : "VoltageRollupStatus",
290+
"Description" : "Represents the subcomponent roll-up statuses.",
291+
"Id" : "iDRAC.Embedded.1_0x23_SubSystem.1_0x23_Voltage",
292+
"InstanceID" : "iDRAC.Embedded.1#SubSystem.1#Voltage",
293+
"Name" : "DellRollupStatus",
294+
"RollupStatus" : "Ok",
295+
"SubSystem" : "Voltage"
296+
},
297+
[..snip..]
298+
```
299+
237300
## Viewing the Output
238301

239302
Note the provided link to the tar.gz zipped file from the command execution. The tar.gz file name identifies the file in the Storage Account of the Cluster Manager resource group. You can also use the link to directly access the output zip file. The tar.gz file also contains the zipped extract command file outputs. Download the output file from the storage blob to a local directory by specifying the directory path in the optional argument `--output-directory`.

0 commit comments

Comments
 (0)