98 lines
6.9 KiB
HTML
98 lines
6.9 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Scenario: Limit browser traffic" />
|
||
|
|
<meta name="abstract" content="You can use quality of service (QoS) to control traffic performance. Use a differentiated service policy to either limit or extend an application's performance within your network." />
|
||
|
|
<meta name="description" content="You can use quality of service (QoS) to control traffic performance. Use a differentiated service policy to either limit or extend an application's performance within your network." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8examples.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8scenariodetailsexample1step1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8scenariodetailsexample1step2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8scenariodetailsexample1step3.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8scenariodetailsexample1step4.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8sla.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8diffserv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8monitoring.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzak8example_1" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Scenario: Limit browser traffic</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak8example_1"><a name="rzak8example_1"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario: Limit browser traffic</h1>
|
||
|
|
<div><p>You can use quality of service (QoS) to control traffic
|
||
|
|
performance. Use a differentiated service policy to either limit or extend
|
||
|
|
an application's performance within your network.</p>
|
||
|
|
<div class="section" id="rzak8example_1__situation"><a name="rzak8example_1__situation"><!-- --></a><h4 class="sectionscenariobar">Situation</h4><p>Your
|
||
|
|
company has been experiencing high levels of browser traffic from the user-centered
|
||
|
|
design (UCD) group on Fridays. This traffic has been interfering with the
|
||
|
|
accounting department, which also requires good performance from their accounting
|
||
|
|
applications on Fridays. You decide to limit browser traffic from the UCD
|
||
|
|
group. The following figure illustrates the network setup in this scenario.</p>
|
||
|
|
<div class="fignone"><span class="figcap">Figure 1. Web server limiting browser traffic to a client</span><br /><img src="rzak8501.gif" alt="Shows the network setup
when you might want to use a differentiated service" /><br /></div>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rzak8example_1__objective"><a name="rzak8example_1__objective"><!-- --></a><h4 class="sectionscenariobar">Objectives</h4><p>To
|
||
|
|
limit browser traffic out of your network, you might create a differentiated
|
||
|
|
service policy. A differentiated service policy divides your traffic into
|
||
|
|
classes. All traffic within this policy is assigned a codepoint. This codepoint
|
||
|
|
tells routers how to treat the traffic. In this scenario, the policy might
|
||
|
|
be assigned a low codepoint value to affect how the network prioritizes browser
|
||
|
|
traffic.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rzak8example_1__prereq"><a name="rzak8example_1__prereq"><!-- --></a><h4 class="sectionscenariobar">Prerequisites
|
||
|
|
and assumptions</h4><ul><li>You have a service-level agreement (SLA) with your ISP to ensure that
|
||
|
|
the policies receive the requested priority. The QoS policy you create on
|
||
|
|
the iSeries™ server
|
||
|
|
enables traffic (in the policy) to receive priority throughout the network.
|
||
|
|
The QoS policy does not guarantee the priority and is dependent on your SLA.
|
||
|
|
In fact, taking advantage of QoS policies might give you some leverage to
|
||
|
|
negotiate certain service-levels and rates.</li>
|
||
|
|
<li>Differentiated service policies require DiffServ-aware routers along the
|
||
|
|
network path. Most routers are DiffServ aware.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rzak8example_1__example1steps"><a name="rzak8example_1__example1steps"><!-- --></a><h4 class="sectionscenariobar">Configuration</h4><p>After
|
||
|
|
you verify the prerequisites steps, you are ready to create the differentiated
|
||
|
|
service policy.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ol>
|
||
|
|
<li class="olchildlink"><a href="rzak8scenariodetailsexample1step1.htm">Scenario details: Create the differentiated service policy</a><br />
|
||
|
|
</li>
|
||
|
|
<li class="olchildlink"><a href="rzak8scenariodetailsexample1step2.htm">Scenario details: Start or update the QoS server</a><br />
|
||
|
|
</li>
|
||
|
|
<li class="olchildlink"><a href="rzak8scenariodetailsexample1step3.htm">Scenario details: Use the monitor to verify your policy is working</a><br />
|
||
|
|
</li>
|
||
|
|
<li class="olchildlink"><a href="rzak8scenariodetailsexample1step4.htm">Scenario details: Change properties (if needed)</a><br />
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak8examples.htm" title="These quality of service (QoS) policy scenarios can help you understand why and how to use QoS.">Scenarios</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzak8sla.htm" title="This topic points out some of the important aspects of a service-level agreement (SLA) that might affect your quality of service (QoS) implementation.">Service-level agreement</a></div>
|
||
|
|
<div><a href="rzak8diffserv.htm" title="This is the first type of outbound bandwidth policy you can create on your server. Differentiated service divides your traffic into classes. To carry out a differentiated service policy, you need to determine how you want to classify your network traffic and how to handle the different classes.">Differentiated service</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzak8monitoring.htm" title="You can use the quality of service (QoS) monitor to analyze your IP traffic through the server.">Monitor QoS</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|