|
The EdgeXOS appliance supports several methods
for prioritizing traffic, including session limiting (where
only so many sessions are allowed per second), URL shaping (where
traffic can be prioritized based on the destination), and application
shaping (where the traffic can be prioritized based on a defined
application classification).
Administrative Shaping
These
methods for controlling bandwidth are called administrative
shaping controls. They do not provide the granularity that policy-based
shaping provides but do allow the administrator to set more
general rules for which traffic is preferred and which traffic
has lower important for the organization.
Application Classification
The EdgeXOS includes a number of pre-defined applications from
which to choose from Application Listing however the network
administrator can also define their own applications based on:
- Name
- Protocol
- Port (Source / Destination)
- and String Identifier
Application Prioritization
Once define an application can be set to one of 5 levels of
prioritization within the shaping engine. By changing the queuing
for each level the EdgeXOS platform is able to effect application
responsiveness and smooth packet streams.
URL Prioritization
Similar to application shaping the EdgeXOS is also able to prioritize
bandwidth based on the destination URL. This is useful if end-users
go to a specific website and/or SaaS service. It can also be
used for prioritizing certain FTP sites, or for Citrix and RDP
users. Simply define the remote URL/network and assign the level
of priority.
Session Limiting
One of the many problems which peer-to-peer clients create is
that when they start they launch many if not hundreds of sessions
in order to speed up the download of recreation audio, video,
and software files. These large session counts have the effect
of slowing down networks. With session limiting enabled, peer-to-peer
applications are limited to the number of sessions they can
use, and this in turns ensures more equal distribution of bandwidth.
|