Author: buildbot
Date: Tue May 10 11:42:30 2011
New Revision: 789432
Log:
Staging update by buildbot
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/hierachical-caching/index.en.html
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/hierachical-caching/index.en.html
==============================================================================
---
websites/staging/trafficserver/trunk/content/docs/trunk/admin/hierachical-caching/index.en.html
(original)
+++
websites/staging/trafficserver/trunk/content/docs/trunk/admin/hierachical-caching/index.en.html
Tue May 10 11:42:30 2011
@@ -109,11 +109,7 @@ the following steps: </p>
<p><strong>Note:</strong> You need to configure the child cache only. No
additional configuration
is needed for the Traffic Server parent cache. </p>
<h5 id="ConfigureTSuseaparentcache">Configure Traffic Server to use a parent
cache:</h5>
-<p>Edit the following variable in <code>records.config</code> file located in
the Traffic Server <code>config</code> directory. </p>
-<dl>
-<dt><em><code>proxy.config.http.parent_proxy_routing_enable</code></em></dt>
-<dd>Set this variable to 1 to enable the parent caching option.</dd>
-</dl>
+<p>Edit the following variable <a
href="../configuration-files/records.config#proxy.config.http.parent_proxy_routing_enable"><em><code>proxy.config.http.parent_proxy_routing_enable</code></em></a>
in <code>records.config</code> file.</p>
<p>Edit the <a
href="../configuration-files/parent.config"><code>parent.config</code></a> file
located in the Traffic Server <code>config</code> directory to set
parent proxy rules to specify the parent cache to which you want missed
requests to be forwarded;</p>
<p>The following example configures Traffic Server to route all requests
containing the regular expression <code>politics</code>
@@ -161,20 +157,13 @@ must perform the following tasks: </p>
<li>Identify the ICP peers (siblings and parents) with which Traffic Server
can communicate.</li>
</ul>
<h5 id="configureTSuseanICPcachehierarchy">To configure Traffic Server to use
an ICP cache hierarchy:</h5>
-<p>Edit the following variables in <code>records.config</code> file located in
the Traffic Server <code>config</code> directory. </p>
-<dl>
-<dt><em><code>proxy.config.icp.enabled</code></em></dt>
-<dd>0 disables ICP.</dd>
-<dd>1 allows Traffic Server to receive ICP queries only</dd>
-<dd>2 allows Traffic Server to send and receive ICP queries.</dd>
-<dt><em><code>proxy.config.icp.icp_port</code></em></dt>
-<dd>This variable specifes the UDP port that you want to use for ICP messages
(default is 3130).</dd>
-<dt><em><code>proxy.config.icp.multicast_enabled</code></em></dt>
-<dd>0 disables ICP multicast.</dd>
-<dd>1 enables ICP multicast.</dd>
-<dt><em><code>proxy.config.icp.query_timeout</code></em></dt>
-<dd>This variable specifes the timeout used for ICP queries (default is 2
seconds).</dd>
-</dl>
+<p>Edit the following variables in <a
href="../configuration-files/records.config"><code>records.config</code></a>
file:</p>
+<ul>
+<li><a
href="../configuration-files/records.config#proxy.config.icp.enabled"><em><code>proxy.config.icp.enabled</code></em></a></li>
+<li><a
href="../configuration-files/records.config#proxy.config.icp.port"><em><code>proxy.config.icp.icp_port</code></em></a></li>
+<li><a
href="../configuration-files/records.config#proxy.config.icp.multicast_enabled"><em><code>proxy.config.icp.multicast_enabled</code></em></a></li>
+<li><a
href="../configuration-files/records.config#proxy.config.icp.query_timeout"><em><code>proxy.config.icp.query_timeout</code></em></a></li>
+</ul>
<p>Edit <code>icp.config</code> file located in the Traffic Server
<code>config</code> directory:
For each ICP peer you want to identify, enter a separate rule in the <a
href="../configuration-files/icp.config">icp.config</a> file.</p>
<p>Run the command <code>traffic_line -x</code> to apply the configuration
changes.</p>
