90 lines
5.7 KiB
HTML
90 lines
5.7 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="Monitor server transactions" />
|
|
<meta name="abstract" content="With the quality of service (QoS) monitor, you can verify that the QoS policies are working as you intend them to work." />
|
|
<meta name="description" content="With the quality of service (QoS) monitor, you can verify that the QoS policies are working as you intend them to work." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8troubleshooting.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8planning.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaie/rzaieaddressports.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8examples.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8monitoring.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="rzak8monitor_server" />
|
|
<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 server transactions</title>
|
|
</head>
|
|
<body id="rzak8monitor_server"><a name="rzak8monitor_server"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Monitor server transactions</h1>
|
|
<div><p>With the quality of service (QoS) monitor, you can
|
|
verify that the QoS policies are working as you intend them to work.</p>
|
|
<p>The QoS monitor can help you in the planning phase and the troubleshooting
|
|
phase of QoS.</p>
|
|
<p>You can use the monitor to analyze your IP traffic through the server.
|
|
This helps you determine where congestion is occurring within your network.
|
|
The QoS monitor can help you continue to monitor your network so you can adjust
|
|
your policies as needed.</p>
|
|
<div class="section"><h4 class="sectiontitle">Planning and maintaining performance</h4><p>One of the
|
|
most difficult parts of implementing QoS is determining what performance limits
|
|
to set in your policies. There is no specific recommendation because every
|
|
network is different. To help you determine what values are right for you,
|
|
you might want to use the monitor before you even start any business-specific
|
|
policies.</p>
|
|
<p>Try to create a differentiated service policy without selecting
|
|
metering to identify how your current network traffic is behaving. Enable
|
|
this policy and start the monitor. The monitor's results can help you tune
|
|
your policies to your specific needs. See a sample monitor policy that will
|
|
identify how your current traffic is behaving.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Troubleshooting performance problems</h4><p>You can also
|
|
use the monitor to troubleshoot problems. Using the monitor output, you can
|
|
determine if the parameters you assigned to a policy are being followed. If
|
|
your policies are appearing in the monitor but do not appear to be affecting
|
|
traffic, do the following verification:</p>
|
|
<ul><li>If the policy is filtering based on a Uniform Resource Identifier (URI),
|
|
verify that Fast Response Cache Accelerator (FRCA) is enabled and configured
|
|
properly. Before you set up an inbound policy that uses URIs, you must ensure
|
|
that the application port assigned for the URI matches the listen directive
|
|
enabled for FRCA in the Apache Web server configuration.</li>
|
|
<li>Verify that the policy schedule. You might be looking for results during
|
|
an inactive time.</li>
|
|
<li>Verify that the port number is correct.</li>
|
|
<li>Verify that the IP address is correct.</li>
|
|
</ul>
|
|
<p>For some examples of monitor output, visit the QoS scenarios or view
|
|
all the monitor fields in monitoring.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzak8troubleshooting.htm" title="Quality of service (QoS) provides several methods to troubleshoot QoS problems.">Troubleshoot QoS</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><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><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>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rzak8monitoring.htm" title="You can use the quality of service (QoS) monitor to analyze your IP traffic through the server.">Monitor QoS</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../rzaie/rzaieaddressports.htm">Manage addresses and ports for your HTTP server (powered by Apache)</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |