The Routing Page - HP P4535A - Web Cache Server Appliance Administrator's Manual

Appendix B
Option
SOCKS timeout (seconds)
SOCKS List

The Routing page

The following table describes the configuration options on the Routing page.
Option
Parent Caching on/off
Parent Cache
ICP Mode
ICP Port
ICP Multicast enabled
on/off
ICP Query Timeout
ICP Peers
Description
Specifies how long (in seconds) the Traffic Server must wait for the
SOCKS server to respond. If the SOCKS server does not respond within
the amount of time specified, the Traffic Server drops the connection.
Displays a page where you can specify the origin servers to which you
want to connect without going through the SOCKS server. The list of
origin servers is recorded in the
option is off, the Traffic Server does not read this file.
In the IP Range field, you can enter a single IP address, a range of IP
addresses, or a combination of IP addresses and ranges separated by
commas.
NOTE: Any machine not identified in the SOCKS configuration file is
considered to be outside the firewall and the Traffic Server will connect
to it only by going through the SOCKS server.
Description
Parent Caching
Sets HTTP parent caching on so that Traffic Server can participate in an HTTP
cache hierarchy. You can point your Traffic Server at a parent network cache
(either another Traffic Server or a different caching product) to form a cache
hierarchy where a child cache relies upon a parent cache in fulfilling client
requests.
Specifies the identify a parent cache and parent cache port using the following
format:
parent_name:port_number
Server cannot find a requested object in its own cache, it searches the parent
cache before searching the internet. If you want parent failover, you can specify
more than one parent cache:
parent1:port1; parent2:port2
NOTE: the
traffic_manager
numbers less than 1024.
ICP
The following options enable or disable ICP mode:
Only Receive Queries
Send/Receive Queries
Disabled
Specifies the port that you want to use for ICP messages. The default is 3130.
If your Traffic Server has a multicast channel connection to its ICP peers, it can
send ICP messages through multicast if you enable this option.
Specifies the timeout for ICP queries in seconds.
Click this link to view or modify the Traffic Server's ICP hierarchy. For ICP to
work, the Traffic Server must recognize its ICP neighbors (siblings and parents).
Refer to Identifying ICP Peers‚ on page
Traffic Manager Configuration Options
file. If the SOCKS
socks.config
. The port must be dedicated. If the Traffic
process must run as "root" to bind to port
56.
138