Skip to content

Commit d6d2feb

Browse files
committed
Addressing all review feedback points.
1 parent 99720e4 commit d6d2feb

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/storage-mover/bandwidth-management.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ A schedule is an attribute of a registered **agent**. In the portal, you can set
2424

2525
A bandwidth management schedule describes time windows throughout a week, during which you can set a limit on how much upload bandwidth a Storage Mover agent is allowed to use.
2626

27-
:::image type="content" source="media/bandwidth-management/bandwidth-full-schedule-small.png" alt-text="Azure portal dialog showing a calendar, similar to Outlook, with scheduled bandwidth limitation windows." lightbox="media/bandwidth-management/bandwidth-full-schedule.png":::
27+
:::image type="content" source="media/bandwidth-management/bandwidth-full-schedule-small.png" alt-text="A screenshot of an Azure portal dialog showing a calendar, similar to Outlook, with scheduled bandwidth limitation windows." lightbox="media/bandwidth-management/bandwidth-full-schedule.png":::
2828

2929
This schedule looks a lot like a calendar in outlook, but there are a few important differences:
3030

@@ -41,7 +41,7 @@ This schedule looks a lot like a calendar in outlook, but there are a few import
4141
Using the Azure portal, you can enable a bandwidth schedule on a registered agent resource.
4242
1. With the portal showing your Storage Mover resource, select "*Registered agents*" in the menu on the left.
4343
1. You now have two options to set or view a schedule. You can find the column "*Bandwidth management*" and click on the link for your selected agent. Or, you can select the checkbox in front of your agent. That enables and a command button above the list of agents, labeled "*Manage bandwidth limit*".
44-
:::image type="content" source="media/bandwidth-management/bandwidth-registered-agents-command-small.png" alt-text="Azure portal, registered agents blade, showing to select and agent and then select the Bandwidth Management command." lightbox="media/bandwidth-management/bandwidth-registered-agents-command.png":::
44+
:::image type="content" source="media/bandwidth-management/bandwidth-registered-agents-command-small.png" alt-text="A screenshot of the Azure portal, registered agents blade, showing first select an agent and then select the Bandwidth Management command." lightbox="media/bandwidth-management/bandwidth-registered-agents-command.png":::
4545
1. The bandwidth management window opens and displays the schedule currently in effect for the agent. When an empty schedule is shown, there are no bandwidth limitations defined for this agent.
4646

4747

@@ -52,7 +52,7 @@ Open the bandwidth scheduling window. ([see previous section](#enabling-or-chang
5252
Here you can create a custom schedule for this selected agent, or you can [reuse a schedule](#reusing-a-schedule-from-another-agent) that was previously created for another agent.
5353

5454
* To create a custom schedule, select the "Add limit" command. A dialog opens, allowing you to define a time slice during which you want to set the maximum bandwidth on your WAN link, that the agent is allowed to use.
55-
:::image type="content" source="media/bandwidth-management/bandwidth-add-limit.png" alt-text="An Azure portal dialog showing the inputs to set a limit for a custom time period.":::
55+
:::image type="content" source="media/bandwidth-management/bandwidth-add-limit.png" alt-text="A screenshot of an Azure portal dialog showing the inputs to set a limit for a custom time period.":::<br>
5656
The dialog requires you to set a start and an end-time during which you want to apply an uplink limit for the agent. You can then pick on which days of the week you like to apply your new limit. Select all weekdays during which you like to apply the same limit. You then need to specify the limit in Mbps (Megabits per second). Overlapping times aren't allowed. Any limit you set, applies at the displayed time in the agent's timezone. You can find the agent's timezone displayed at the top of the bandwidth management window. You may need to offset your schedule or adjust the agent's timezone.
5757
* To "[reuse a schedule from another agent](#reusing-a-schedule-from-another-agent)", follow the link to an upcoming section.
5858
* To apply your changes to this agent, select the "*Save*" button at the bottom of the "*Bandwidth management*" window.
@@ -192,7 +192,7 @@ Update-AzStorageMoverAgent `
192192
-AgentName $registeredAgentName `
193193
-UploadLimitScheduleWeeklyRecurrence $schedule # Apply your entire, updated schedule. Performing this step on an agent with other limits already configured will override them with this new schedule. Ensure there are no overlapping time spans, otherwise the operation will fail.
194194
```
195-
## Understanding the JSON schema of the bandwidth limit schedule
195+
## Understanding the JSON schema of a bandwidth limit schedule
196196
The bandwidth limit schedule is stored as a JSON construct in the property `UploadLimitScheduleWeeklyRecurrence` of a registered agent.
197197

198198
The [previous PowerShell section](#use-powershell-to-configure-a-bandwidth-limit-schedule) shows an example of how you can form and update this agent property by using Azure PowerShell.
@@ -203,7 +203,7 @@ You can, however, manually form that JSON and directly supply it as an argument
203203
204204
The following two representations of a bandwidth limit schedule are equivalent:
205205

206-
:::image type="content" source="media/bandwidth-management/bandwidth-limit-json-small.png" alt-text="Azure portal dialog showing a calendar with scheduled bandwidth limitations." lightbox="media/bandwidth-management/bandwidth-limit-json.png":::
206+
:::image type="content" source="media/bandwidth-management/bandwidth-limit-json-small.png" alt-text="A screenshot of the Azure portal showing a calendar with scheduled bandwidth limitations." lightbox="media/bandwidth-management/bandwidth-limit-json.png":::
207207

208208
```json
209209
{

0 commit comments

Comments
 (0)