[isalist] Traffic prioritization/bandwidth control
- From: "Mayo, Bill" <bemayo@xxxxxxxxxxxxxxxx>
- To: <isalist@xxxxxxxxxxxxx>
- Date: Mon, 4 Jan 2010 13:48:42 -0500
I am looking for recommendations/experiences for a solution for giving
priority to specific outbound traffic through ISA Server. The basic
problem is that we have an browser-based application that a significant
portion of our staff need to access in order to do their jobs (the
application is provided by the state). This application establishes
through HTTP and then shifts to operating primarily through Java (using
ports 4543-4544 and 46000-460005). Per the admission of the tech folks
at the state, this is a "fat" client--in other words, it is relatively
bandwidth intensive. We have sufficient bandwidth to suppor the
application, the problem is that bursty activity by others make the
application slow down. The biggest problem is the way this application
is engineered, but we have no control over that.
What I need is a way to tell ISA to give this traffic priority.
Theoretically, there is other traffic that I might have to identify in
the same way. Likewise, it would be nice to be able to have a group of
sites that we could identify as low priority (e.g. Facebook).
Our environment is 2 load-balanced ISA Server Enterprise Edition 2006
servers. We have QOS enabled on our switches for VOIP traffic, but I
really don't have any experience with using QOS for anything other than
the specific configurations used for the phones. I am aware that ISA
has at least some QOS available and I am aware of the things listed on
http://www.isaserver.org/software/ISA/Bandwidth-Control/. What I am
looking for is info from folks that have experience with any of these,
and/or what you would do in this situation. I have to wear a lot of
hats, so something that is as hands-off as possible is the best, as well
as something that is relatively straightforward to configure. On the
other hand, I don't want something that is going to add a lot of
overhead (bog down) our ISA Servers.
Thanks!
Bill Mayo
Other related posts:
