The content accelerator feature is no longer supported on the NetScaler appliance.
Storing data on a T2100 appliance saves bandwidth and provides faster response times, because the NetScaler does not have to connect to the server for repeated requests of the same data.
When a load balancing or content switching virtual server receives a client request, the NetScaler appliance evaluates a content accelerator policy that you have bound to the virtual server. The policy filters the requests to identify the ones to which to apply the content accelerator feature.
The following figure illustrates the operations that the appliance performs when a client request arrives at a virtual server configured to use the content accelerator feature:
The process flow is as follows:
Client sends request.
NetScaler forwards the request to the server.
Server responds with the predefined size of the response (specified by the accumResSize parameter of the add ca action command).
NetScaler computes a hash of the response sent by the server.
NetScaler looks up the hash on the T2100 appliance.
A successful lookup indicates that the data is available and the T2100 appliance sends the data to the NetScaler.
When a lookup does not succeed, the NetScaler fetches all of the requested data from the server, and simultaneously serves the data to the client and updates the data on the T2100 appliance.
The T2100 appliance can be configured to specify the number of requests after which to cache the data.
NetScaler sends the response to the client.
Before configuring the content accelerator feature, you must enable it on the NetScaler appliance.
You can configure the content accelerator feature to use one or multiple T2100 appliances. You must add each T2100 appliance as a service and bind these services to a load balancing virtual server that is dedicated to distributing the load between the configured T2100 appliances.
You must also configure a content accelerator action to lookup the data on the T2100 appliance. The action must also specify the T2100 load balancing virtual server and the size of data (in KB) to be fetched from the server to calculate the hash.
The action must be bound to a content accelerator policy that defines the traffic on which to perform content acceleration. The content accelerator policy must be bound to a content switching or load balancing virtual server that receives client traffic. Alternatively, you can bind the policy globally to be applicable to all virtual servers.
At the command prompt, do the following:
enable ns feature ca
add service <name> <IPAddress> <serviceType> <port>Example:
> add service T2100-A 10.102.29.61 HTTP 30 > add service T2100-B 10.102.29.62 HTTP 40 > add service T2100-C 10.102.29.63 HTTP 50
add lb vserver <name> <serviceType> <IPAddress> <port> -lbMethod TOKEN -rule "http.req.url.after_str(\"/lookup/\") alt http.req.url.path.SKIP(1).PREFIX(64)"Example:
> add lb vserver T2100-lbvserver HTTP 10.102.29.64 99 -lbMethod TOKEN -rule "http.req.url.after_str(\"/lookup/\") alt http.req.url.path.SKIP(1).PREFIX(64)"
bind lb vserver <name> <serviceName>Example:
> bind lb vserver T2100-lbvserver T2100-A > bind lb vserver T2100-lbvserver T2100-B > bind lb vserver T2100-lbvserver T2100-C
add ca action <name> -accumResSize <KBytes> -lbvserver <string> -type lookupExample:
> add ca action ca_action1 -type lookup -lbvserver T2100-lbvserver -accumResSize 60
add ca policy <name> -rule <expression> -action <name>Example: To create a content accelerator policy that caches all video formats.
> add ca policy ca_mp4_pol -rule ns_video -action ca_action1
where ns_video is a built-in expression.
bind lb vserver <name> -policyName <string>
bind cs vserver <name> -policyName <string>
bind ca global -policyName <string> -priority <num> -type <type>Example: To apply the content accelerator policy to a virtual server named "traf_rec"
> bind lb vserver traf_rec -policyName ca_mp4_polExample: To apply the content accelerator policy for all traffic reaching the NetScaler.
> bind ca global -policyName ca_mp4_pol -priority 100 -type RES_DEFAULT
save ns config