PDQ Connect offers bandwidth control options in the form of Staged deployments. This feature allows you to set a limit on the number of active downloads per public IP address. When the download limit is reached, any excess deployments will remain in a “Staged” status until the number of active downloads drops below the allowed limit.
Configuring Staged Deployments
To access the settings page for Staged deployments, click the gear icon in the lower left corner of the page, and select the Bandwidth tab.
Options overview:
|
Specifying IP Addresses
When entering the IP addresses that you wish to enable deployment staging on, some of the key aspects to remember are as follows:
- A maximum of 10 concurrent deployments may be configured as the Active download limit.
- All IP addresses should be public/external facing addresses. Staged deployments do not work for internal IP addresses. You can quickly see the public IP address for all your devices by enabling the Public IP address column on the Devices page.
- PDQ Connect allows you to enter as many different IP addresses as needed. If your network consists of five separate branches, you could enter all five public IP addresses for each location. Use the Plus icon under the IP addresses field to add additional IPs.
- The number of active downloads apply to every IP address in the list. It is not possible to configure the active downloads on a per IP basis.
- When specifying IP address ranges, CIDR notation must be used. If you wanted to use the IP range as 198.51.100.20 - 198.51.100.23, for example, it would need to be entered as 198.51.100.20/30.
- IPv4 and IPv6 addresses are supported, and the guidelines above apply to both.
- When multiple machines are queued for staging, there is no predetermined order for deployments. For practical purposes, the order is determined randomly.
For simplicity, some system administrators may wish to apply a single limit to every device in their PDQ Connect organization, regardless of the public IP. This can be accomplished by specifying the entire IPv4 and IPv6 ranges in CIDR notation using 0.0.0.0/0 for IPv4 and ::/0 for IPv6.
Example 1 - Single IP
In this example, a maximum of 5 concurrent deployments may be active for machines with the public IP 198.51.100.8. For any other device managed in PDQ Connect, deployments will all be processed simultaneously. |
Example 2 - Multiple (non-range) IPs
This example contains 3 single IP addresses, two in IPv4 and one in IPv6. Each of these IP addresses may have 10 active deployments at once, for a total limit of 30 active downloads. Note: If a device is managed in PDQ Connect behind a different public-facing IP address, the limit would not apply to that device or any others behind that IP address. |
Example 3 - Multiple IP Ranges using CIDR Notation
The example to the right includes 2 IP ranges in CIDR notation, one in IPv4 and the other in IPv6. Each range encompasses 4 IP addresses, for a total of 8 IP addresses targeted by staged deployments. Note that each IP in the range is counted separately toward the Active download limit, so there could be a total of 24 active downloads with this setup (3 Active downloads per each of the 8 possible IP addresses). |
Example 4 - All IP Ranges
In the final example, we are using CIDR notation to apply Staged deployments to every device in PDQ Connect. This is done by using IP ranges that include the entire range of IPv4 and IPv6 addresses: 0.0.0.0/0 and ::/0. While this is a quick way to apply implement bandwidth throttling across all devices, note that the Active download limit is still capped at 10 devices. In larger environments, it is usually recommended to narrow down the targets to specific IPs to prevent issues with scaling. Another common use case would be specifying specific IPv4 addresses, then using ::/0 to encompass all IPv6 addresses.
|
