378 lines
23 KiB
HTML
378 lines
23 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="reference" />
|
||
|
|
<meta name="DC.Title" content="Monitor QoS" />
|
||
|
|
<meta name="abstract" content="You can use the quality of service (QoS) monitor to analyze your IP traffic through the server." />
|
||
|
|
<meta name="description" content="You can use the quality of service (QoS) monitor to analyze your IP traffic through the server." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8administration.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8example_1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8example_4.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8scenario_5.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8example_3.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8example_2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8examples.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8monitor_server.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8monitor_policy.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="rzak8monitoring" />
|
||
|
|
<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>Monitor QoS</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak8monitoring"><a name="rzak8monitoring"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Monitor QoS</h1>
|
||
|
|
<div><p>You can use the quality of service (QoS) monitor to
|
||
|
|
analyze your IP traffic through the server.</p>
|
||
|
|
<div class="section"><p>This helps to determine where congestion is occurring within your
|
||
|
|
network. Not only is this useful during QoS planning, but it can also be helpful
|
||
|
|
as a troubleshooting tool. The QoS monitor can help you continue to monitor
|
||
|
|
your network so you can adjust your policies as needed. To monitor all active
|
||
|
|
policies, select <span class="menucascade"><span class="uicontrol">Server</span> > <span class="uicontrol">Monitor</span></span> from the QoS Configuration Server window. If you right-click
|
||
|
|
a single policy and select <span class="uicontrol">Monitor</span>, the monitor will
|
||
|
|
only display information for that one policy.</p>
|
||
|
|
<p>You can use the monitor
|
||
|
|
policies in the following ways:</p>
|
||
|
|
<ul><li><span class="uicontrol">To view real-time data on active policies</span> <p>When
|
||
|
|
you open the monitor, real-time data is always displayed on active policies.
|
||
|
|
There is no need to start data collection.</p>
|
||
|
|
</li>
|
||
|
|
<li><span class="uicontrol">To collect and save data over a period of time</span> <p>If
|
||
|
|
you want to save monitor results, then you need to start QoS data collection.
|
||
|
|
The monitor continues to collect data until you stop the collection. Closing
|
||
|
|
the monitor window does not stop the data collection. You can also change
|
||
|
|
the properties that the monitor uses when collecting data. On the QoS Monitor
|
||
|
|
window, highlight <em>QoS monitor</em> and select <em>File-->Properties</em> to
|
||
|
|
change your options. Use the online help for additional information.</p>
|
||
|
|
<p>If
|
||
|
|
QoS data collection is turned on and monitor properties are changed, then
|
||
|
|
you must perform the following steps to ensure that the changes are reflected
|
||
|
|
in data collection.</p>
|
||
|
|
<ol><li>Stop QoS Data Collection.</li>
|
||
|
|
<li>Change monitor properties. <ol type="a"><li>In the Monitor window, click <span class="uicontrol">QoS Monitor</span>.</li>
|
||
|
|
<li>Select <span class="menucascade"><span class="uicontrol">File</span> > <span class="uicontrol">Properties</span></span>.</li>
|
||
|
|
<li>Change the monitor properties and click <span class="uicontrol">OK</span>.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li>Update the QoS Server.</li>
|
||
|
|
<li>Start QoS Data Collection.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Monitor output</h4><p>The output information you receive
|
||
|
|
depends on the type of policy you are monitoring. Remember the types of policies:
|
||
|
|
DiffServ, IntServ (Controlled Load), IntServ (Guaranteed), and Inbound admission.
|
||
|
|
The fields to evaluate depend on the policy type. The most interesting values
|
||
|
|
are the values that show a measurement. The following fields are measured
|
||
|
|
rather than given a definition: accepted requests, active connections, connections
|
||
|
|
services, connection rates, dropped requests, in-profile packets, in-profile
|
||
|
|
bits, out-of-profile bits, total bits, total packets, and total requests.</p>
|
||
|
|
<p>By
|
||
|
|
reading information from the measured fields above, you can form a good picture
|
||
|
|
of how your network traffic is conforming to your policies. Use the descriptions
|
||
|
|
below for more detailed information about the monitor output field for each
|
||
|
|
policy type. See any of the QoS scenarios for a sample of how to use the monitor
|
||
|
|
along with the QoS policies.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rzak8monitoring__diff"><a name="rzak8monitoring__diff"><!-- --></a><h4 class="sectiontitle">Differentiated service policies</h4>
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. Differentiated
|
||
|
|
service policies</caption><thead align="left"><tr><th valign="top" width="50%" id="d0e117">Field</th>
|
||
|
|
<th valign="top" width="50%" id="d0e119">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="50%" headers="d0e117 ">Policy name</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The name you assigned to this policy.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Protocol</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">UDP, TCP, ALL</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Average token rate limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The average token rate allowed by this policy in each router and server
|
||
|
|
along the flow path.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Token depth limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The maximum token buffer size allowed by this policy in each router
|
||
|
|
and server along the flow path.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Peak token rate limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The maximum rate allowed by this connection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Packets in-profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The number of transmitted IP packets that fit within this policy's
|
||
|
|
parameters.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Bits in-profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The number of transmitted bits that fit within this policy's parameters.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Bits out-of-profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The number of transmitted bits that exceed the policy's parameters.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Bits rate</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The measured number of bits permitted by this connection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Active connections</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The total number of active connections.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Traffic profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 "><p>The type of packet conditioning used on out-of-profile packets.
|
||
|
|
Format might include:</p>
|
||
|
|
<ul><li>Re-marking</li>
|
||
|
|
<li>Shaping</li>
|
||
|
|
<li>Dropping</li>
|
||
|
|
</ul>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Bits total</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The number of transmitted bits used by this policy from the time it
|
||
|
|
was started to the time of the monitor collection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Codepoint in-profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">If the packet is remarked with a new codepoint, this is the codepoint
|
||
|
|
which IP packets will use if they fit within this policy's parameters.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Codepoint out-of-profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">If the packet is remarked with a new codepoint, this is the codepoint
|
||
|
|
which the IP packets will use if they exceed the policy's parameters.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Destination address range</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The address range which determines the packets' (controlled by this
|
||
|
|
policy)destination point.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Packet total</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The number of packets transmitted by this policy from the time the
|
||
|
|
policy started to the time of the monitor collection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e117 ">Source port range</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e119 ">The source port range which determines which applications are controlled
|
||
|
|
by this policy.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rzak8monitoring__int"><a name="rzak8monitoring__int"><!-- --></a><h4 class="sectiontitle">Integrated service (controlled load) policies</h4><p>IntServ
|
||
|
|
policies do not display in the monitor until the applications are running
|
||
|
|
and reservations have been established. If your IntServ policies have more
|
||
|
|
than one reservation, you will see multiple entries in the monitor.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 2. Integrated service (controlled load) policies</caption><thead align="left"><tr><th valign="top" width="50%" id="d0e229">Field</th>
|
||
|
|
<th valign="top" width="50%" id="d0e231">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="50%" headers="d0e229 ">Policy name</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The name you assigned to this policy.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Protocol</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">UDP or TCP</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Destination address</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The address range which determines the packets' (controlled by this
|
||
|
|
policy)destination point.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Average token rate limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The average token rate allowed by this policy in each router and server
|
||
|
|
along the connection path.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Token depth limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The maximum token buffer size allowed by this policy in each router
|
||
|
|
and server along the connection path.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Peak token rate limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The maximum rate allowed by this connection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Packet total</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The number of packets transmitted by this policy from the time the
|
||
|
|
policy started to the time of the monitor collection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Bits out-of-profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The number of transmitted bits that exceed the policy's parameters.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Bits total</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The number of transmitted bits used by this policy from the time it
|
||
|
|
was started to the time of the monitor collection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Bit rate</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The measured number of bits permitted by this connection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Bits in-profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The number of transmitted bits that fit within this policy's parameters.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Maximum packet size</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The maximum allowed packet size controlled by this policy.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Minimum policed unit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The smallest number of bits that will be removed from the token bucket.
|
||
|
|
For example, if your minimum policed unit is 100 bits, packets under 100 bits
|
||
|
|
will still be removed at 100 bits.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Packets in-profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The number of transmitted IP packets that fit within this policy's
|
||
|
|
parameters.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e229 ">Source port range</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e231 ">The source port range which determines which applications are controlled
|
||
|
|
by this policy.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rzak8monitoring__intdiff"><a name="rzak8monitoring__intdiff"><!-- --></a><h4 class="sectiontitle">Integrated service (guaranteed) policies</h4><p>IntServ
|
||
|
|
policies do not display in the monitor until the applications are running
|
||
|
|
and reservations have been established. If your IntServ policies have more
|
||
|
|
than one reservation, you will see multiple entries in the monitor.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 3. Integrated service (guaranteed) policies</caption><thead align="left"><tr><th valign="top" width="50%" id="d0e322">Field</th>
|
||
|
|
<th valign="top" width="50%" id="d0e324">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="50%" headers="d0e322 ">Policy name</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The name you assigned to this policy.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Protocol</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">UDP or TCP</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Destination address</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The address range which determines the packets' (controlled by this
|
||
|
|
policy)destination point.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Average token rate limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The maximum token rate allowed by this policy in each router and server
|
||
|
|
along the connection path.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Token depth limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The maximum token buffer size allowed by this policy in each router
|
||
|
|
and server along the connection path.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Peak token rate limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The maximum rate allowed by this connection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Packet total</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The number of packets transmitted by this policy from the time the
|
||
|
|
policy started to the time of the monitor collection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Bits total</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The number of transmitted bits used by this policy from the time it
|
||
|
|
was started to the time of the monitor collection.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Bits out-of-profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The number of transmitted bits that exceed the policy's parameters.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Guaranteed rate</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The guaranteed rate in bits per second.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Bits in-profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The number of transmitted bits that fit within this policy's parameters.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Maximum packet size</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The maximum allowed packet size controlled by this policy.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Minimum policed units</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The smallest number of bits that will be removed from the token bucket.
|
||
|
|
For example, if your minimum policed unit is 100 bits, packets under 100 bits
|
||
|
|
will still be removed at 100 bits.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Packets in-profile</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The number of transmitted IP packets that fit within this policy's
|
||
|
|
parameters.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Slack term</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The difference (in seconds) between the required delay and the delay
|
||
|
|
obtained.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e322 ">Source port range</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e324 ">The source port range which determines which applications are controlled
|
||
|
|
by this policy.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rzak8monitoring__connect"><a name="rzak8monitoring__connect"><!-- --></a><h4 class="sectiontitle">Inbound admission policies</h4>
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 4. Inbound
|
||
|
|
admission policies</caption><thead align="left"><tr><th valign="top" width="50%" id="d0e418">Field</th>
|
||
|
|
<th valign="top" width="50%" id="d0e420">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="50%" headers="d0e418 ">Policy name</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The name you assigned to this policy.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Connection rate</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The number of connection requests accepted per second.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Total requests</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The total number of connection requests made to this server.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Accepted requests</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The total number of connection requests accepted by this server.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Dropped requests</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The total number of requests dropped by this server.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Average connection rate limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The average allowable number of new connection requests admitted per
|
||
|
|
second.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Connection burst limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The maximum number of new connection requests accepted concurrently.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Peak connection rate limit</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The maximum allowable rate at which the server will accept connections
|
||
|
|
from the network.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Priority</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The priority assigned to each rule loaded in the QoS Manager.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Queue Priority</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The priority assigned to incoming connections placed in the listen
|
||
|
|
queue.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Destination port range</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The port range or port to which traffic is destined on your server.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Interface address</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">IP address of system interface being monitored.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Source address range</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The IP address range of the clients sending requests to your server.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e418 ">Uniform Resource Identifier (URI)</td>
|
||
|
|
<td valign="top" width="50%" headers="d0e420 ">The identity of the URI being policed.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak8administration.htm" title="You can use these procedures to manage existing quality of service (QoS) properties and policies.">Manage QoS</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzak8example_1.htm" title="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.">Scenario: Limit browser traffic</a></div>
|
||
|
|
<div><a href="rzak8example_4.htm" title="If you are using a virtual private network (VPN), you can still create quality of service (QoS) policies. This example shows the two being used together.">Scenario: Secure and predictable results (VPN and QoS)</a></div>
|
||
|
|
<div><a href="rzak8scenario_5.htm" title="If you need to control the inbound connection requests made to your server, use an inbound admission policy.">Scenario: Limit inbound connections</a></div>
|
||
|
|
<div><a href="rzak8example_3.htm" title="If you need predictable delivery and still need to request a reservation, you also use an integrated service policy. This example uses a controlled load service.">Scenario: Predictable B2B traffic</a></div>
|
||
|
|
<div><a href="rzak8example_2.htm" title="If you need dedicated delivery and want to request a reservation, you use an integrated service policy. There are two types of integrated service policies to create: Guaranteed and controlled load. In this example, guaranteed service is used.">Scenario: Dedicated delivery (IP telephony)</a></div>
|
||
|
|
<div><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><a href="rzak8monitor_server.htm" title="With the quality of service (QoS) monitor, you can verify that the QoS policies are working as you intend them to work.">Monitor server transactions</a></div>
|
||
|
|
<div><a href="rzak8monitor_policy.htm" title="Within the wizards, you are asked to set performance limits. These values cannot be recommended because they are based on individual network requirements.">Scenario: Monitor current network statistics</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|