77 lines
5.6 KiB
HTML
77 lines
5.6 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="Integrated service using differentiated service markings" />
|
||
|
|
<meta name="abstract" content="Use differentiated service markings in an integrated service policy to maintain priority of packets sent in a mixed environment." />
|
||
|
|
<meta name="description" content="Use differentiated service markings in an integrated service policy to maintain priority of packets sent in a mixed environment." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8intserv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8cos.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzak8intserv.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="rzak8markings" />
|
||
|
|
<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>Integrated service using differentiated service markings </title>
|
||
|
|
</head>
|
||
|
|
<body id="rzak8markings"><a name="rzak8markings"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Integrated service using differentiated service markings </h1>
|
||
|
|
<div><p>Use differentiated service markings in an integrated service policy
|
||
|
|
to maintain priority of packets sent in a mixed environment.</p>
|
||
|
|
<p>A mixed environment occurs when an integrated service reservation travels
|
||
|
|
through different routers that do not support integrated service reservations
|
||
|
|
but do support differentiated service. Because your traffic passes through
|
||
|
|
different domains, service-level agreements, and equipment capabilities, you
|
||
|
|
might not always get the service you intend.</p>
|
||
|
|
<p>To help alleviate this potential problem, you can attach a differentiated
|
||
|
|
service marking to your integrated service policy. In the event that a policy
|
||
|
|
crosses a router that cannot use the ReSerVation Protocol (RSVP), your policy
|
||
|
|
will still maintain some priority. The marking you add is called a per-hop
|
||
|
|
behavior.</p>
|
||
|
|
<div class="section" id="rzak8markings__nosignalling"><a name="rzak8markings__nosignalling"><!-- --></a><h4 class="sectiontitle">No signaling</h4><p>In addition to using
|
||
|
|
markings, you can also use the <em>no-signal</em> function. When you select
|
||
|
|
this function, the no-signal versions of the APIs allow you to write an application
|
||
|
|
that causes an RSVP rule to be loaded on the server and only requires the
|
||
|
|
server-side application of the TCP/IP conversation to be RSVP-enabled. The
|
||
|
|
RSVP signaling is done automatically on behalf of the client side. This creates
|
||
|
|
the RSVP connection for the application even if the client side is not able
|
||
|
|
to use RSVP.</p>
|
||
|
|
<p>The no-signal function is specified within the integrated
|
||
|
|
service policy. To designate no signal, perform the following steps:</p>
|
||
|
|
<ol><li>In iSeries™ Navigator,
|
||
|
|
expand your server <span class="menucascade"><span class="uicontrol"></span> > <span class="uicontrol">Network</span> > <span class="uicontrol">IP Policies</span></span>.</li>
|
||
|
|
<li>Right-click <span class="uicontrol">Quality of Service</span> and select <span class="uicontrol">Configuration</span>.</li>
|
||
|
|
<li>Expand <span class="menucascade"><span class="uicontrol">Outbound Bandwidth Policies</span> > <span class="uicontrol">IntServ</span></span>.</li>
|
||
|
|
<li>Right-click the required IntServ policy name and select <span class="uicontrol">Properties</span>.
|
||
|
|
The IntServ Properties window opens.</li>
|
||
|
|
<li>Select the <span class="uicontrol">Traffic Management</span> tab to disable or
|
||
|
|
enable signaling. This is also where you edit the schedule, client, applications,
|
||
|
|
and traffic management.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <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>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzak8cos.htm" title="When you create a differentiated service policy or an inbound admission policy, you also create and use a class of service.">Class of service</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>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|