88 lines
6.0 KiB
HTML
88 lines
6.0 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="Traffic conditioners" />
|
||
|
|
<meta name="abstract" content="To use quality of service (QoS) policies, network equipment (like routers and switches) must have the capability for traffic conditioners. Traffic conditioners refer to classifiers, meters, markers, shapers, and droppers." />
|
||
|
|
<meta name="description" content="To use quality of service (QoS) policies, network equipment (like routers and switches) must have the capability for traffic conditioners. Traffic conditioners refer to classifiers, meters, markers, shapers, and droppers." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8diffserv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8equipment.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="rzak8conditioners" />
|
||
|
|
<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>Traffic conditioners</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak8conditioners"><a name="rzak8conditioners"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Traffic conditioners</h1>
|
||
|
|
<div><p>To use quality of service (QoS) policies, network
|
||
|
|
equipment (like routers and switches) must have the capability for traffic
|
||
|
|
conditioners. Traffic conditioners refer to classifiers, meters, markers,
|
||
|
|
shapers, and droppers.</p>
|
||
|
|
<p>If the network equipment has all the traffic conditioners, then it is considered <dfn class="term">DiffServ-aware</dfn>.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> These hardware requirements are not iSeries™ specific. You will not see these
|
||
|
|
terms used in the QoS interface, because the server cannot control external
|
||
|
|
hardware. Outside a private network, hardware needs to have the ability to
|
||
|
|
handle general QoS requirements. Check with the specific equipment manuals
|
||
|
|
to make sure that they can handle differentiated service requirements. It
|
||
|
|
is also recommended that you research general QoS concepts and prerequisites
|
||
|
|
before implementing policies.</div>
|
||
|
|
<p>The following figure shows a logical representation of how traffic conditioners
|
||
|
|
work.</p>
|
||
|
|
<div class="fignone"><span class="figcap">Figure 1. Traffic conditioners</span><br /><img src="rzak8506.gif" alt="shows a logical representation of how traffic conditioners work." /><br /></div>
|
||
|
|
<p>The following information describes each of the traffic conditioners in
|
||
|
|
more detail.</p>
|
||
|
|
<dl><dt class="dlterm">Classifiers</dt>
|
||
|
|
<dd>Packet classifiers select packets in a traffic stream, based on the content
|
||
|
|
in its IP header. The iSeries server defines two types of classifiers.
|
||
|
|
The behavior aggregate (BA) classifies packets, based exclusively on the differentiated
|
||
|
|
services codepoint. The multi-field (MF) classifier selects packets, based
|
||
|
|
on the value of a combination of one or more header fields, such as source
|
||
|
|
address, destination address, differentiated services field, protocol ID,
|
||
|
|
source port, Uniform Resource Identifier (URI), server type and destination
|
||
|
|
port numbers.</dd>
|
||
|
|
<dt class="dlterm">Meters</dt>
|
||
|
|
<dd>Traffic meters measure whether the IP packets, being forwarded by the
|
||
|
|
classifier, are corresponding to the traffic's IP header profile. The information
|
||
|
|
in the IP header is determined by the values you set in the QoS policy for
|
||
|
|
this traffic. A meter passes information to other conditioning functions to
|
||
|
|
trigger an action. The action is triggered for each packet whether it is in-profile
|
||
|
|
or out-of-profile.</dd>
|
||
|
|
<dt class="dlterm">Markers</dt>
|
||
|
|
<dd>Packet markers set the differentiated services (DS) field. The marker
|
||
|
|
can be configured to mark all packets to a single codepoint or to a set of
|
||
|
|
codepoints used to select a per-hop behavior.</dd>
|
||
|
|
<dt class="dlterm">Shapers</dt>
|
||
|
|
<dd>Shapers delay some or all of the packets in a traffic stream to bring
|
||
|
|
the stream into compliance with the traffic profile. A shaper has a finite
|
||
|
|
buffer size, and routers might discard packets if there is not enough space
|
||
|
|
to hold the delayed packets.</dd>
|
||
|
|
<dt class="dlterm">Droppers</dt>
|
||
|
|
<dd>Droppers discard some or all of the packets in a traffic stream. This
|
||
|
|
occurs to bring the stream into compliance with the traffic profile.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <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="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzak8equipment.htm" title="The capabilities of your internal equipment and other equipment outside your network have enormous effects on quality of service (QoS) results.">Network hardware and software</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|