63 lines
4.3 KiB
HTML
63 lines
4.3 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="Network hardware and software" />
|
||
|
|
<meta name="abstract" content="The capabilities of your internal equipment and other equipment outside your network have enormous effects on quality of service (QoS) results." />
|
||
|
|
<meta name="description" content="The capabilities of your internal equipment and other equipment outside your network have enormous effects on quality of service (QoS) results." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8planning.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8rsvp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8conditioners.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="rzak8equipment" />
|
||
|
|
<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>Network hardware and software</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak8equipment"><a name="rzak8equipment"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Network hardware and software</h1>
|
||
|
|
<div><p>The capabilities of your internal equipment and other equipment
|
||
|
|
outside your network have enormous effects on quality of service (QoS)
|
||
|
|
results.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Applications</h4><p>Integrated service policies require
|
||
|
|
applications that are enabled by ReSerVation Protocol (RSVP). Because the iSeries™ applications
|
||
|
|
are not presently RSVP-enabled, you must enable them to use RSVP. To enable
|
||
|
|
your applications, you need to write special programs using the RSVP APIs
|
||
|
|
or qtoq QoS sockets APIs. These programs will allow your applications to use
|
||
|
|
RSVP. </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Network nodes</h4><p>The routers, switches, and even your
|
||
|
|
own servers must have the capability to use QoS. To use differentiated services
|
||
|
|
policies, your equipment must be enabled for differentiated services. This
|
||
|
|
means that the network node must be able to classify, meter, mark, shape,
|
||
|
|
and drop IP packets (traffic conditioners).</p>
|
||
|
|
<p>To use integrated services
|
||
|
|
policies, your equipment must be RSVP-enabled. This means that the network
|
||
|
|
nodes must also be able to support RSVP.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak8planning.htm" title="The most important step to accomplishing quality of service (QoS) is planning. To receive expected results, you must review your network equipment and monitor network traffic.">Plan for QoS</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><a href="rzak8conditioners.htm" title="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.">Traffic conditioners</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|