58 lines
4.0 KiB
HTML
58 lines
4.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="task" />
|
||
|
|
<meta name="DC.Title" content="Scenario details: Use the monitor to verify your policy is working" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8example_2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8scenariodetailsexample2step2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8scenariodetailsexample2step4.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="rzak8scenariodetailsexample2step3" />
|
||
|
|
<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>Scenario details: Use the monitor to verify your policy is working</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak8scenariodetailsexample2step3"><a name="rzak8scenariodetailsexample2step3"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario details: Use the monitor to verify your policy is working</h1>
|
||
|
|
<div><div class="section">To verify that the policy is working as you configured it to work,
|
||
|
|
do the following steps:</div>
|
||
|
|
<ol><li class="stepexpand"><span>On the quality of service (QoS) Server Configuration
|
||
|
|
window, select <span class="menucascade"><span class="uicontrol">Server</span> > <span class="uicontrol">Monitor</span></span>. The QoS Monitor window appears.</span></li>
|
||
|
|
<li class="stepexpand"><span>Select the IntServ policy type folder. This will display all the
|
||
|
|
IntServ policies.</span> <p>The most interesting fields are the measured
|
||
|
|
fields that obtain their data from your traffic. These fields include the
|
||
|
|
bits total, bits in-profile, and packets in-profile. Bits out-of-profile indicates
|
||
|
|
that other traffic is getting delayed or dropped to satisfy this integrated
|
||
|
|
service policy requirements. See the <a href="rzak8monitoring.htm">Monitor QoS</a> section
|
||
|
|
for a description of all the monitor fields.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> Remember that the results
|
||
|
|
will only be accurate when the policy is active. Verify the schedule you specified
|
||
|
|
within the policy. Also, the monitor only shows IntServ policies after the
|
||
|
|
applications are running. A ReSerVation Protocol (RSVP) reservation has to
|
||
|
|
be established before monitoring.</div>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <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 class="previouslink"><strong>Previous topic:</strong> <a href="rzak8scenariodetailsexample2step2.htm">Scenario details: Start or update the QoS server</a></div>
|
||
|
|
<div class="nextlink"><strong>Next topic:</strong> <a href="rzak8scenariodetailsexample2step4.htm">Scenario details: Change properties (if needed)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|