You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage-mover/bandwidth-management.md
+13-10Lines changed: 13 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,11 +44,14 @@ Using the Azure portal, you can enable a bandwidth schedule on a registered agen
44
44
45
45
## Setting a bandwidth limit
46
46
47
-
1. Open the bandwidth scheduling window. ([see previous section](#enabling-or-changing-a-bandwidth-management-schedule))
48
-
1. 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.
47
+
Open the bandwidth scheduling window. ([see previous section](#enabling-or-changing-a-bandwidth-management-schedule))
48
+
49
+
Here you can create a custom schedule for this selected agent, or you [reuse a schedule](#reusing-a-schedule-from-another-agent) that was previously created for another agent.
50
+
49
51
1. 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.
50
52
:::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.":::
51
-
1. 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. Find more details in the paragraph: "[Reusing a schedule from another agent](#reusing-a-schedule-from-another-agent)".
53
+
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.
54
+
1. To "[reuse a schedule from another agent](#reusing-a-schedule-from-another-agent)", follow the link to an upcoming section.
52
55
1. To apply your changes to this agent, select the "*Save*" button at the bottom of the "*Bandwidth management*" window.
53
56
54
57
> [!NOTE]
@@ -87,7 +90,7 @@ Add all cmdlets - better to have them in one place.
-EndTimeMinute 30 # Optional. Time blocks are precise to 30 Minutes. -EndTimeMinute 0 is equivalent to omitting the parameter. The only other acceptable value is the half hour mark: 30.
133
136
134
-
TODO:
135
-
I need to see how to add a single new time block to an empty or existing schedule.
136
-
I need to see the best method of editing a schedule.
137
-
I need to see how I can delete a schedule.
138
-
139
-
I would like to document the JSON schema through an annotated example schedule.
137
+
#TODO:
138
+
#I need to see how to add a single new time block to an empty or existing schedule.
139
+
#I need to see the best method of editing a schedule.
140
+
#I need to see how I can delete a schedule.
141
+
#
142
+
#I would like to document the JSON schema through an annotated example schedule.
0 commit comments