1. Home
    2. /
  2. Manuals
    3. /
  3. Zyxel
    4. /
  4. ZyWALL-USG50
    5. /
  5. 89
Page 441 / 944 Scroll up to view Page 436 - 440
Chapter 28 Application Patrol
ZyWALL USG 50 User’s Guide
441
•
Inbound traffic is limited to 500 kbs. The connection initiator is on the LAN1 so
inbound means the traffic traveling from the WAN to the LAN1.
Figure 268
LAN1 to WAN, Outbound 200 kbps, Inbound 500 kbps
Bandwidth Management Priority
•
The ZyWALL gives bandwidth to higher-priority traffic first, until it reaches its
configured bandwidth rate.
•
Then lower-priority traffic gets bandwidth.
•
The ZyWALL uses a fairness-based (round-robin) scheduler to divide bandwidth
among traffic flows with the same priority.
•
The ZyWALL automatically treats traffic with bandwidth management disabled
as priority 7 (the lowest priority).
Maximize Bandwidth Usage
Maximize bandwidth usage allows applications with maximize bandwidth usage
enabled to “borrow” any unused bandwidth on the out-going interface.
After each application gets its configured bandwidth rate, the ZyWALL uses the
fairness- based scheduler to divide any unused bandwidth on the out-going
interface amongst applications that need more bandwidth and have maximize
bandwidth usage enabled.
Unused bandwidth is divided equally. Higher priority traffic does not get a larger
portion of the unused bandwidth.
Bandwidth Management Behavior
The following sections show how bandwidth management behaves with various
settings. For example, you configure DMZ to WAN policies for FTP servers
A
and
B
. Each server tries to send 1000 kbps, but the WAN is set to a maximum
Inbound
Outbound
Outbound
500 kbps
200 kbps
200 kbps
Page 442 / 944
Chapter 28 Application Patrol
ZyWALL USG 50 User’s Guide
442
outgoing speed of 1000 kbps. You configure policy A for server
A
’s traffic and
policy B for server
B
’s traffic.
Figure 269
Bandwidth Management Behavior
Configured Rate Effect
In the following table the configured rates total less than the available bandwidth
and maximize bandwidth usage is disabled, both servers get their configured rate.
Priority Effect
Here the configured rates total more than the available bandwidth. Because server
A
has higher priority, it gets up to it’s configured rate (800 kbps), leaving only 200
kbps for server
B
.
Maximize Bandwidth Usage Effect
With maximize bandwidth usage enabled, after each server gets its configured
rate, the rest of the available bandwidth is divided equally between the two. So
server
A
gets its configured rate of 300 kbps and server
B
gets its configured rate
of 200 kbps. Then the ZyWALL divides the remaining bandwidth (1000 - 500 =
500) equally between the two (500 / 2 = 250 kbps for each). The priority has no
effect on how much of the unused bandwidth each server gets.
Table 125
Configured Rate Effect
POLICY
CONFIGURED RATE
MAX. B. U.
PRIORITY
ACTUAL RATE
A
300 kbps
No
1
300 kbps
B
200 kbps
No
1
200 kbps
Table 126
Priority Effect
POLICY
CONFIGURED RATE
MAX. B. U.
PRIORITY
ACTUAL RATE
A
800 kbps
Yes
1
800 kbps
B
1000 kbps
Yes
2
200 kbps
1000 kbps
1000 kbps
BWM
1000 kbps
Page 443 / 944
Chapter 28 Application Patrol
ZyWALL USG 50 User’s Guide
443
So server
A
gets its configured rate of 300 kbps plus 250 kbps for a total of 550
kbps. Server
B
gets its configured rate of 200 kbps plus 250 kbps for a total of
450 kbps.
Priority and Over Allotment of Bandwidth Effect
Server
A
has a configured rate that equals the total amount of available
bandwidth and a higher priority. You should regard extreme over allotment of
traffic with different priorities (as shown here) as a configuration error. Even
though the ZyWALL still attempts to let all traffic get through and not be lost,
regardless of its priority, server
B
gets almost no bandwidth with this
configuration.
Finding Out More
•
See
Section 6.5.17 on page 102
for related information on these screens.
•
See
Section 7.5 on page 122
for an example of how to set up web surfing
policies with bandwidth restrictions.
•
See
DSCP Marking and Per-Hop Behavior on page 283
for a description of DSCP
marking.
28.1.3
Application Patrol Bandwidth Management Examples
Bandwidth management is very useful when applications are competing for limited
bandwidth. For example, say you have a WAN zone interface connected to an
ADSL device with a 8 Mbps downstream and 1 Mbps upstream ADSL connection.
The following sections give some simplified examples of using application patrol
policies to manage applications competing for that 1 Mbps of upstream bandwidth.
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.
Table 127
Maximize Bandwidth Usage Effect
POLICY
CONFIGURED RATE
MAX. B. U.
PRIORITY
ACTUAL RATE
A
300 kbps
Yes
1
550 kbps
B
200 kbps
Yes
2
450 kbps
Table 128
Priority and Over Allotment of Bandwidth Effect
POLICY
CONFIGURED RATE
MAX. B. U.
PRIORITY
ACTUAL RATE
A
1000 kbps
Yes
1
999 kbps
B
1000 kbps
Yes
2
1 kbps
Page 444 / 944
Chapter 28 Application Patrol
ZyWALL USG 50 User’s Guide
444
•
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 270
Application Patrol Bandwidth Management Example
28.1.3.1
Setting the Interface’s Bandwidth
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.2
SIP 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.
•
Highest priority (1). Set policies for other applications to lower priorities so the
SIP traffic always gets the best treatment.
SIP: Any to WAN
Outbound: 200 Kbps
Inbound: 200 Kbps
Priority: 1
Max. B. U.
HTTP: Any to WAN
Outbound: 100 Kbps
Inbound: 500 Kbps
Priority: 2
Max. B. U.
FTP: WAN to DMZ
Outbound: 100 Kbps
Inbound: 300 Kbps
Priority: 3
No Max. B. U.
SIP: WAN to Any
Outbound: 200 Kbps
Inbound: 200 Kbps
Priority: 1
Max. B. U.
FTP: LAN1 to DMZ
Outbound: 50 Mbps
Inbound: 50 Mbps
Priority: 4
No Max. B. U.
Page 445 / 944
Chapter 28 Application Patrol
ZyWALL USG 50 User’s Guide
445
•
Enable maximize bandwidth usage so the SIP traffic can borrow unused
bandwidth.
Figure 271
SIP Any to WAN Bandwidth Management Example
28.1.3.3
SIP WAN to Any Bandwidth Management Example
You also create a policy for calls coming in from the SIP server on the WAN. It is
the same as the SIP Any to WAN policy, but with the directions reversed (WAN to
Any instead of Any to WAN).
28.1.3.4
HTTP Any to WAN Bandwidth Management Example
•
Inbound traffic gets more bandwidth as the local users will probably download
more than they upload (and the ADSL connection supports this).
•
Second highest priority (2). Set policies for other applications (except SIP) to
lower priorities so the local users’ HTTP traffic gets sent before non-SIP traffic.
•
Enable maximize bandwidth usage so the HTTP traffic can borrow unused
bandwidth.
Figure 272
HTTP Any to WAN Bandwidth Management Example
Inbound: 200 kbps
Outbound: 200 kbps
BWM
BWM
Inbound: 500 kbps
Outbound: 200 kbps
BWM
BWM

Rate

4.5 / 5 based on 2 votes.

Popular Zyxel Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top