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

Dakelley at 21:35, 11 March 2011

2011-03-11T21:35:14Z

← Older revision		Revision as of 21:35, 11 March 2011
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 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\|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__
		+
		+

Dakelley at 18:17, 11 March 2011

2011-03-11T18:17:56Z

← Older revision		Revision as of 18:17, 11 March 2011
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>
	\|}		\|}

Dakelley at 18:17, 11 March 2011

2011-03-11T18:17:05Z

← Older revision		Revision as of 18:17, 11 March 2011
Line 36:		Line 36:
	== 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

Dakelley: /* Troubleshooting Tips */

2011-03-11T18:13:39Z

Troubleshooting Tips

← Older revision		Revision as of 18:13, 11 March 2011
Line 67:		Line 67:
	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:

Dakelley: /* Troubleshooting Tips */

2011-03-11T18:12:46Z

Troubleshooting Tips

← Older revision		Revision as of 18:12, 11 March 2011
Line 103:		Line 103:
	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: _

Dakelley: /* Overview of Compression */

2011-03-11T17:08:51Z

Overview of Compression

← Older revision		Revision as of 17:08, 11 March 2011
Line 53:		Line 53:
	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:

Dakelley: /* Troubleshooting Tips */

2011-03-11T17:08:30Z

Troubleshooting Tips

← Older revision		Revision as of 17:08, 11 March 2011
Line 70:		Line 70:
	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:

Dakelley: /* Overview of Compression */

2011-03-11T17:05:56Z

Overview of Compression

← Older revision		Revision as of 17:05, 11 March 2011
Line 44:		Line 44:
	4 match http url .*js		4 match http url .*js

-	policy-map type loadbalance first-match ~~L7_COMP-TEST_SLB_POLICY~~	+	policy-map type loadbalance first-match L7_COMP_SLB_POLICY
	class L7default-compression-exclusion-mime-type_CLASS		class L7default-compression-exclusion-mime-type_CLASS
	serverfarm SFARM1		serverfarm SFARM1
Line 50:		Line 50:
	serverfarm SFARM1		serverfarm SFARM1
	compress default-method deflate '''<--------------------------- Configured compression method'''		compress default-method deflate '''<--------------------------- Configured compression method'''
		+
		+	interface vlan 200
		+	service-policy L7_COMP_SLB_POLICY

	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:

-	parameter-map type http ~~http~~	+	parameter-map type http HTTP_PARAMMAP
	compress minimum-size 100		compress minimum-size 100

Dakelley at 17:02, 11 March 2011

2011-03-11T17:02:45Z

← Older revision		Revision as of 17:02, 11 March 2011
Line 36:		Line 36:
	== Overview of Compression ==		== Overview of Compression ==

-	You can configure compression by ~~configuring~~ the '''compress''' command under a Layer 7 policy. For example:	+	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 49:		Line 49:
	class class-default		class class-default
	serverfarm SFARM1		serverfarm SFARM1
-	compress default-method deflate <~~<<<<<<<<<<<<<<<<<<<<~~	+	compress default-method deflate '''<--------------------------- Configured compression method'''

	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:

-	parameter-map type http http	+	parameter-map type http http
-	compress minimum-size 100	+	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:		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:

Dakelley at 17:00, 11 March 2011

2011-03-11T17:00:37Z

← Older revision		Revision as of 17:00, 11 March 2011
Line 8:		Line 8:

	__TOC__		__TOC__
		+
		+
		+
		+