133 lines
9.0 KiB
HTML
133 lines
9.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="Prioritized classes: How to classify network traffic" />
|
||
|
|
<meta name="abstract" content="Differentiated service identifies traffic as classes. The most common classes are defined using client IP addresses, application ports, server types, protocols, local IP addresses, and schedules. All traffic that conforms to the same class is treated equally." />
|
||
|
|
<meta name="description" content="Differentiated service identifies traffic as classes. The most common classes are defined using client IP addresses, application ports, server types, protocols, local IP addresses, and schedules. All traffic that conforms to the same class is treated equally." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8diffserv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8apis.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="rzak8classes" />
|
||
|
|
<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>Prioritized classes: How to classify network traffic</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak8classes"><a name="rzak8classes"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Prioritized classes: How to classify network traffic</h1>
|
||
|
|
<div><p>Differentiated service identifies traffic as <em>classes</em>. The
|
||
|
|
most common classes are defined using client IP addresses, application ports,
|
||
|
|
server types, protocols, local IP addresses, and schedules. All traffic that
|
||
|
|
conforms to the same class is treated equally.</p>
|
||
|
|
<p>For more advanced classification, you can specify server data to set different
|
||
|
|
levels of service for some of your iSeries applications. Using server data
|
||
|
|
is optional, but might be helpful when you want to classify at a lower level.
|
||
|
|
Server data is based on two types of application data: <em>application token</em> or <em>Uniform
|
||
|
|
Resource Identifier (URI)</em>. If traffic matches the token or URI you specify
|
||
|
|
in the policy, the policy will be applied to the outbound response, thus giving
|
||
|
|
the outbound traffic, whatever priority is specified in the differentiated
|
||
|
|
service policy.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Use application token with differentiated service policies</h4><p>Using
|
||
|
|
application data tells the policy to respond to specific parameters (token
|
||
|
|
and priority) passed by the application to the server through the sendmsg()
|
||
|
|
application programming interface (API). This setting is optional. If you
|
||
|
|
do not need this level of granularity in your outbound policies, select <span class="uicontrol">All
|
||
|
|
tokens</span> in the wizard. You can match an application's token and
|
||
|
|
priority with a specific token and priority set in the outbound policy, if
|
||
|
|
you want to. In the policy, there are two parts to setting the application
|
||
|
|
data, which include the token and the priority.</p>
|
||
|
|
<ul><li>What is an application token? <p>An application token is any character
|
||
|
|
string that can represent a defined resource, such as <samp class="codeph">myFTP</samp>.
|
||
|
|
The token you specify in the quality of service (QoS) policy is matched against
|
||
|
|
the token provided by the outbound application. The application provides the
|
||
|
|
token value through the sendmsg() API. If the tokens match, the application
|
||
|
|
traffic is included in the differentiated service policy.</p>
|
||
|
|
<p>To use an
|
||
|
|
application token in a differentiated service policy, follow these steps:</p>
|
||
|
|
<ol><li>From the QoS configuration window, right-click <span class="uicontrol">DiffServ</span> and
|
||
|
|
select <span class="uicontrol">New Policy</span>. Start the wizard.</li>
|
||
|
|
<li>On the Server Data Request page, select <span class="uicontrol">Selected application
|
||
|
|
token</span>.</li>
|
||
|
|
<li>To create a new token, click <span class="uicontrol">New</span>. The New URI window
|
||
|
|
appears.</li>
|
||
|
|
<li>In the <strong>Name</strong> field, enter a meaningful name for the application
|
||
|
|
token.</li>
|
||
|
|
<li>In the <strong>URI</strong> field, delete the <samp class="codeph">(/)</samp> and enter the
|
||
|
|
application token (a string of not more than 128 characters). For example, <samp class="codeph">myFTPapp</samp>,
|
||
|
|
rather than the typical URI.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li>What is an application priority? <p>The application priority you specify
|
||
|
|
is matched against the application priority provided by the outbound application.
|
||
|
|
The application provides the priority value using the sendmsg() API. If the
|
||
|
|
priorities match, the application traffic is included in the differentiated
|
||
|
|
service policy. All traffic defined in the differentiated service policy will
|
||
|
|
still receive the priority given to the entire policy.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>When you specify application token as the application data type, the
|
||
|
|
application providing this information to the server must be specifically
|
||
|
|
coded to use the sendmsg() API. This is done by the application programmer.
|
||
|
|
The application's documentation should provide valid values (token and priority),
|
||
|
|
which the QoS administrator will use in the differentiated service policy.
|
||
|
|
The differentiated service policy then applies its own priority and classification
|
||
|
|
to traffic that matches the token set in the policy. If the application does
|
||
|
|
not have values that match the values set in the policy, you must either update
|
||
|
|
the application or use different application data parameters for the differentiated
|
||
|
|
service policy.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Use a URI with differentiated service policies</h4><p>When
|
||
|
|
creating a differentiated service policy, the wizard allows you to set server
|
||
|
|
data information, as discussed in <span class="q">"Use application token with differentiated
|
||
|
|
service policies"</span> section. Although the fields in the wizard prompt you
|
||
|
|
for an application token, you can instead specify a relative URI. Again, this
|
||
|
|
is optional. If you do not need this level of granularity in your outbound
|
||
|
|
policies, select <span class="uicontrol">All tokens</span> in the wizard. You can
|
||
|
|
match a specific URI set in the outbound policy if you want to.</p>
|
||
|
|
<p>The
|
||
|
|
relative URI is actually a subset of an absolute URI (similar to the old absolute
|
||
|
|
URL). Consider this example: http://www.ibm.com/software. The <em>http://www.ibm.com/software</em> segment
|
||
|
|
is considered the absolute URI. The <em>/software</em> segment is the relative
|
||
|
|
URI. All relative URI values must begin with one forward slash <samp class="codeph">(<span class="uicontrol">/</span>)</samp>.
|
||
|
|
The following segments are valid relative URI examples:</p>
|
||
|
|
<ul><li>/market/grocery#D5</li>
|
||
|
|
<li>/software</li>
|
||
|
|
<li>/market/grocery?q=green</li>
|
||
|
|
</ul>
|
||
|
|
<p>Before you set up a differentiated service policy that uses URLs,
|
||
|
|
you must ensure that the application port assigned for the URI matches the
|
||
|
|
Listen directive enabled for the Fast Response Cache Accelerator (FRCA) in
|
||
|
|
the Apache Web Server configuration. To change or view the port for your HTTP
|
||
|
|
server, see <a href="../rzaie/rzaieaddressports.htm">Manage
|
||
|
|
addresses and ports for your HTTP server (powered by Apache)</a>.</p>
|
||
|
|
<p>FRCA
|
||
|
|
identifies the URI for each outbound HTTP response. It compares the URI related
|
||
|
|
to the outbound response to the URI defined in each differentiated service
|
||
|
|
policy. The first policy with a token string (URI) that best matches the URI
|
||
|
|
identified by FRCA, is applied to all responses for the URI.</p>
|
||
|
|
</div>
|
||
|
|
</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="rzak8apis.htm" title="The sendmsg() function is used to send data, ancillary data, or a combination of these through a connected or unconnected socket.">QoS sendmsg() API extensions</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|