126 lines
8.9 KiB
HTML
126 lines
8.9 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="Scenario: Predictable B2B traffic" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8examples.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8scenariodetailsexample3step1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8scenariodetailsexample3step2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8scenariodetailsexample3step3.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8scenariodetailsexample3step4.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8servicetype.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8intserv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8rsvp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8sla.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="rzak8example_3" />
|
||
|
|
<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: Predictable B2B traffic</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak8example_3"><a name="rzak8example_3"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario: Predictable B2B traffic</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<div class="section" id="rzak8example_3__example3situation"><a name="rzak8example_3__example3situation"><!-- --></a><h4 class="sectionscenariobar">Situation</h4><p>The
|
||
|
|
Sales department reports problems that network traffic is not performing as
|
||
|
|
they expected. Your company's iSeries™ server resides in a business-to-business
|
||
|
|
(B2B) environment that requires predictable on demand business service. You
|
||
|
|
need to provide predictable transactions to your customers. You want to give
|
||
|
|
the sales unit a higher quality of service (QoS) for their ordering application
|
||
|
|
during the busiest time of the day (between 10:00 a.m. and 4:00 p.m.).</p>
|
||
|
|
<p>In
|
||
|
|
the following figure, the sales team is within your private network. There
|
||
|
|
are routers, enabled by ReSerVation Protocol (RSVP), along the traffic's path
|
||
|
|
to the B2B client. Each <samp class="codeph">R</samp> represents a router along the traffic's
|
||
|
|
path.</p>
|
||
|
|
<div class="fignone"><span class="figcap">Figure 1. Integrated services policy to a B2B client using RSVP-enabled
|
||
|
|
routers</span><br /><img src="Rzak8503.gif" alt="Integrated services policy
to a B2B client using RSVP-enabled routers" /><br /></div>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rzak8example_3__example3objective"><a name="rzak8example_3__example3objective"><!-- --></a><h4 class="sectionscenariobar">Objectives</h4><p>Controlled
|
||
|
|
load service supports applications that are highly sensitive to congested
|
||
|
|
networks, but are still tolerant to small amounts of loss and delay. If an
|
||
|
|
application uses the controlled load service, its performance will not suffer
|
||
|
|
as network load increases. Traffic will be provided with service resembling
|
||
|
|
normal traffic in a network under light conditions. Because this particular
|
||
|
|
application is tolerant to some delay, you decide to use an integrated services
|
||
|
|
policy using a controlled load service.</p>
|
||
|
|
<p>Integrated service policies
|
||
|
|
also require that, along the traffic's path, the routers are RSVP-enabled.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rzak8example_3__example3prereq"><a name="rzak8example_3__example3prereq"><!-- --></a><h4 class="sectionscenariobar">Prerequisites
|
||
|
|
and assumptions</h4><p>An integrated service policy is an advanced policy
|
||
|
|
that can require substantial resource. Integrated service policies require
|
||
|
|
the following prerequisites:</p>
|
||
|
|
<ul><li><span class="uicontrol">RSVP-enabled applications</span> <p>Because your server
|
||
|
|
does not have any RSVP-enabled applications, you must write your own RSVP-enabled
|
||
|
|
applications. To write your own applications, use the RSVP API, qtoq QoS socket
|
||
|
|
APIs, or integrated service APIs.</p>
|
||
|
|
</li>
|
||
|
|
<li><span class="uicontrol">RSVP-enabled routers and servers along the network path</span> <p>QoS
|
||
|
|
is a network solution. If you are unsure if the entire network has RSVP capabilities,
|
||
|
|
you can still create an integrated service policy and use a marking to give
|
||
|
|
it some priority; however, priority cannot be guaranteed.</p>
|
||
|
|
</li>
|
||
|
|
<li><span class="uicontrol">Service-level agreement</span> <p>You have a service-level
|
||
|
|
agreement (SLA) with your ISP to ensure that the policies receive the requested
|
||
|
|
priority. The QoS policy you create on the iSeries server enables traffic (in the
|
||
|
|
policy) to receive priority throughout the network. The QoS policy does not
|
||
|
|
guarantee the priority and is dependent on your SLA. In fact, taking advantage
|
||
|
|
of QoS policies can give you some leverage to negotiate certain service-levels
|
||
|
|
and rates. Use the service-level agreement link to find out more.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> If
|
||
|
|
you are within a private network, an SLA is not required.</div>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section" id="rzak8example_3__example3config"><a name="rzak8example_3__example3config"><!-- --></a><h4 class="sectionscenariobar">Configuration</h4><p>After
|
||
|
|
you verify the prerequisites steps, you are ready to create the integrated
|
||
|
|
service policy.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ol>
|
||
|
|
<li class="olchildlink"><a href="rzak8scenariodetailsexample3step1.htm">Scenario details: Create the integrated service policy</a><br />
|
||
|
|
</li>
|
||
|
|
<li class="olchildlink"><a href="rzak8scenariodetailsexample3step2.htm">Scenario details: Start or update the QoS server</a><br />
|
||
|
|
</li>
|
||
|
|
<li class="olchildlink"><a href="rzak8scenariodetailsexample3step3.htm">Scenario details: Use the monitor to verify your policy is working</a><br />
|
||
|
|
</li>
|
||
|
|
<li class="olchildlink"><a href="rzak8scenariodetailsexample3step4.htm">Scenario details: Change properties (if needed)</a><br />
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <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="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzak8servicetype.htm" title="There are two integrated service types: controlled load and guaranteed.">Integrated service types</a></div>
|
||
|
|
<div><a href="rzak8intserv.htm" title="The second type of outbound bandwidth policy you can create is an integrated service policy. Integrated service provides the capability for IP applications to request and reserve bandwidth using the ReSerVation Protocol (RSVP) and quality of service (QoS) APIs.">Integrated service</a></div>
|
||
|
|
<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="rzak8sla.htm" title="This topic points out some of the important aspects of a service-level agreement (SLA) that might affect your quality of service (QoS) implementation.">Service-level agreement</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>
|
||
|
|
</body>
|
||
|
|
</html>
|