Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Compression

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (Overview of Compression)
m
 
(6 intermediate revisions not shown)
Line 4: Line 4:
|align="center"|'''Guide Contents'''
|align="center"|'''Guide Contents'''
|-
|-
-
|[[Cisco Application Control Engine (ACE) Troubleshooting Guide|Main Article]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Overview of ACE Troubleshooting|Overview of ACE Troubleshooting]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Understanding the ACE Module Architecture and Traffic Flow|Understanding the ACE Module Architecture and Traffic Flow]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Preliminary ACE Troubleshooting|Preliminary ACE Troubleshooting]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting ACE Boot Issues|Troubleshooting ACE Boot Issues]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting with ACE Logging|Troubleshooting with ACE Logging]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Connectivity|Troubleshooting Connectivity]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Ethernet Ports|Troubleshooting ACE Appliance Ethernet Ports]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Remote Access|Troubleshooting Remote Access]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Access Control Lists|Troubleshooting Access Control Lists]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Network Address Translation|Troubleshooting Network Address Translation]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting ACE Health Monitoring|Troubleshooting ACE Health Monitoring]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Layer 4 Load Balancing|Troubleshooting Layer 4 Load Balancing]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Layer 7 Load Balancing|Troubleshooting Layer 7 Load Balancing]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Redundancy|Troubleshooting Redundancy]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting SSL|Troubleshooting SSL]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Performance Issues|Troubleshooting Performance Issues]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- ACE Resource Limits|ACE Resource Limits]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Managing Resources|Managing ACE Resources]]<br>
+
|[[Cisco Application Control Engine (ACE) Troubleshooting Guide|Main Article]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Overview of ACE Troubleshooting|Overview of ACE Troubleshooting]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Understanding the ACE Module Architecture and Traffic Flow|Understanding the ACE Module Architecture and Traffic Flow]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Preliminary ACE Troubleshooting|Preliminary ACE Troubleshooting]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting ACE Boot Issues|Troubleshooting ACE Boot Issues]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting with ACE Logging|Troubleshooting with ACE Logging]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Connectivity|Troubleshooting Connectivity]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Ethernet Ports|Troubleshooting ACE Appliance Ethernet Ports]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Remote Access|Troubleshooting Remote Access]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Access Control Lists|Troubleshooting Access Control Lists]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Network Address Translation|Troubleshooting Network Address Translation]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting ACE Health Monitoring|Troubleshooting ACE Health Monitoring]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Layer 4 Load Balancing|Troubleshooting Layer 4 Load Balancing]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Layer 7 Load Balancing|Troubleshooting Layer 7 Load Balancing]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Redundancy|Troubleshooting Redundancy]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting SSL|Troubleshooting SSL]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Compression|Troubleshooting Compression]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Troubleshooting Performance Issues|Troubleshooting Performance Issues]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- ACE Resource Limits|ACE Resource Limits]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Managing Resources|Managing ACE Resources]]<br>[[Cisco Application Control Engine (ACE) Troubleshooting Guide -- Show Counter Reference|Show Counter Reference]]<br>
|}
|}
__TOC__
__TOC__
 +
 +
Line 36: Line 38:
== Overview of Compression ==
== Overview of Compression ==
-
You can configure compression by entering the '''compress''' command under a Layer 7 load-balancing policy. For example:
+
Compression is supported on the ACE30 module running software version A4(1.x) and later and on the ACE 4700 series appliance (all software releases). You can configure compression by entering the '''compress''' command under a Layer 7 load-balancing policy. For example:
  class-map type http loadbalance match-any L7default-compression- exclusion-mime-type_CLASS
  class-map type http loadbalance match-any L7default-compression- exclusion-mime-type_CLASS
Line 53: Line 55:
  interface vlan 200
  interface vlan 200
     service-policy L7_COMP_SLB_POLICY
     service-policy L7_COMP_SLB_POLICY
 +
    no shutdown
For compression to work, a client must send a request with an ACCEPT-ENCODING method of gzip or deflate. If a client sends both methods, then the ACE uses the configured method. The ACE rewrites the ACCEPT-ENCODING header to IDENTITY to indicate to the server that it should not compress the return data. By default, the ACE does not compress responses that are less than 512 bytes. You can change this minimum size threshold by using an HTTP parameter-map as follows:
For compression to work, a client must send a request with an ACCEPT-ENCODING method of gzip or deflate. If a client sends both methods, then the ACE uses the configured method. The ACE rewrites the ACCEPT-ENCODING header to IDENTITY to indicate to the server that it should not compress the return data. By default, the ACE does not compress responses that are less than 512 bytes. You can change this minimum size threshold by using an HTTP parameter-map as follows:
Line 66: Line 69:
You can configure various others parameters using an HTTP parameter map (for example, mimetype and user-Agent).
You can configure various others parameters using an HTTP parameter map (for example, mimetype and user-Agent).
-
== Troubleshooting Tips ==
+
== Troubleshooting Compression ==
To display compression statistics, enter the following command:
To display compression statistics, enter the following command:
-
  switch/Admin# '''show service-policy MP detail'''
+
  switch/Admin# '''show service-policy L7_COMP_SLB_POLICY detail'''
   
   
  Status    : ACTIVE
  Status    : ACTIVE
  Description: -----------------------------------------
  Description: -----------------------------------------
  Interface: vlan 1 108
  Interface: vlan 1 108
-
   service-policy: MP
+
   service-policy: L7_COMP_SLB_POLICY
     class: vip
     class: vip
       VIP Address:    Protocol:  Port:
       VIP Address:    Protocol:  Port:
Line 102: Line 105:
       compression:
       compression:
         bytes_in  : 0                          bytes_out : 0  '''<--- Number of bytes transmitted after compressing the server response'''
         bytes_in  : 0                          bytes_out : 0  '''<--- Number of bytes transmitted after compressing the server response'''
-
         Compression ratio : 0.00%  '''<------------------------------ Ratio of data compressed'''
+
         Compression ratio : 0.00%  '''<------------------------------ Percentage of data compressed'''
                 Gzip: 0              Deflate: 0  '''<--------------- Number of times the method is used'''
                 Gzip: 0              Deflate: 0  '''<--------------- Number of times the method is used'''
       compression errors:                                    _
       compression errors:                                    _

Latest revision as of 21:35, 11 March 2011

This article describes the process and CLI commands for troubleshooting compression in the ACE.

Guide Contents
Main Article
Overview of ACE Troubleshooting
Understanding the ACE Module Architecture and Traffic Flow
Preliminary ACE Troubleshooting
Troubleshooting ACE Boot Issues
Troubleshooting with ACE Logging
Troubleshooting Connectivity
Troubleshooting ACE Appliance Ethernet Ports
Troubleshooting Remote Access
Troubleshooting Access Control Lists
Troubleshooting Network Address Translation
Troubleshooting ACE Health Monitoring
Troubleshooting Layer 4 Load Balancing
Troubleshooting Layer 7 Load Balancing
Troubleshooting Redundancy
Troubleshooting SSL
Troubleshooting Compression
Troubleshooting Performance Issues
ACE Resource Limits
Managing ACE Resources
Show Counter Reference

Contents















Overview of Compression

Compression is supported on the ACE30 module running software version A4(1.x) and later and on the ACE 4700 series appliance (all software releases). You can configure compression by entering the compress command under a Layer 7 load-balancing policy. For example:

class-map type http loadbalance match-any L7default-compression- exclusion-mime-type_CLASS
  description Classmap for default SLB compression exclusion mime-types.
  2 match http url .*gif
  3 match http url .*css
  4 match http url .*js

policy-map type loadbalance first-match L7_COMP_SLB_POLICY
  class L7default-compression-exclusion-mime-type_CLASS
    serverfarm SFARM1
  class class-default
    serverfarm SFARM1
    compress default-method deflate  <--------------------------- Configured compression method

interface vlan 200
   service-policy L7_COMP_SLB_POLICY
   no shutdown

For compression to work, a client must send a request with an ACCEPT-ENCODING method of gzip or deflate. If a client sends both methods, then the ACE uses the configured method. The ACE rewrites the ACCEPT-ENCODING header to IDENTITY to indicate to the server that it should not compress the return data. By default, the ACE does not compress responses that are less than 512 bytes. You can change this minimum size threshold by using an HTTP parameter-map as follows:

parameter-map type http HTTP_PARAMMAP
  compress minimum-size 100

The ACE does not compress the server response if the response contains HTTP/1.0, HTTP responses other than 200 OK and 100 Continue, and the following:

  • cache-control: not transform
  • content-MD5

You can configure various others parameters using an HTTP parameter map (for example, mimetype and user-Agent).

Troubleshooting Compression

To display compression statistics, enter the following command:

switch/Admin# show service-policy L7_COMP_SLB_POLICY detail

Status     : ACTIVE
Description: -----------------------------------------
Interface: vlan 1 108
  service-policy: L7_COMP_SLB_POLICY
    class: vip
     VIP Address:    Protocol:  Port:
     2.0.5.1         tcp        eq    80
      loadbalance:
        L7 loadbalance policy: pm
        VIP ICMP Reply       : ENABLED
        VIP state: OUTOFSERVICE
        Persistence Rebalance: ENABLED
        curr conns       : 0         , hit count        : 0
        dropped conns    : 0
        client pkt count : 0         , client byte count: 0
        server pkt count : 0         , server byte count: 0
        conn-rate-limit      : 0         , drop-count : 0
        bandwidth-rate-limit : 0         , drop-count : 0
        L7 Loadbalance policy : pm
          class/match : h
            ssl-proxy client : c
            LB action :
               primary serverfarm: sf1
                    state: DOWN
                backup serverfarm : -
            hit count        : 0
            dropped conns    : 0
            compression      : on  <------------------------------ Compression is enabled if the value is "on"
      compression:
        bytes_in  : 0                          bytes_out : 0  <--- Number of bytes transmitted after compressing the server response
        Compression ratio : 0.00%  <------------------------------ Percentage of data compressed
                Gzip: 0               Deflate: 0  <--------------- Number of times the method is used
      compression errors:                                     _
        User-Agent  : 0               Accept-Encoding    : 0   | 
        Content size: 0               Content type       : 0   |
        Not HTTP 1.1: 0               HTTP response error: 0   |-- Check these error counters to see if they are increasing
        Others      : 0                                        |
        Parameter-map(s):                                     _|

Rating: 0.0/5 (0 votes cast)

Personal tools