HP Cache Server Appliance Administrator Guide HP Part Number 5971-3045 Printed in June 2001
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Who should read this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Conventions used in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Blocking particular groups . . . . . . . . . Clustering. . . . . . . . . . . . . . . . . . Transparency . . . . . . . . . . . . . . . . Posting . . . . . . . . . . . . . . . . . . . Maintaining the cache: updates and feeds . Configuring access control . . . . . . . . . Using enhanced NNTP authentication . . . Obeying NNTP control messages . . . . . Client bandwidth throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 7 Hierarchical Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Understanding cache hierarchies . . . . . . . . . . . . . . HTTP cache hierarchies . . . . . . . . . . . . . . . . . . Parent failover . . . . . . . . . . . . . . . . . . . . . . Configuring Traffic Server to use an HTTP parent cache ICP cache hierarchies . . . . . . . . . . . . . . . . . . . . Configuring Traffic Server to use an ICP cache hierarchy .
Contents Controlling access to Traffic Manager . . . . . Setting the administrator ID and password . . Creating a list of administrator accounts . . . Controlling host access to Traffic Manager. . Using SSL for secure administration . . . . . Configuring SOCKS firewall integration . . . . . Setting SOCKS configuration options . . . . Configuring DNS server selection (split DNS). . Configuring LDAP-based proxy authentication . Configuring LDAP Authentication Bypass . . Using SSL Termination . . . . . . . .
Contents The Other page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The MRTG page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 127 B Traffic Manager Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 The Server Basics page. . . . . The Protocols page . . . . . . . The Cache page . . . . . . . . The Security page . . . . . . . . The Routing page . . . . . . .
Contents Example . . . . . . . . . . . . . . . . . . logs.config . . . . . . . . . . . . . . . . . . . Format . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . WELF (WebTrends Enhanced Log Format) log_hosts.config . . . . . . . . . . . . . . . . Format . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . logs_xml.config . . . . . . . . . . . . . . . . Format . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . .
Contents Format . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . Specifying URL Regular Expressions (url_regex). Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 220 220 221 E Event Logging Formats . . . . . . . . . . . . . . . . . . . . .
List of Procedures To verify that Traffic Server is up and running: 8 To access Traffic Manager: 8 To start a Traffic Line session: 10 To enable WCCP 1.0 after Traffic Server installation: 25 To enable WCCP 2.
List of Procedures To set configuration options in Configure mode: 77 To set configuration options in batch mode: 78 To specify the clients allowed to use Traffic Server as a proxy cache: 81 To edit the arm_security.
Preface This manual describes how to use and configure an HP Traffic Server™ system. For information about installing Traffic Server and unsupported features and last minute information not available in this manual, refer to the HP Web Cache Server Appliance (sa2100 or sa2200) Getting Started Guide.
1 Overview Welcome to a faster network. Traffic Server speeds Internet access, enhances web site performance, and delivers unprecedented web hosting capabilities.
Chapter 1 Overview Traffic Server as a web proxy cache As a web proxy cache, user requests for web content go to Traffic Server on the way to the destined web server (origin server). If Traffic Server contains the requested content, it serves it directly. If Traffic Server does not have the requested content, Traffic Server acts as a proxy, fetching the content from the origin server on the user’s behalf, while keeping a copy to satisfy future requests.
Chapter 1 Overview Traffic Server components Traffic Server consists of several components that work together to form a web proxy cache you can easily monitor and configure. The main components are described below. The Traffic Server cache The Traffic Server cache consists of a high speed object database called the object store. The object store indexes objects according to URLs and associated headers.
Chapter 1 • Overview Host reliability and availability information (to avoid making the user wait for non-functional servers) The DNS Resolver Traffic Server includes a fast, asynchronous DNS resolver to streamline conversion of host names to IP addresses. Traffic Server implements the DNS resolver natively, directly issuing DNS command packets, rather than relying on slower, conventional resolver libraries.
Chapter 1 Overview Administration tools Traffic Server offers several administration alternatives to suit the needs of many environments: • Traffic Manager User Interface (UI) is a web based interface consisting of a series of web pages accessible through a browser. Traffic Manager provides a rich set of graphs and statistical displays for monitoring Traffic Server performance and network traffic, and a set of options for configuring and fine-tuning the Traffic Server system.
Chapter 1 Overview • Configure Traffic Server integration into your firewall and control traffic through a SOCKS server. • Configure Traffic Server to use multiple DNS servers to match your site’s security configuration. For example, you might choose to have Traffic Server use different DNS servers depending on whether it needs to resolve host names located inside or outside a firewall.
2 Getting Started You are now ready to begin using Traffic Server. This chapter contains the following sections: • Overview of Access Methods‚ on page 7 • Verifying that Traffic Server is up and running‚ on page 8 • Accessing Traffic Manager‚ on page 8 • Starting Traffic Line‚ on page 10 Overview of Access Methods The instructions in this guide refer to different methods of accessing the functionality of the cache appliance.
Chapter 2 Getting Started Verifying that Traffic Server is up and running When you completed the initial configuration of the cache appliance as described in the HP Web Cache Server Appliance sa2100/sa2200 Getting Started Guide, Traffic Server was automatically started. To verify that Traffic Server is up and running: 1. Access Traffic Manager (refer to Overview of Access Methods‚ on page 7). 2. From the Monitor tab, click the Protocols button. 3.
Chapter 2 Getting Started Traffic Manager opens in your web browser and displays the Dashboard, shown in Figure 2-1. Click the Configure tab to display the Configure buttons and set configuration The Monitor tab contains seven buttons. Click a button to display a page of Click the Help button to display a description of the current page This shows the current user logged in to Traffic Manager Figure 2-1.
Chapter 2 Getting Started Starting Traffic Line Traffic Line is a text-based interface that can be accessed through a Telnet session. You can use Traffic Line to perform many of the tasks you can perform in Traffic Manager. For ease of use, it is recommended that Traffic Manager be used unless a function only available in Traffic Line is required.
3 Web Proxy Caching The idea behind web proxy caching is to store copies of frequently accessed documents close to users and serve this information to them on demand. Internet users get their information faster and Internet bandwidth is freed up for other tasks. This chapter discusses the following topics. • Understanding web proxy caching‚ on page 11 • News article caching‚ on page 16 Understanding web proxy caching Internet users direct their requests to web servers all over the Internet.
Chapter 3 Web Proxy Caching 5. If the object is not in the cache (a cache miss) or the server indicates that the cached copy is no longer valid, Traffic Server gets the document from the origin server, simultaneously streaming it to the user and the cache (Figure 3-2.). Subsequent requests for the object will be served faster. 3 Traffic Server simultaneously caches origin and serves the document to the client 1 request miss local Traffic Server server cache 2 a cache miss client Figure 3-2.
Chapter 3 Web Proxy Caching HTTP object freshness tests Here is how Traffic Server determines an HTTP document’s freshness: Expires header test. Some documents come with Expires headers or max-age headers that explicitly define how long the document may be cached. A simple comparison of the current time with the expiration time tells Traffic Server whether or not the document is fresh. Last-Modified / Date header test.
Chapter 3 Web Proxy Caching Traffic Server applies Cache-Control servability criteria after HTTP freshness criteria. For example, a document might be considered fresh, but if its age is greater than its max-age, it is not served. Configuring HTTP freshness options You can configure the following freshness guidelines for Traffic Server: • How often to revalidate (when to consider objects stale). See Configuring HTTP revalidation‚ on page 14. • Whether to cache documents without freshness information.
Chapter 3 Web Proxy Caching Alternates are identified by header information. You can configure Traffic Server to cache all alternates according to a particular header. For example, if you tell Traffic Server to vary on the User-Agent header, Traffic Server caches all the different user-agent versions of documents it encounters. You configure the caching of alternates in the Variable Content section of the Cache page in Traffic Manager’s Configure mode. To cache or not to cache?.
Chapter 3 Web Proxy Caching Scheduling updates to local cache content To further increase the performance of Traffic Server, you can configure it to perform scheduled updates to the local cache content. This enables you to instruct Traffic Server to explicitly load specific objects into cache. You might find this especially beneficial when using Traffic Server as a reverse proxy for server acceleration, enabling you to preload content that you anticipate will be in demand.
Chapter 3 Web Proxy Caching Traffic Server provides many configurable options for supporting parent NNTP servers. The following sections describe Traffic Server’s NNTP features. Traffic Server as a news server When clients want to read news, they access a news server. The news server offers a list of groups to which clients can subscribe. For each subscribed group, the clients read an overview list of the articles in the group, and then select an article to read.
Chapter 3 • Web Proxy Caching Background retries Failed servers are retried in the background and are used (restored to their specified priority) when they become available. Several servers supplying different groups Several news servers can be configured with news servers supplying different (disjoint) groups. Administrators can use this feature to spread the load based on group.
Chapter 3 Web Proxy Caching Transparency NNTP traffic bound for a well known NNTP server can be intercepted transparently by Traffic Server. By transparently intercepting, caching, and serving the NNTP data from a centralized parent news server, Traffic Server simplifies migration and administration while increasing responsiveness and decreasing network utilization. Transparency mode is installed by default during Traffic Server installation.
Chapter 3 • Web Proxy Caching Take a full feed for some or all groups For all groups designated as feed, Traffic Server does not connect to the parent news server, and instead acts like a conventional news server. In particular, if a cache miss occurs, Traffic Server does not forward the request to a parent news server. Full feeds can be used for very high volume groups in which most or all the articles are accessed or for shifting article transport to a time when bandwidth is cheaper or more plentiful.
Chapter 3 Web Proxy Caching Obeying NNTP control messages The Traffic Server default setup for nonfeed news groups is to periodically check the parent server for new groups, cancelled articles, and new articles. If you have enabled these periodic checks in the Configure: Protocols page, you do not need to enable obeying control messages. Traffic Server can be configured to obey NNTP control messages.
4 Transparent Proxy Caching The transparency option enables Traffic Server to respond to Internet requests without requiring users to reconfigure their browser settings. This chapter discusses the following topics.
Chapter 4 Transparent Proxy Caching Interception strategies Routing solutions enable transparent interception of Internet requests. The transparency routing solutions supported by Traffic Server are: • A Layer 4 switch. See “Using a layer 4 switch with cache switching functionality to filter transparency requests” on page 23. • A Cisco IOS-based router using the Web Cache Control Protocol (WCCP). See Using a WCCP-enabled router for transparency‚ on page 24. • Policy-based routing.
Chapter 4 Transparent Proxy Caching Layer 4 switches offer the following features, depending on the particular switch: • A Layer 4 switch that can sense downed hosts on the network and redirect traffic adds reliability. • If a single Layer 4 switch feeds several Traffic Servers, the switch handles load balancing among the Traffic Server nodes. Different switches might use different load balancing methods, such as round-robin or hashing.
Chapter 4 Transparent Proxy Caching WCCP provides the following routing benefits: • The WCCP-enabled router and Traffic Server exchange heartbeat messages, letting each other know they are running. The WCCP router automatically reroutes port 80 traffic (and port 119 traffic in WCCP 2.0) if the Traffic Server goes down. • If several Traffic Servers receive traffic from a WCCP router, WCCP balances the load among the Traffic Servers. The group of Traffic Servers is called a WCCP cache farm.
Chapter 4 Transparent Proxy Caching To enable WCCP 2.0 after installation: 1. Telnet into the HP web cache appliance and select Shell Access as described in Overview of Access Methods‚ on page 7. 2. Open the records.config file located in the Traffic Server’s config directory with Vi. 3. Set the following variable to 1: proxy.config.wccp.enabled INT 1 4. Set the following variable to 2: proxy.config.wccp.
Chapter 4 Transparent Proxy Caching About WCCP load balancing If a WCCP router serves several nodes, as in Figure 4-2‚ on page 24 the router balances load among the Traffic Servers. The router sends each node requests aimed at a particular range of IP addresses, so that each node is responsible for caching content residing at particular IP addresses. You can monitor the percentage of traffic that goes to each node. If a node becomes unavailable, its traffic is redistributed.
Chapter 4 Transparent Proxy Caching A Traffic Server cluster with virtual IP failover adds reliability; if one node fails, another node can take up its transparency requests. See Virtual IP failover‚ on page 47. world wide web router end users non80 non port:80 traffic all 80 port:80 traffic Traffic Server Figure 4-3. Using a router to filter HTTP requests Interception bypass A very small number of clients and servers do not interoperate correctly with web proxies.
Chapter 4 Transparent Proxy Caching NOTE Do not confuse bypass rules with client access control lists. Bypass rules are generated in response to interoperability problems. Client access control is simply restriction of the client IP addresses that can access the Traffic Server cache as described in Controlling client access to the Traffic Server proxy cache‚ on page 81.
Chapter 4 Transparent Proxy Caching Variable Description proxy.config.arm.bypass_dynamic_enabled Set this variable to 1 to enable dynamic bypass. proxy.config.arm.bypass_use_and_rules_bad_client_request Set this variable to 1 to enable dynamic source/ destination bypass in the event of non-HTTP traffic on port 80. proxy.config.arm.bypass_use_and_rules_400 Set this variable to 1 to enable dynamic source/ destination bypass when an origin server returns a 400 error. proxy.config.arm.
Chapter 4 Transparent Proxy Caching IMPORTANT For a dynamic source/destination bypass rule to work, you must also enable the equivalent destination bypass rule. For example, when you set the variable proxy.config.arm.bypass_use_and_rules_403 to 1, you must also set the variable proxy.config.arm.bypass_on_403 to 1. 4. Save and close the records.config file. 5.
Chapter 4 Transparent Proxy Caching Static bypass rules In addition to adaptively learning what to bypass, Traffic Server allows you to manually configure bypass rules to direct requests from certain clients or to particular origin servers around Traffic Server. For example, you might want client IP addresses that did not pay for a caching service to be steered around the cache, while paying clients can obtain the benefits of caching.
5 Reverse Proxy and HTTP Redirects As a reverse proxy cache, Traffic Server serves requests on behalf of origin servers. Traffic Server is configured in such a way that it appears to clients like a normal origin server. Using HTTP redirects, Traffic Server routes HTTP requests automatically without contacting the origin server.
Chapter 5 Reverse Proxy and HTTP Redirects requests for www.janes_books.com and jazz.flute.org resolve to virtual IP of Traffic Server web world wide web server Traffic Server serves documents on behalf of real.janes_books.com and big.server.net Traffic Server web real.janes_books.com server big.server.net hosts jazz.flute.org Figure 5-1.
Chapter 5 Reverse Proxy and HTTP Redirects HTTP Reverse Proxy In forward proxy caching, Traffic Server acts as a proxy server and receives proxy requests. In reverse proxy caching, because Traffic Server is advertised as the origin server, Traffic Server needs to act as an origin server rather than a proxy server, meaning that it receives server requests, not proxy requests. To satisfy proxy requests, Traffic Server must construct a proxy request from the server request.
Chapter 5 Reverse Proxy and HTTP Redirects Using mapping rules Traffic Server uses two types of mapping rules for HTTP reverse proxy: • A map rule translates the URL in client requests into the URL where the content is located (refer to “Map rules,” below) • A reverse-map rule translates the URL in origin server redirect responses to point to the Traffic Server so that clients are redirected to Traffic Server instead of accessing an origin server directly (refer to “Reversemap rules,” below) Both map
Chapter 5 Reverse Proxy and HTTP Redirects 3. In the Mapping/Redirection section of the Routing page, click the Edit Mapping Rules link. The Routing: URL Rewriting page opens. 4. Click the Add Entry button. The Add Entry page opens (shown below). 5. From the Type field, select the type of rule you want to set (map or reverse_map). 6. In the Target field, enter the origin or from URL for the rule. 7. In the Replacement field, enter the destination or to URL for the rule. 8.
Chapter 5 Reverse Proxy and HTTP Redirects The following example shows a map rule that translates all requests for www.x.com to the origin server server.hoster.com: map http://www.x.com/ http://server.hoster.com For more examples of mapping rules, refer to remap.config‚ on page 212. 4. Save and close the remap.config file. 5. Run the following command to apply the configuration changes.
Chapter 5 Reverse Proxy and HTTP Redirects 3. Edit the following variables: Variable Description proxy.config.reverse_proxy.enabled Set this variable to 1 to enable HTTP reverse proxy mode. Set this variable to 0 (zero) to disable HTTP reverse proxy mode. proxy.config.url_remap.pristine_host_hdr Set this variable to 1 to retain the client host header in the request. Set this variable to 0 (zero) if you want Traffic Server to translate the client host header. proxy.config.url_remap.
Chapter 5 Reverse Proxy and HTTP Redirects Configuring FTP Reverse Proxy To use FTP reverse proxy, you must: • Set FTP mapping rules in the ftp_remap.config file. (Refer to Setting FTP Mapping Rules‚ on page 40.) • Enable the FTP reverse proxy option. (Refer to Enabling FTP Reverse Proxy‚ on page 40.) As an optional configuration step, you can modify FTP options (for example, you can change the FTP connection mode and inactivity timeouts). (Refer to Modifying FTP Options‚ on page 41.
Chapter 5 Reverse Proxy and HTTP Redirects 3. Edit the following variables: Variable Description proxy.config.ftp.ftp_enabled Set this variable to 1 to enable FTP on your Traffic Server. This variable must be enabled for Traffic Server to process FTP requests. proxy.config.ftp.reverse_ftp_enabled Set this variable to 1 to enable the FTP reverse proxy option. Set this variable to 0 (zero) to disable the FTP reverse proxy option. NOTE: If this variable is set to 0, but the proxy.config.ftp.
Chapter 5 Reverse Proxy and HTTP Redirects Variable Description proxy.config.ftp.proxy_server_port Set this variable to specify the port used for FTP connections. proxy.config.ftp.min_lisn_port Set this variable to specify the lowest port in the range of listening ports used by Traffic Server for data connections when the FTP client sends a PASV or Traffic Server sends a PORT to the FTP server. proxy.config.ftp.
Chapter 5 Reverse Proxy and HTTP Redirects Variable Description proxy.config.ftp.port_accept_timeout Set this variable to specify the timeout value for a listening data port in traffic server (for PORT, for the FTP server data connection) proxy.config.ftp.share_ftp_server_ctrl_enabled Set this variable to 1 to enable sharing of server control connections among multiple anonymous FTP clients.
Chapter 5 Reverse Proxy and HTTP Redirects To set redirect rules: 1. Telnet into the HP web cache appliance and select Shell Access as described in Overview of Access Methods‚ on page 7. 2. Open the remap.config file located in Traffic Server’s config directory with Vi. 3. For each redirect , enter a mapping rule. Each mapping rule must be on a separate line and must consist of three space-delimited fields: type, target, and replacement. The following table describes the format for each field.
6 Traffic Server Clusters Traffic Server scales from a single node to multiple nodes that form a cluster, allowing you to improve system performance and reliability. This chapter discusses the following topics: • Understanding Traffic Server clusters‚ on page 45 • Changing clustering mode‚ on page 46 • Adding and deleting nodes in a cluster‚ on page 46 • Virtual IP failover‚ on page 47 Understanding Traffic Server clusters A Traffic Server cluster consists of multiple Traffic Server nodes.
Chapter 6 Traffic Server Clusters Changing clustering mode To change clustering mode: 1. Telnet into the HP web cache appliance and select Shell Access as described in Overview of Access Methods‚ on page 7. 2. Open the records.config file located in Traffic Server’s config directory with Vi. 3. Edit the following variable: Variable Description proxy.config.cluster.type Set this variable to: 1 for full-clustering mode. 2 for management-only mode. 3 for no clustering. 4. Save and close the records.
Chapter 6 Traffic Server Clusters 3. Edit the following variables: Variable Description proxy.config.cluster.type Set this variable to: • 1 for full-clustering mode • 2 for management-only mode Clustering modes are described in Understanding Traffic Server clusters‚ on page 45. proxy.config.proxy_name Set this variable to the name of Traffic Server cluster. All nodes in a cluster must use the same name. proxy.config.cluster.
Chapter 6 Traffic Server Clusters Virtual IP failover assures that if a node in the cluster fails, other nodes can assume the failed node’s responsibilities. Traffic Server handles virtual IP failover in the following ways: • The traffic_manager process maintains cluster communication. Nodes automatically exchange statistics and configuration information through multicast communication. If multicast heartbeats are not received from one of the cluster nodes, the other nodes recognize it as down.
Chapter 6 Traffic Server Clusters 5. Click the Make These Changes button. 6. Scroll to the Web Management section of the Server Basics page and click the restart button to restart the traffic_manager process on all the nodes in the cluster. To enable/disable virtual IP addressing manually: 1. Telnet into the HP web cache appliance and select Shell Access as described in Overview of Access Methods‚ on page 7. 2. Open the records.config file located in the Traffic Server’s config directory with Vi. 3.
Chapter 6 Traffic Server Clusters The Add Entry page opens (shown below). 7. In the IP Address field, enter the virtual IP address. 8. In the Device field, enter the network interface name (for example, eth0). 9. In the Subinterface field, enter the subinterface-ID (this is the number between 1 and 255 that the interface uses for the address). 10. Click the Add button. 11. Click the Make these Changes button. 12.
7 Hierarchical Caching Traffic Server can participate in cache hierarchies, where requests not fulfilled in one cache can be routed to other regional caches, taking advantage of the contents and proximity of nearby caches. This chapter discusses the following topics. • Understanding cache hierarchies‚ on page 51 • HTTP cache hierarchies‚ on page 51 • ICP cache hierarchies‚ on page 54 Understanding cache hierarchies A cache hierarchy consists of levels of caches that communicate with each another.
Chapter 7 Hierarchical Caching New York traffic server regional 3 returned document cache hit parent cache 1 request local Baltimore traffic server end user cache miss 2 forwarded request Figure 7-1. An HTTP cache hierarchy in action NOTE If the request is a cache miss on the parent, the parent retrieves the content from the origin server (or from another cache depending on the parent’s configuration).
Chapter 7 Hierarchical Caching 3. Scroll to the Parent Caching section of the Routing page (shown below). 4. Select Parent Caching: On. 5. Click the Make These Changes button. To enable HTTP parent caching manually: 1. Telnet into the HP web cache appliance and select Shell Access as described in Overview of Access Methods‚ on page 7. 2. Open the records.config file located in Traffic Server’s config directory with Vi. 3. Edit the following variable: Variable Description proxy.config.http.
Chapter 7 Hierarchical Caching parent_name:port_number; parent_name:port_number; NOTE When you use Traffic Manager to identify parent caches for parent failover, Traffic Server sends requests to the parents in the order that they appear in the Parent Cache field. For example, when the first parent cache listed in the Parent Cache field is not available, Traffic Server sends requests to the next parent cache in the list.
Chapter 7 Hierarchical Caching To set ICP options from Traffic Manager: 1. Access Traffic Manager from your browser (refer to Accessing Traffic Manager‚ on page 8). 2. On the Configure tab, click the Routing button. 3. Scroll to the ICP section of the Routing page (shown below) 4. In the ICP mode area, select: o Only Receive Queries to configure Traffic Server to receive ICP queries from other ICP peers only. In this mode, Traffic Server cannot send queries to other ICP peers.
Chapter 7 Hierarchical Caching Variable Description proxy.config.icp.multicast_enabled Set this variable to: • 0 to disable ICP multicast. • 1 to enable ICP multicast. proxy.config.icp.query_timeout Set this variable to specify the timeout used for ICP queries. The default is 2 seconds. 4. Save and close the records.config file. 5. Run the following command to apply the configuration changes.
Chapter 7 Hierarchical Caching 7. From the Type drop-down list, select: o Parent to indicate that the ICP peer is a parent cache. o Sibling to indicate that the ICP peer is a sibling cache. 8. In the Proxy Port field, enter the TCP port used by the ICP peer for ICP communication. This is the Traffic Server’s proxy port (usually 8080). 9. In the ICP Port field, enter the UDP port used by the ICP peer for ICP communication (usually 3130). 10.
Chapter 7 Hierarchical Caching Field Description MC_IP Specifies the multicast IP address. MC_TTL Specifies one of the following options: 1 if you do not want IP multicast datagrams to 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). 4. Save and close the icp.config file. 5. Run the following command to apply the configuration changes.
8 Configuring the cache The Traffic Server cache consists of a high speed object database called the object store that indexes objects according to URLs and associated headers. This chapter discusses the following topics: • The Traffic Server Cache‚ on page 59 • Clearing the cache‚ on page 62 • Partitioning the cache‚ on page 59 • Partitioning the cache‚ on page 59 The Traffic Server Cache The Traffic Server cache consists of a high speed object database called the object store.
Chapter 8 Configuring the cache Creating cache partitions for specific protocols You can create separate partitions for your cache that vary in size to store content according to protocol. This configuration ensures that a certain amount of disk space is always available for a particular protocol. To partition the cache according to protocol: 1. Telnet into the HP web cache appliance and select Shell Access as described in Overview of Access Methods‚ on page 7. 2. Run the stop_traffic_server command. 3.
Chapter 8 Configuring the cache Partitioning the cache according to origin server or domain After you have partitioned the cache according to size and protocol, you can assign the partitions you created to specific origin servers and/or domains. You can assign a partition to a single origin server or multiple origin servers. However, if a partition is assigned to multiple origin servers, there is no guarantee on the space available in the partition for each origin server.
Chapter 8 Configuring the cache In the following example, content from the domain hp.com is stored on partition 1 and 2, while content from www.yahoo.com is stored on partition 3. domain=hp.com partition=1,2 hostname=www.yahoo.com partition=3 NOTE If you want to allocate more than one partition to an origin server or domain, you must enter the partitions in a comma-separated list on one line as shown in the above example. The file cannot contain multiple entries for the same origin server or domain. 5.
9 Monitoring Traffic Traffic Server provides several options for monitoring system performance and analyzing network traffic.
Chapter 9 Monitoring Traffic where nodename is the name of the web cache appliance and adminport is the number assigned to Traffic Manager port, port 8081 by default. NOTE Use the SSL https command to reach Traffic Manager only if you have restricted access to Traffic Manager via SSL connections; otherwise, use the standard http command. Traffic Manager displays the Monitor tab (shown below).
Chapter 9 Monitoring Traffic Figure 9-1. shows the Dashboard. Click this link to see more information about the selected node Lists the nodes in the cluster. Select the node whose statistics you want to view. The selected node appears in black without underlining. The other nodes appear in blue as hypertext links.
Chapter 9 Monitoring Traffic The Graphs button Click the Graphs button to view the same statistics displayed on the Node page (cache performance, current connections and transfers, network, and name resolution) in graphical format. You can display multiple statistics in one graph. To display a single graph, click the graph’s name in the list. Each graph’s name appears as a link (The graphs that display are the same graphs that display when you click a link for a statistic on the Node page).
Chapter 9 Monitoring Traffic The MRTG button Displays MRTG (Multi Router Traffic Grapher) graphs, which enable you to monitor Traffic Server performance and network traffic. Refer to Using MRTG‚ on page 70. Working with Traffic Manager Alarms Traffic Server signals an alarm when it detects a problem (for example, if the traffic_server process shuts down, if the space allocated to event logs is full, or if Traffic Server cannot write to a configuration file).
Chapter 9 Monitoring Traffic Configuring Traffic Server to E-mail alarms Alarm messages are built into Traffic Server, you cannot change them. However, you can write a script file to execute certain actions when an alarm is signaled. For example, if Traffic Server signals an alarm to indicate that the logging directory is full, you can write a script file that sends an E-mail to alert someone of the problem. Traffic Server provides a sample script file named example_alarm_bin.sh.
Chapter 9 Monitoring Traffic The Monitor mode command list appears (shown below). NOTE If the command list does not display, enter ? at the prompt. 4. At the prompt, enter the number that corresponds to the group of statistics you want to view. For example, to view protocol related statistics, enter 3, then press Return. For a description of the type of information listed in each group, refer to Using Monitor mode‚ on page 64.
Chapter 9 Monitoring Traffic Using MRTG MRTG (Multi Router Traffic Grapher) is a graphing tool that enables you to monitor Traffic Server’s performance and analyze network traffic. MRTG provides a variety of graphs that show information about virtual memory usage, client connections, document hit rates, hit and miss rates, and so on. MRTG uses five minute intervals to formulate the statistics and provides useful historical information. You access MRTG from the Monitor tab in Traffic Manager.
Chapter 9 Monitoring Traffic Using SNMP The Simple Network Management Protocol (SNMP) is a standard protocol used for network management. SNMP agents collect and store management information in Management Information Bases (MIBs), and SNMP managers can probe the agents for this information. In addition, SNMP agents can send alarms and alerts called SNMP traps to the SNMP manager to warn of any problems.
Chapter 9 Monitoring Traffic 4. Save and close the records.config file. 5. Run the following command to apply the configuration changes. traffic_line -x Configuring SNMP trap destinations To configure SNMP trap destinations, edit the snmpd.cnf file located in Traffic Server’s config directory. Refer to snmpd.cnf‚ on page 214.
10 Configuring Traffic Server Traffic Server provides several options for configuring the system. This chapter discusses the following topics: • Configuring Traffic Server using Traffic Manager‚ on page 73 • Configuring Traffic Server using Traffic Line‚ on page 76 • Configuring Traffic Server using configuration files‚ on page 78 Configuring Traffic Server using Traffic Manager You can use Traffic Manager to view and change your Traffic Server configuration.
Chapter 10 Configuring Traffic Server Click here to display the Configure mode buttons Click a button to display a page listing configuration options you can modify Click this button to display a description of the configuration options on the current page Shows the current user logged on to Traffic Manager Figure 10-1. Traffic Manager Configure mode buttons Using Configure mode In Configure mode, Traffic Manager displays a series of buttons on the Configure tab.
Chapter 10 • Configuring Traffic Server Configure customizable response pages for HTTP transactions The Protocols button Click the Protocols button to view or change Traffic Server’s protocol configuration.
Chapter 10 Configuring Traffic Server The Logging button Click the Logging page to view or change Traffic Server logging options.
Chapter 10 Configuring Traffic Server The Configure mode command list appears (shown below). If the command list does not display, enter ? at the prompt. Navigating Configure mode Configure mode in a Traffic Line interactive session consists of levels of commands. Each command has a number associated with it. To execute a command, enter its number at the command prompt, then press Return.
Chapter 10 Configuring Traffic Server Setting configuration options in batch mode You can also set configuration options from Traffic Line batch mode. To set configuration options in batch mode: 1. Telnet into the HP web cache appliance and select Shell Access as described in Overview of Access Methods‚ on page 7. 2.
Chapter 10 Configuring Traffic Server The following is a sample portion of the records.config file. The variable value that you can edit The variable name The variable type: an integer (INT), a string, or a floating point (FLOAT) Figure 10-2. A sample records.config file In addition to the records.config file, Traffic Server provides other configuration files that are used to configure specific features. All the configuration files are described in Appendix D‚ Configuration Files.
11 Security Options Traffic Server provides a number of security features.
Chapter 11 Security Options Controlling client access to the Traffic Server proxy cache You can configure Traffic Server to allow only certain clients to use the proxy cache. To specify the clients allowed to use Traffic Server as a proxy cache: 1. Telnet into the HP web cache appliance and select Shell Access as described in Overview of Access Methods‚ on page 7. 2. Open the ip_allow.config file located in Traffic Server’s config directory with Vi.
Chapter 11 Security Options To use the ARM security feature, you must do the following in the order listed: • Edit the arm_security.config file to open specific ports and define the hosts that are allowed to communicate with the Traffic Server machine. IMPORTANT • By default, the arm_security.config file specifies that all ports on the Traffic Server machine are closed (including telnet) except port 8080, which remains open to allow Traffic Server to continue functioning normally.
Chapter 11 Security Options 6. Open the records.config file located in Traffic Server’s config directory with Vi. 7. Edit the following variable: Variable Description proxy.config.arm.security_enabled Set this variable to 1 to enable ARM security. NOTE To disable the ARM security option, set the proxy.config.arm.security_enabled variable to 0 (zero). 8. Save and close the records.config file. 9. Restart Traffic Server.
Chapter 11 Security Options The Security page opens displaying the Control Access to the Traffic Server Manager section (shown below). 3. Select Authentication (basic): On to check the administrator ID and password when a user tries to access Traffic Manager from a browser. When Authentication (basic) is Off, any user can access Traffic Manager unless you have set up a list of IP addresses that are denied access to Traffic Manager (refer to Controlling host access to Traffic Manager‚ on page 86). 4.
Chapter 11 Security Options 3. Edit the following variables: Variable Description proxy.config.admin.basic_auth Set this variable to 1 to enable authentication. proxy.config.admin.admin_password Change the value of this variable to NULL to leave the password blank. 4. Save and close the records.config file. 5. Run the command traffic_line -x to apply the configuration changes. 6. Access Traffic Manager from your browser.
Chapter 11 Security Options 5. In the User field, enter the name of the user allowed to access Traffic Manager. 6. In the Password field, enter the password for the user, then enter the password again in the Password (retype) field. 7. In the Access drop-down list, select which Traffic Manager activities the user can perform: o Select Access Disabled to disable Traffic Manager access for the user. o Select Monitor Only to allow the user to view statistics from the Monitor tab only.
Chapter 11 Security Options 6. Run the command traffic_line -x to apply the configuration changes. Using SSL for secure administration Traffic Server supports the Secure Sockets Layer protocol (SSL) to provide protection for remote administrative monitoring and configuration using Traffic Manager. SSL security provides authentication of both ends of a network connection using certificates and provides privacy using encryption.
Chapter 11 Security Options Accessing Traffic Manager using SSL To access Traffic Manager from your browser using SSL, use the https command as shown below: https://nodename:adminport where nodename is the hostname of the Traffic Server node, and adminport is the port number assigned to Traffic Manager port (the default port number is 8081).
Chapter 11 Security Options Configuring SOCKS firewall integration SOCKS is commonly used as a network firewall that allows hosts behind a SOCKS server to gain full access to the Internet and prevents unauthorized access from the Internet to hosts inside the firewall. Figure 11-1. illustrates how Traffic Server integrates into a SOCKS firewall. Internet SOCKS server Firewall Traffic Server inside a firewall Clients Figure 11-1.
Chapter 11 Security Options 3. Scroll to the Firewall Configuration section (shown below). 4. Select SOCKS: On to enable the SOCKS option. 5. In the SOCKS server IP address field, enter the IP address of your SOCKS server. 6. In the SOCKS server port, enter the port through which Traffic Server communicates with the SOCKS server. 7. In the SOCKS timeout field, enter the number of seconds the Traffic Server must wait for the SOCKS server to respond before dropping the connection.
Chapter 11 Security Options To set SOCKS options manually: 1. Telnet into the HP web cache appliance and select Shell Access as described in Overview of Access Methods‚ on page 7. 2. Open the records.config file located in Traffic Server’s config directory with Vi. 3. Edit the following variables: Variable Description proxy.config.socks.socks_needed Set this variable to 1 to enable SOCKS. proxy.config.socks.socks_server_ip_str Specify the IP address of the SOCKS server. proxy.config.socks.
Chapter 11 Security Options 6. Add rules to the splitdns.config file. For information about the format of the splitdns.config file, see page 217. 7. Save and close the splitdns.config file. 8. Run the command traffic_line -x to apply the configuration changes.
Chapter 11 Security Options 3. Edit the following variables: Variable Description proxy.config.ldap.auth.bypass.enabled Set this variable to 1 to enable LDAP authentication bypass. proxy.config.ldap.auth.multiple.ldap_servers.enabled Set this variable to 1 to allow the sites specified in the ldapsrvr.config file to bypass authentication. 4. Save and close the records.config file. 5. Open the ldapsrvr.config file with Vi. 6. Add bypass sites to the ldapsrvr.config file.
Chapter 11 Security Options Client and Traffic Server connections Figure 11-2. illustrates communication between a client and Traffic Server, and between Traffic Server and an origin server when the SSL termination option is enabled and configured for client/Traffic Server connections only. 1 Client HTTPS request Encrypted secure connection 2 Traffic Server 3 HTTP origin server 1 The client sends an HTTPS request for content.
Chapter 11 Security Options To set SSL termination configuration variables for client/Traffic Server connections: 1. Telnet into the HP web cache appliance and select Shell Access as described in Overview of Access Methods‚ on page 7. 2. Open the records.config file located in Traffic Server’s config directory with Vi. 3. Edit the following variables in the SSL Termination section of the file: Variable Description proxy.config.ssl.enabled Set this variable to 1 to enable the SSL termination option.
Chapter 11 Security Options 4. Save and close the records.config file. 5. Restart Traffic Server using the command start_traffic_server Traffic Server and origin server connections Figure 11-2. illustrates communication between Traffic Server and an origin server when the SSL termination option is enabled for Traffic Server /origin server connections.
Chapter 11 Security Options To set SSL termination configuration variables for Traffic Server/origin server connections: 1. Telnet into the HP web cache appliance and select Shell Access as described in Overview of Access Methods‚ on page 7. 2. Open the records.config file located in Traffic Server’s config directory with Vi. 3. Edit the following variables in the SSL Termination section of the file: Variable Description proxy.config.ssl.auth.
12 Working with Log Files Traffic Server generates log files that contain information about every request it receives and every error it detects.
Chapter 12 Working with Log Files Traffic Server supports several standard log file formats, such as Squid and Netscape, and user-defined custom formats. You can analyze the standard format log files with off-the-shelf analysis packages. To help with log file analysis, you can separate log files so that they contain information specific to protocol or hosts. You can also configure Traffic Server to roll log files automatically at specific intervals during the day.
Chapter 12 Working with Log Files • If the autodelete option (discussed in Rolling event log files‚ on page 109) is enabled, Traffic Server identifies previously rolled log files (log files with a .old extension) and starts deleting files one by one— beginning with the oldest file—until it emerges from the low state. Traffic Server logs a record of all files it deletes in the system error log.
Chapter 12 Working with Log Files 3. Edit the following variables: Variable Description proxy.config.log2.logfile_dir Specify the name and path of the directory in which you want to store event log files. The default is logs located in the directory where you installed Traffic Server. proxy.config.log2.max_space_mb_for_logs Enter the maximum amount of space you want to allocate to the logging directory. proxy.config.log2.max_space_mb_headroom Enter the tolerance for the log space limit. 4.
Chapter 12 Working with Log Files 3. Scroll to the Standard Event Log Formats section of the Logging page (shown below). 4. Click the Enabled:On button for the format you want to use. 5. Select the log file type (ASCII or binary). 6. In the Log file name field, enter the name you want to use for the event log file. 7. In the Log file header field, enter a text header that will display at the top of the event log file. Leave this field blank if you do not want to use a text header. 8.
Chapter 12 Working with Log Files 4. To use the Netscape Common format, edit the following variables: Variable Description proxy.config.log2.common_log_enabled Set this variable to 1 to enable the Netscape Common log file format. proxy.config.log2.common_log_is_ascii Set this variable to 1 to enable ASCII mode. Set this variable to 0 to enable binary mode. proxy.config.log2.common_log_name Enter the name you want to use for Netscape Common event log files. The default is common. proxy.config.log2.
Chapter 12 Working with Log Files Using traditional custom formats To create traditional custom log files, you must enable the traditional custom log format option and edit Traffic Server’s traditional log configuration file (logs.config). You must specify the information you want to display in your log files by entering printf-style format strings. You can create as many custom log file formats as necessary. However, log files consume space quickly, so do not create more than you really need.
Chapter 12 Working with Log Files Field Description file_name Enter a name you want to use for the log file created with this format. type Enter one of the following: • ASCII • BINARY header If you want your custom log file to have header text, enter it here.
Chapter 12 Working with Log Files o The origin servers you want to log (if the servers tag is used, Traffic Server will only log transactions from the origin servers listed, otherwise, transactions from all origin servers are logged). NOTE To generate a custom log file, you must specify at least one LogObject definition. One log file is produced for each LogObject definition. To generate XML-based custom log files: 1.
Chapter 12 Working with Log Files • COUNT • SUM • AVERAGE • FIRST • LAST You can apply each of these operators to specific fields, requesting it to operate over a specified interval. Summary logs represent a trade-off between convenience and information granularity. Since you must specify a time interval during which only a single record is generated, you will necessarily be losing a certain amount of information.
Chapter 12 Working with Log Files Choosing binary or ASCII You can configure the Traffic Server to create event log files in either of the following: • ASCII - these files are human readable and can be processed using standard, off-the-shelf log analysis tools. However, Traffic Server must perform additional processing to create the files in ASCII, resulting is a slight increase in overhead. Also, ASCII files tend to be larger than the equivalent binary files. ASCII log files have a .
Chapter 12 Working with Log Files The following table describes the command-line options: Option Description -o output_file Specifies where the command output is directed. -a Automatically generates the output file name based on the input file name. If the input is from stdin, this option is ignored. For example: logcat -a squid-1.blog squid-2.blog squid-3.blog generates squid-1.log, squid-2.log, squid-3.log -S Attempts to transform the input to Squid format, if possible.
Chapter 12 • Working with Log Files The suffix .old that makes it easy for automated scripts to find rolled log files The time stamps have the following format: %Y%M%D.%Hh%Mm%Ss-%Y%M%D.
Chapter 12 Working with Log Files 3. Scroll to the Log File Rolling section of the Logging page (shown below). 4. Click the Rolling enabled:On button to turn on log file rotation. 5. In the Roll offset hour field, enter the time of day to start the log file rolling. You can enter any hour in the range 0 (midnight) to 23. 6. In the Roll interval field, enter the amount of time Traffic Server enters data in the log files before rotation takes place. You can enter a value between 15 minutes and 24 hours. 7.
Chapter 12 Working with Log Files Splitting event log files By default, Traffic Server uses standard log formats and generates separate log files for HTTP/FTP, NNTP, and ICP transactions. Under most circumstances, this default behavior offers the most flexibility for collecting and analyzing log files. However, you can disable log splitting if you prefer to log all transactions for all protocols in the same log file.
Chapter 12 Working with Log Files If you disable NNTP and ICP log splitting, NNTP and ICP transactions are placed in the same log file as HTTP and FTP transactions. Using the previous example hosts and assuming the Squid log format, Traffic Server generates these log files: Log file name Description squid-uni.edu.log All entries for uni.edu squid-company.com.log All entries for company.com squid.
Chapter 12 Working with Log Files 3. Edit the following variables: records.config Variable Description proxy.config.log2.separate_icp_logs Set this variable to 1 to record all ICP transactions in a separate log file. Set this variable to 0 to record all ICP transactions in the same log file as HTTP/FTP transactions. proxy.config.log2.separate_nntp_logs Set this variable to 1 to record NNTP transactions in a separate log file.
Chapter 12 Working with Log Files Collating event log files You can use Traffic Server’s log file collation feature to keep all logged information in one place. This allows you to analyze Traffic Server as a whole rather than as individual nodes and to use a large disk that may only be located on one of the nodes in a cluster. Traffic Server collates log files by using one or more nodes as log collation servers and all remaining nodes as log collation clients.
Chapter 12 Working with Log Files Collated log files contain time stamp information for each entry, but entries do not appear in the files in strict chronological order. You can sort collated log files before doing analysis. Setting log collation options You can set log collation options by using Traffic Manager or by editing a configuration file manually. Both procedures are provided below. To configure a Traffic Server node to be a collation server from Traffic Manager: 1.
Chapter 12 Working with Log Files 3. Scroll to the Log Collation section of the Logging page (shown below). 4. Click one of the following buttons: o Send standard formats to set the Traffic Server node as a collation client and send the active standard formats (such as Squid and Netscape) to the log collation server. o Send custom non-xml formats to set the Traffic Server node as a collation client and send the custom traditional formats to the log collation server.
Chapter 12 Working with Log Files 3. Edit the following variables: records.config Variable Description proxy.config.log2.collation_host Specify the collation server’s hostname. proxy.config.log2.collation_host_tagged Set this variable to 1 if you want the hostname of the collation client that generated the log entry to be included in each entry. Set this variable to 0 if you do not want the hostname of the collation client that generated the log entry to be included in each entry. proxy.config.log2.
Chapter 12 Working with Log Files The records.config file contains the log collation secret and port you specified when configuring Traffic Server nodes to be collation clients. The collation port and secret must be the same for all collation clients and hosts. 5. Enter the following command: sac -c config_dir where config_dir is the configuration directory in which you copied the records.config file on the stand-alone collator.
A Traffic Manager Statistics This appendix describes the statistics on the following Traffic Manager Monitor pages: • The Dashboard page‚ on page 120 • The Node page‚ on page 121 • The Graphs page‚ on page 121 • The Protocols page‚ on page 122 • The Cache page‚ on page 125 • The Other page‚ on page 126 • The MRTG page‚ on page 127 The Dashboard page The following table describes the statistics on the Dashboard. Statistic/Field Description Node Name The name of the Traffic Server node.
Appendix A Traffic Manager Statistics Statistic/Field Description Node IP Address The IP address assigned to this node. If virtual IP addressing is enabled, several virtual IP addresses could be assigned to this node. Virtual IP Address Mappings If you have configured your Traffic Server system to use virtual IP addresses (refer to Virtual IP failover‚ on page 47), the virtual IP addresses for each node in a cluster display at the bottom of the More Detail page.
Appendix A Traffic Manager Statistics The Protocols page The following table describes the statistics on the Protocols page. Statistic Description HTTP Transaction Frequency and Speeds Hits Fresh The percentage of hits that are fresh and their average transaction times. Stale Revalidated The percentage of hits that are stale and revalidated, turn out to be still fresh and served, and their average transaction times.
Appendix A Traffic Manager Statistics Statistic Description PASV Connections Successes The number of successful PASV connections since installation. PASV Connections Failures The number of PASV connection failures since installation. PORT Connections Successes The number of successful PORT connections since installation. PORT Connections Failures The number of PORT connection failures since installation. NNTP Client Open Connections The number of open NNTP connections.
Appendix A Statistic Traffic Manager Statistics Description Queries Originating From ICP Peers Query Messages Received The number of ICP query messages received from remote ICP peers (siblings and parents). Remote Query Hits The number of successful cache lookups in response to queries from ICP peers. Remote Query Misses The number of unsuccessful cache lookups in response to queries from ICP peers.
Appendix A Traffic Manager Statistics Statistic Description Number of Caches The number of nodes in the WCCP cache farm. Number of Routers The number of WCCP routers sending traffic to the Traffic Server. Router[0] IP address The IP address of the router sending traffic to the Traffic Server. If there is more than one router sending traffic, the IP addresses of all other routers are also listed.
Appendix A Statistic Traffic Manager Statistics Description READS In Progress The number of cache reads in progress (NNTP, HTTP, and FTP). Hits The number of cache reads completed since installation (NNTP, HTTP, and FTP). Misses The number of cache read misses since installation (NNTP, HTTP, and FTP). WRITES In Progress The number of cache writes in progress (NNTP, HTTP, and FTP). Successes The number of successful cache writes since installation (NNTP, HTTP, and FTP).
Appendix A Traffic Manager Statistics Statistic Description Network Backups The number of times this node encountered intracluster network congestion and reverted to proxy-only mode since installation. Clustering Nodes The number of clustering nodes. SOCKS Unsuccessful Connections The number of unsuccessful connections to the SOCKS server since installation. Successful Connections The number of successful connections to the SOCKS server since installation.
B Traffic Manager Configuration Options This appendix describes the configuration options in the following Traffic Manager Configure pages: • The Server Basics page‚ on page 128 • The Protocols page‚ on page 131 • The Cache page‚ on page 135 • The Security page‚ on page 137 • The Routing page‚ on page 138 • The Host Database page‚ on page 139 • The Logging page‚ on page 140 • The Snapshots page‚ on page 143 • The Plugins page‚ on page 143 • The Content Management page‚ on page 143 The Se
Appendix B .com Domain Expansion Traffic Manager Configuration Options Turns .com domain expansion on so that Traffic Server can attempt to resolve unqualified hostnames by redirecting them to the expanded address, prepended with www. and appended with .com. For example, if a client makes a request to hp, the Traffic Server redirects the request to www.hp.com. NOTE: If local domain expansion is set to on, the Traffic Server attempts local domain expansion before .
Appendix B Traffic Manager Configuration Options Throttling of Network Connections Maximum Number of Connections Specifies the maximum number of network connections accepted by the Traffic Server. Setting a throttling limit on the Traffic Server helps to prevent system overload when traffic bottlenecks develop. When network connections reach this maximum, new connections are queued until existing connections close.
Appendix B Control customizable response pages: Traffic Manager Configuration Options Select Turn Off Customizable Response Pages to send the default response pages to clients. Select Enable Default Custom Response Pages to send customized response pages to your clients. You can customize the error message text and format to provide a different look and feel or to explain the errors in a different language.
Appendix B Traffic Manager Configuration Options Option Definition Activity timeout (inbound) Specifies the maximum time the Traffic Server should remain connected to a client. If the client does not finish making a request— reading and writing data—before this timeout expires, the Traffic Server closes the connection. NOTE: The client can close the connection at any time.
Appendix B Traffic Manager Configuration Options Option Definition NNTP option: Clustering Allows cluster-wide NNTP caching. NNTP option: Allow Feeds Allows the Traffic Server to accept feeds of news articles from feed or push groups. CAUTION: If Traffic Server is clustered, configure your news server to send feeds to only one node in the cluster. Feed and push groups are designated in the nntp_servers.config file.
Appendix B Traffic Manager Configuration Options Option Definition Check Pull Groups Every Sets how often the Traffic Server checks pull groups for new articles (and “pulls” the new articles if they exist). The Traffic Server actively pulls (caches) news articles from pull groups, rather than waiting for user requests. Pull groups are designated in the nntp_servers.config file. Authentication Server Host Specifies the name of the host machine running the authentication server.
Appendix B Traffic Manager Configuration Options The Cache page The following table describes the configuration options on the Cache page. Option Description Cache Activation Enable HTTP caching Configures the Traffic Server to cache objects retrieved via HTTP. Enable FTP caching Configures the Traffic Server to cache FTP objects retrieved via HTTP.
Appendix B Traffic Manager Configuration Options Option Description Internet Explorer requests force a check with the origin server Certain versions of Microsoft Internet Explorer do not request cache reloads from reverse proxies and transparent caches when the user presses the browser Refresh button. This can prevent content from being loaded directly from the origin servers.
Appendix B Traffic Manager Configuration Options The Security page The following table describes the configuration options on the Security page. Option Description Control Access to the Traffic Server Manager Authentication (basic) on/off Sets basic authentication on or off. When on, Traffic Server checks the administrator ID and password or user name and password (if administrator accounts have been configured) whenever a user logs on to Traffic Manager.
Appendix B Traffic Manager Configuration Options Option Description SOCKS timeout (seconds) 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. SOCKS List 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 socks.config file.
Appendix B Option Traffic Manager Configuration Options Description Reverse proxy Reverse Proxy Enables or disables HTTP reverse proxy caching mode. For FTP reverse caching mode, refer to FTP Reverse Proxy‚ on page 39. If you enable reverse proxy, Traffic Server is a reverse proxy for the origin servers specified in mapping rules (in the remap.config file). Retain Client Host Header Select Yes to retain the client host header in a request (Traffic Server will not translate the client host header).
Appendix B Traffic Manager Configuration Options Option Description Background timeout Specifies how long DNS entries can remain in the database before they are flagged as entries to refresh in the background. These entries are still fresh, so they can be refreshed after they are served, rather than before. Example: The foreground refresh timeout interval is 24 hours and the background timeout is 12 hours. A client requests an object from my.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
Appendix B Traffic Manager Configuration Options Options Description Log space limit (MB) Specifies the maximum amount of space, in MB, allocated to the logging directory for the log files. NOTE: Transaction logs can consume a lot of space. You should set this limit high enough to accommodate at least a single day's worth of uncompressed transaction logs. Also, make sure that this limit is smaller than the actual space available on the partition that contains the logging directory.
