Page 251 / 427 Scroll up to view Page 246 - 250
P-2602H(W)(L)-DxA Series User’s Guide
Chapter 18 Static Route
251
Figure 134
Static Route Edit
The following table describes the labels in this screen.
Table 95
Static Route Edit
LABEL
DESCRIPTION
Active
This field allows you to activate/deactivate this static route.
Route Name
Enter the name of the IP static route. Leave this field blank to delete this static route.
Destination IP
Address
This parameter specifies the IP network address of the final destination.
Routing is
always based on network number. If you need to specify a route to a single host, use
a subnet mask of 255.255.255.255 in the subnet mask field to force the network
number to be identical to the host ID.
IP Subnet Mask
Enter the IP subnet mask here.
Gateway IP
Address
Enter the IP address of the gateway. The gateway is a router or switch on the same
network segment as the device's LAN or WAN port. The gateway helps forward
packets to their destinations.
Back
Click
Back
to return to the previous screen without saving.
Apply
Click
Apply
to save your changes back to the ZyXEL Device.
Cancel
Click
Cancel
to begin configuring this screen afresh.
Page 252 / 427
P-2602H(W)(L)-DxA Series User’s Guide
252
Chapter 18 Static Route
Page 253 / 427
P-2602H(W)(L)-DxA Series User’s Guide
Chapter 19 Bandwidth Management
253
C
HAPTER
19
Bandwidth Management
This chapter contains information about configuring bandwidth management, editing rules and
viewing the ZyXEL Device’s bandwidth management logs.
19.1
Bandwidth Management Overview
ZyXEL’s Bandwidth Management allows you to specify bandwidth management rules based
on an application and/or subnet. You can allocate specific amounts of bandwidth capacity
(bandwidth budgets) to different bandwidth rules.
The ZyXEL Device applies bandwidth management to traffic that it forwards out through an
interface. The ZyXEL Device does not control the bandwidth of traffic that comes into an
interface.
Bandwidth management applies to all traffic flowing out of the router, regardless of the
traffic's source.
Traffic redirect or IP alias may cause LAN-to-LAN traffic to pass through the ZyXEL Device
and be managed by bandwidth management.
The sum of the bandwidth allotments that apply to the WAN interface (LAN to WAN,
WLAN to WAN) must be less than or equal to the WAN speed that you configure in the
Bandwidth Management Summary
screen.
The sum of the bandwidth allotments that apply to the LAN port (WAN to LAN, WLAN
to LAN) must be less than or equal to the LAN speed that you configure in the
Bandwidth Management Summary
screen.
The sum of the bandwidth allotments that apply to the WLAN port (LAN to WLAN,
WAN to WLAN) must be less than or equal to the WLAN speed that you configure in the
Bandwidth Management Summary
screen.
19.2
Application-based Bandwidth Management
You can create bandwidth classes based on individual applications (like VoIP, Web, FTP, E-
mail and Video for example).
19.3
Subnet-based Bandwidth Management
You can create bandwidth classes based on subnets.
Page 254 / 427
P-2602H(W)(L)-DxA Series User’s Guide
254
Chapter 19 Bandwidth Management
The following figure shows LAN subnets. You could configure one bandwidth class for
subnet
A
and another for subnet
B
.
Figure 135
Subnet-based Bandwidth Management Example
19.4
Application and Subnet-based Bandwidth Management
You could also create bandwidth classes based on a combination of a subnet and an
application. The following example table shows bandwidth allocations for application specific
traffic from separate LAN subnets.
19.5
Scheduler
The scheduler divides up an interface’s bandwidth among the bandwidth classes. The ZyXEL
Device has two types of scheduler: fairness-based and priority-based.
19.5.1
Priority-based Scheduler
With the priority-based scheduler, the ZyXEL Device forwards traffic from bandwidth classes
according to the priorities that you assign to the bandwidth classes. The larger a bandwidth
class’s priority number is, the higher the priority. Assign real-time applications (like those
using audio or video) a higher priority number to provide smoother operation.
Table 96
Application and Subnet-based Bandwidth Management Example
TRAFFIC TYPE
FROM SUBNET A
FROM SUBNET B
VoIP
64 Kbps
64 Kbps
Web
64 Kbps
64 Kbps
FTP
64 Kbps
64 Kbps
E-mail
64 Kbps
64 Kbps
Video
64 Kbps
64 Kbps
Page 255 / 427
P-2602H(W)(L)-DxA Series User’s Guide
Chapter 19 Bandwidth Management
255
19.5.2
Fairness-based Scheduler
The ZyXEL Device divides bandwidth equally among bandwidth classes when using the
fairness-based scheduler; thus preventing one bandwidth class from using all of the interface’s
bandwidth.
19.6
Maximize Bandwidth Usage
The maximize bandwidth usage option (see
Figure 136 on page 258
) allows the ZyXEL
Device to divide up any available bandwidth on the interface (including unallocated
bandwidth and any allocated bandwidth that a class is not using) among the bandwidth classes
that require more bandwidth.
When you enable maximize bandwidth usage, the ZyXEL Device first makes sure that each
bandwidth class gets up to its bandwidth allotment. Next, the ZyXEL Device divides up an
interface’s available bandwidth (bandwidth that is unbudgeted or unused by the classes)
depending on how many bandwidth classes require more bandwidth and on their priority
levels. When only one class requires more bandwidth, the ZyXEL Device gives extra
bandwidth to that class.
When multiple classes require more bandwidth, the ZyXEL Device gives the highest priority
classes the available bandwidth first (as much as they require, if there is enough available
bandwidth), and then to lower priority classes if there is still bandwidth available. The ZyXEL
Device distributes the available bandwidth equally among classes with the same priority level.
19.6.1
Reserving Bandwidth for Non-Bandwidth Class Traffic
Do the following to configure the ZyXEL Device to allow bandwidth for traffic that is not
defined in a bandwidth filter.
1
Do not enable the interface’s
Maximize Bandwidth Usage
option.
2
Leave some of the interface’s bandwidth unbudgeted. Make sure that the interface’s root
class has more bandwidth than the sum of the bandwidths of the interface’s bandwidth
management rules.

Rate

3.5 / 5 based on 2 votes.

Bookmark Our Site

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

Share
Top