Skip to content

Commit 02d7b9e

Browse files
committed
Mark ups - remote storage team review
1 parent 73ee0f8 commit 02d7b9e

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

articles/operator-nexus/troubleshoot-unhealthy-degraded-storage-appliance.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -51,11 +51,13 @@ The health events listed in the text below indicate that the appliance has activ
5151
Storage Appliance. Warning alerts indicate that there is an issue that requires attention, but the Storage
5252
Appliance should continue to function.
5353
- `StorageApplianceActiveAlertsCritical`, which means there are one or more open critical alerts on the
54-
Storage Appliance. Critical alerts indicate a severe problem with the Storage Appliance.
54+
Storage Appliance. Critical alerts indicate a severe problem with the Storage Appliance, that may impact
55+
functionality.
5556

56-
You should find more details of the specific alert(s), using the following instructions:
57+
You can find more details of the specific alert(s), using the following instructions:
5758

58-
- If you have your Storage Appliance set up to send logs to a Log Analytics Workspace (LAW), you can gather
59+
- If you have your Storage Appliance set up to send logs to a
60+
[Log Analytics workspace](/azure/azure-monitor/logs/log-analytics-workspace-overview) (LAW), you can gather
5961
more details by running the query from the text block below in your LAW.
6062
```
6163
StorageApplianceAlerts
@@ -75,8 +77,8 @@ Once you have this information, use it to determine the appropriate next action.
7577

7678
- Take an action yourself (such as reseating a cable).
7779
- Raise a ticket with your storage vendor.
78-
- Raise a ticket with Microsoft. If you need to raise a ticket with us, please include the Storage Appliance
79-
name and the details of the health event for quicker issue triage.
80+
- Raise a ticket with Microsoft. If you need to raise a ticket with Microsoft, please include the Storage Appliance
81+
resource ID, and the details of the health event for quicker issue triage.
8082

8183
## Latency
8284

@@ -97,7 +99,7 @@ is the cause:
9799
- Select the `Nexus Storage Array Latency` metric. Click `Apply splitting`, and select `Dimension` as
98100
the dimension to split on.
99101
- Click `+ New Chart`, and select the `Nexus Storage Array Performance Throughput Iops (Avg)` metric.
100-
Click `Apply Splitting`, and select `Dimension` as the dimension to split on
102+
Click `Apply Splitting`, and select `Dimension` as the dimension to split on.
101103

102104
:::image type="content" source="media/storage-metrics-latency-throughput.png" alt-text="Metric showing the latency and throughput on a Storage Appliance":::
103105

@@ -114,7 +116,7 @@ The health event listed in the text below indicates that the appliance has netwo
114116
on one or more interfaces has exceeded 3%.
115117

116118
To determine the unhealthy network interfaces, as well as the distribution of the errors, navigate
117-
to the Storage Appliance in the portal, navigate to the `Monitoring > Metrics` tab select
119+
to the Storage Appliance in the portal, navigate to the `Monitoring > Metrics` tab, and select
118120
`Nexus Storage Network Interface Performance Errors` in the `Metric` dropdown. Then, you should click
119121
`Apply splitting`, and select the `Dimension` and `Name` boxes, ensuring that you select a time range
120122
that starts shortly before the start time of the resource health alert. After identifying the
@@ -134,4 +136,4 @@ The health events listed in the text below indicate that the appliance has high
134136

135137
This increased latency implies an underlying problem with the networking between the Bare Metal Machines
136138
(BMMs) and the Storage Appliance. Latency can be introduced on any of the hops between BMMs and Storage Appliance.
137-
You should raise a ticket with Microsoft, quoting the text of this troubleshooting guide (TSG).
139+
You should raise a ticket with Microsoft, quoting the text of this troubleshooting article.

0 commit comments

Comments
 (0)