HP Cache Server Appliance Administrator Guide

168
Appendix D Configuration Files
Each field is described in the following table:
Example
The following example configuration is for 3 nodes: the local host, one parent, and one sibling:
localhost:0.0.0.0:3:8080:3130:0:0.0.0.0:0:
host1:123.12.1.23:1:8080:3131:0:0.0.0.0:0:
host2:123.12.1.24:1:8080:3131:0:0.0.0.0:0:
ip_allow.config
The ip_allow.config file controls client access to the Traffic Server proxy cache. You can specify ranges
of IP addresses that are allowed to use the Traffic Server as a web proxy. If you want to deny Traffic Server
access to specific IP addresses, do not include them in any line in the
ip_allow.config file.
Format
Each line in the ip_allow.config file must have the following format:
src_ip=IPaddress_or_range_of_IPaddresses action=ip_allow
where IPaddress_or_range_of_IPaddresses is the IP address or range of IP addresses of the clients
allowed to access the Traffic Server.
Field Description
host The hostname of the ICP peer. The name localhost is reserved for the Traffic
Server.
host _IP The IP address of the ICP peer.
cache _type Use the following options:
• 1 to indicate an ICP parent cache
• 2 to indicate an ICP sibling cache
• Option 3 is reserved for the local host (the Traffic Server itself).
proxy _port The port number of the TCP port used by the ICP peer for proxy
communication.
icp_port The port number of the UDP port used by the ICP peer for ICP communication.
MC _on Multicast on/off. Use the following options:
• 0 if multicast is not enabled.
• 1 if multicast is enabled.
MC _IP The multicast IP address.
MC _TTL The multicast time to live. Use the following options:
• 1 if IP multicast datagrams will not be forwarded beyond a single
subnetwork
• 2 to allow delivery of IP multicast datagrams to more than one subnet (if
there are one or more multicast routers attached to the first hop subnet)
IMPORTANT After you modify the
ip_allow.config file, Traffic Manager has to reread the
configuration files. Run the
traffic_line -x command. If you are running a
cluster, you need only run the command for one node; the changes will propagate.