81 lines
5.5 KiB
HTML
81 lines
5.5 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 control functions" />
|
||
|
|
<meta name="abstract" content="Traffic control functions only apply to integrated service and are not specific to iSeries." />
|
||
|
|
<meta name="description" content="Traffic control functions only apply to integrated service and are not specific to iSeries." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8intserv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8other_info.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8rsvp.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="rzak8traffic_control" />
|
||
|
|
<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 control functions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak8traffic_control"><a name="rzak8traffic_control"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Traffic control functions</h1>
|
||
|
|
<div><p>Traffic control functions only apply to integrated service and
|
||
|
|
are not specific to iSeries™.</p>
|
||
|
|
<p>You will not see these terms used in the quality of service (QoS)
|
||
|
|
interface, because the server cannot control external hardware. Outside a
|
||
|
|
private network, hardware needs to have the ability to handle general QoS
|
||
|
|
requirements. The general router requirements for IntServ policies are discussed
|
||
|
|
in the following section. It is suggested that you research general QoS concepts
|
||
|
|
and prerequisites before implementing policies.</p>
|
||
|
|
<p>To get predictable results, you need to have hardware that is enabled by
|
||
|
|
ReSerVation Protocol (RSVP), along the traffic's path. Routers must have certain
|
||
|
|
traffic control functions in order to use RSVP. This is often referred to
|
||
|
|
as being <em>RSVP-enabled</em> or <em>QoS-enabled</em>. Remember that your server's
|
||
|
|
role is either a client or a server. It cannot be used as a router at this
|
||
|
|
time. Check with your network equipment manuals, to verify that they can handle
|
||
|
|
QoS requirements.</p>
|
||
|
|
<p>Traffic control functions can include the following functions:</p>
|
||
|
|
<dl><dt class="dlterm">Packet scheduler</dt>
|
||
|
|
<dd>The packet scheduler manages the packet forwarding based on the information
|
||
|
|
in the IP header. The packet scheduler ensures that the packet delivery corresponds
|
||
|
|
to the parameters you set in your policy. The scheduler is implemented at
|
||
|
|
the point where packets are queued.</dd>
|
||
|
|
<dt class="dlterm">Packet classifier</dt>
|
||
|
|
<dd>The packet classifier identifies which packets of an IP flow will receive
|
||
|
|
a certain level of service based, again, on the IP header information. Each
|
||
|
|
incoming packet is mapped by the classifier into a specific class. All the
|
||
|
|
packets that are classified in the same class receive the same treatment.
|
||
|
|
This service-level is based on the information you provided in your policy.</dd>
|
||
|
|
<dt class="dlterm">Admission control</dt>
|
||
|
|
<dd>The admission control contains the decision algorithm that a router uses
|
||
|
|
to determine if there are enough routing resources to accept the requested
|
||
|
|
QoS for a new flow. If there are not enough resources, the new flow is rejected.
|
||
|
|
If the flow is accepted, the router assigns the packet classifier and scheduler
|
||
|
|
to reserve the requested QoS. Admission control occurs in each router along
|
||
|
|
the reservation path.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak8intserv.htm" title="The second type of outbound bandwidth policy you can create is an integrated service policy. Integrated service provides the capability for IP applications to request and reserve bandwidth using the ReSerVation Protocol (RSVP) and quality of service (QoS) APIs.">Integrated service</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzak8rsvp.htm" title="You can read this topic to learn about protocols, APIs, and requirements for a router that is enabled for the ReSerVation Protocol (RSVP). The current quality of service (QoS) APIs include the RAPI API, the qtoq socket API, the sendmsg() API, and the monitor APIs.">QoS APIs</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzak8other_info.htm" title="Listed here are the IBM Redbooks (in PDF format), Web sites, and information center topics that relate to the quality of service (QoS) topic. You can view or print any of the PDFs.">Related information for QoS</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|