SonicWALL 5.8.1 Manuale Utente
Firewall Settings > QoS Mapping
765
SonicOS 5.8.1 Administrator Guide
Bandwidth Management
Although bandwidth management (BWM) is a fully integrated QoS service, wherein
classification and shaping is performed on the single SonicWALL appliance, effectively
eliminating the dependency on external systems and thus obviating the need for marking, it is
possible to concurrently configure BWM and QoS (layer 2 and/or layer 3 marking) settings on
a single Access Rule. This allows those external systems to benefit from the classification
performed on the SonicWALL even after it has already shaped the traffic. For details on how to
configure BWM, see
classification and shaping is performed on the single SonicWALL appliance, effectively
eliminating the dependency on external systems and thus obviating the need for marking, it is
possible to concurrently configure BWM and QoS (layer 2 and/or layer 3 marking) settings on
a single Access Rule. This allows those external systems to benefit from the classification
performed on the SonicWALL even after it has already shaped the traffic. For details on how to
configure BWM, see
Outbound Bandwidth Management
The available bandwidth on a WAN link is tracked by means of adjusting a link credit (token)
pool for each packet sent. Providing that the link has not yet reached a point of saturation, the
prioritized queues are deemed eligible for processing.
pool for each packet sent. Providing that the link has not yet reached a point of saturation, the
prioritized queues are deemed eligible for processing.
Like CBQ, SonicOS BWM is based on a class structure, where traffic queues are classified
according to Access Rules—for example SSH, Telnet, or HTTP—and then scheduled
according to their prescribed priority. Each participating Access Rule is assigned three values:
Guaranteed bandwidth, Maximum bandwidth, and Bandwidth priority. Scheduling prioritization
is achieved by assignment to one of eight priority queues, starting at 0 (zero) for the highest
priority, and descending to 7 (seven) for the lowest priority. The resulting queuing hierarchy can
be best thought of as a node tree structure that is always one level deep, where all nodes are
leaf nodes, containing no children.
according to Access Rules—for example SSH, Telnet, or HTTP—and then scheduled
according to their prescribed priority. Each participating Access Rule is assigned three values:
Guaranteed bandwidth, Maximum bandwidth, and Bandwidth priority. Scheduling prioritization
is achieved by assignment to one of eight priority queues, starting at 0 (zero) for the highest
priority, and descending to 7 (seven) for the lowest priority. The resulting queuing hierarchy can
be best thought of as a node tree structure that is always one level deep, where all nodes are
leaf nodes, containing no children.
WAN Interface
Link BW
100 Kbps
100 Kbps
GBW 10 kbps
MBW 20 Kbps
Pri 4
GBW 20 kbps
MBW 40 Kbps
Pri 0
GBW 20 kbps
MBW 25 Kbps
Pri 0
GBW 5 kbps
MBW 15 Kbps
Pri 7
FTP
H323
Yahoo Msngr
VOIP
VNC
Pkt 5 - 500 B
Pkt 4 - 40 B
Pkt 3 - 1500 B
Pkt 2 - 1000 B
Pkt 1 - 400 B
Pkt 4 - 40 B
Pkt 3 - 1500 B
Pkt 2 - 1000 B
Pkt 1 - 400 B
Pkt 3 - 500 B
Pkt 2 - 700 B
Pkt 1 - 1500 B
Pkt 2 - 700 B
Pkt 1 - 1500 B
Pkt 5 - 500 B
Pkt 4 - 40 B
Pkt 3 - 500 B
Pkt 2 - 1500 B
Pkt 1 - 1200 B
Pkt 4 - 40 B
Pkt 3 - 500 B
Pkt 2 - 1500 B
Pkt 1 - 1200 B
LOL!
Pkt 5 - 500 B
Pkt 4 - 40 B
Pkt 3 - 500 B
Pkt 2 - 1200 B
Pkt 1 - 1000 B
Pkt 4 - 40 B
Pkt 3 - 500 B
Pkt 2 - 1200 B
Pkt 1 - 1000 B