Chapter 28 Bandwidth Management
Here is an overview of what the rules need to accomplish. See the following sections for more details.
•SIP traffic from VIP users must get through with the least possible delay regardless of if it is an outgoing call or an incoming call. The VIP users must be able to make and receive SIP calls no matter which interface they are connected to.
•HTTP traffic needs to be given priority over FTP traffic.
•FTP traffic from the WAN to the DMZ must be limited so it does not interfere with SIP and HTTP traffic.
•FTP traffic from the LAN1 to the DMZ can use more bandwidth since the interfaces support up to 1 Gbps connections, but it must be the lowest priority and limited so it does not interfere with SIP and HTTP traffic.
Figure 281 Bandwidth Management Example
SIP: Any to WAN | SIP: WAN to Any | |
Outbound: 200 Kbps | Outbound: 200 Kbps | |
Inbound: 200 Kbps | Inbound: 200 Kbps | |
Priority: 1 | Priority: 1 | |
Max. B. U. | Max. B. U. | |
HTTP: Any to WAN |
| |
Outbound: 100 Kbps |
| |
Inbound: 500 Kbps |
| |
Priority: 2 |
| |
Max. B. U. |
| |
FTP: WAN to DMZ | ADSL | |
Up: 1 Mbps | ||
Outbound: 100 Kbps | ||
Down 8 Mbps | ||
Inbound: 300 Kbps | ||
Priority: 3 |
| |
No Max. B. U. |
| |
| FTP: LAN1 to DMZ | |
| Outbound: 50 Mbps | |
| Inbound: 50 Mbps | |
| Priority: 4 | |
| No Max. B. U. |
Use the interface screens to set the WAN zone interface’s upstream bandwidth to be equal to (or slightly less than) what the connected device can support. This example uses 1000 Kbps.
28.1.3.2SIP Any to WAN Bandwidth Management Example•Manage SIP traffic going to the WAN zone from a VIP user on the LAN or DMZ.
•Outbound traffic (to the WAN from the LAN and DMZ) is limited to 200 kbps. The ZyWALL applies this limit before sending the traffic to the WAN.
•Inbound traffic (to the LAN and DMZ from the WAN) is also limited to 200 kbps. The ZyWALL applies this limit before sending the traffic to LAN or DMZ.
458 |
| |
ZyWALL USG 20/20W User’s Guide |
| |
|
|
|