The Wide-Area Application Services (WAAS) Express software optimizes TCP traffic flows across a WAN. WAAS Express integrates with native services such as security, NetFlow, and quality of service (QoS). WAAS Express provides the following benefits:

• Bandwidth optimization
• Application acceleration
• Increase in remote user productivity
• Interoperation with existing Cisco WAAS infrastructure
• Network transparency
• Deployment flexibility with on-demand service enablement

WAAS Express is supported on Cisco ISR G2 devices (Cisco 800, Cisco 890, Cisco 1905, Cisco 1921, Cisco 1941, Cisco 2901, Cisco 2911, Cisco 2921, Cisco 2951, Cisco 3925, and Cisco 3945 Series routers) only. These devices must have the maximum Dynamic random-access memory (DRAM) installed because WAAS Express stores Data Redundancy Elimination (DRE) cache in DRAM. For more information about DRE, see the "Compression" section. WAAS Express supports WAN speeds in the range from 1.5 to 10 Mbps.

WAAS Express switches to one of the following modes based on the available memory on the device: WAAS_Standard, WAAS_Trial_Limited, or WAAS_Disabled. The table below lists the default memory and maximum memory that can be installed on each of the devices that supports WAAS Express.

The Cisco WAN optimization system consists of ISR G2 devices running the WAAS Express software feature and WAVEs that work together to optimize TCP traffic in your network. When client and server applications attempt to communicate with each other, the network intercepts the traffic and acts on behalf of the client application and the destination server. WAAS Express and Wide-Area Application Virtualization Engines (WAVE) examine the traffic and use built-in application policies to determine whether the traffic in the network can be optimized.

Any application that uses TCP as its underlying transport can benefit from WAAS Express. However, a lot depends on the redundant elements in the application's transactions and the WAN bandwidth condition. The more the redundancy, the more the application is benefitted by WAAS Express. Typical applications that benefit from WAAS Express include HTTP, FTP, and mail applications.

WAAS Express uses the following TCP optimization techniques to overcome the most common challenges associated with transporting traffic over a WAN:

• Constrained bandwidth: Data caching and data compression reduce the amount of data sent over the WAN, which increases data transfer rates. These solutions improve the total transaction time on congested links by reducing the amount of data sent across the WAN.
• Packet loss: The optimized TCP stack in WAAS overcomes issues associated with high packet loss and protects the communicating endpoints from the state of the WAN.

Two devices using WAAS Express can optimize network traffic between themselves, but without any DRE.

When a WAAS Express device is moved from one device group to another device group on the WAAS Central Manager (WCM), the policy definitions under the new device group do not function. When a device is unassigned from a device group, the device gets the policies from the backup policy set from the previously assigned group.

Perform the following steps on WCM when you move a device between device groups. You can either perform only the first step or perform from step 2 through step 4 to move a device between device groups.

1. Go to the "Policy Definitions" page of the device that you want to move; select the new device group, and click "Submit".
2. Go to "Assign Devices" page of device group-1, and unassign the device from the device group.
3. Go to "Assign Devices" page of device group-2, and assign the device to the device group.
4. Go to "Policy Definitions" page of device group-2, and click "Force DG settings".

WAAS Express offers the following benefits:

• Ease of deployment: WAAS Express deployment is easy through simple software activation on any Cisco ISR G2 device running Cisco software.
• Integration with device services: WAAS Express integrates with security, QoS, and other services native to Cisco software.
• Application acceleration: WAAS Express mitigates the effects of WAN latency while allowing data to be transferred faster.
• Investment protection: WAAS Express enables you to deploy your current WAAS deployments to smaller branches and devices without having to invest heavily in WAN optimization overlay technologies.

The following steps describe how a Wide-Area Application Services (WAAS) Express-enabled network optimizes connections between a branch office client and the destination server:

1. A branch office client attempts to connect to the destination server over the native application port.
2. The branch client intercepts the traffic.
3. The branch client performs the following actions:
   1. Examines parameters in the TCP headers of the traffic and then refers to the application policies to determine whether the intercepted traffic should be optimized. Information such as the source and destination IP addresses in the TCP header allows the branch client to match the traffic to an application policy. For a list of the default policies, see the "WAAS Application Policies" section.
   2. Negotiates with the data-center Wide-Area Application Virtualization Engine (WAVE) about whether the traffic must be optimized.
   3. Based on the negotiation, if the branch client determines that the traffic should be optimized, it adds information to the TCP header that informs the next client in the network path to optimize the traffic.
4. The branch client passes the client request through the network to its original destination server.
5. The data-center WAVE performs the following actions:
   1. Intercepts traffic going to the destination server.
   2. Establishes an optimized connection with the branch client. If optimization is disabled on the data-center WAVE, then the connection established between the data-center WAVE and the branch client is not optimized, and the traffic passes over the network unoptimized.
6. WAAS optimizes subsequent traffic between the branch client and data-center WAVE depending on the connection type.

WAAS Express does not optimize traffic in the following scenarios:

• The number of concurrent connections exceed the maximum number of concurrent connections supported on a WAAS Express device.
• WAAS Express and WAVE intercept non-TCP traffic such as Internet Control Message Protocol (ICMP).
• WAVE is overloaded and does not have resources to optimize traffic.
• The intercepted traffic matches an application policy that specifies to pass the traffic unoptimized.

  Note	If unoptimized traffic reaches a WAVE, the WAVE forwards the traffic in pass-through mode without affecting the performance of the application by using the passed-through connection.

• Transport Flow Optimization
• Compression
• Autodiscovery of WAAS Express Devices

In addition to the TCP optimization features that enhance the flow of traffic over a WAN, WAAS Express provides selected application acceleration benefits. WAAS Express reduces the response time of remote applications. Even though TFO optimizes traffic over a WAN, protocol messages between branch office clients and remote servers can cause slow application response time. To resolve this issue, WAAS Express helps to respond to messages locally so that the client need not wait for a response from the remote server.

For an accelerator to operate, you must enable the accelerator on both the WAAS Express device and the peer WAVE at either end of a WAN link. CIFS-Express is a single-sided accelerator; it works when it is enabled only on the WAAS Express device. Each WAAS Express-enabled device uses application policies to match specific types of traffic to an application and to determine whether that application traffic should be optimized and accelerated. For more information, see the "WAAS Application Policies" section.

All WAAS Express accelerators, except SSL-Express accelerator, are mutually exclusive. This means that only one accelerator is applied to a specific flow. The only two accelerators that can act in conjunction are SSL-Express and HTTP-Express accelerators. TFO, along with DRE and LZ, forms a transport optimization (TO) module.

For a particular flow, the following optimizations are possible:

• Application accelerator-only (CIFS-Express accelerator or HTTP-Express accelerator)
• TFO-only (no accelerator)
• TFO (TFO+LZ or TFO+DRE or TFO+LZ+DRE)
• HTTP-Express accelerator + TFO
• CIFS-Express accelerator + TFO
• SSL-Express accelerator + TFO
• SSL-Express accelerator + HTTP-Express accelerator + TFO

• CIFS-Express Accelerator
• HTTP-Express Accelerator
• SSL-Express Accelerator

The WAAS Express software includes over 150 default application policies that help WAAS Express to classify and optimize some of the most common types of traffic in a network.

The table below lists the default applications and classifiers that WAAS Express either optimizes or passes through based on the policies that are provided with the system.

The WAAS Express software supports the following optimization actions based on the type of traffic it encounters:

• TFO--A collection of optimization technologies such as automatic windows scaling, increased buffering, and selective acknowledgment that optimize all TCP traffic over a network.
• DRE--A compression technology that reduces the size of transmitted data by removing redundant information before sending the shortened data stream over the WAN. DRE operates on significantly larger streams and maintains a much larger compression history than LZ compression.
• LZ--A compression technology that operates on smaller data streams and keeps limited compression history compared to DRE.
• Application accelerators--A collection of individual accelerators for the following traffic types: CIFS, HTTP, and SSL.

We recommend that you review the default policies and modify them as appropriate before you create a new application policy. Often, modifying an existing policy is easier than creating a new one.

When reviewing the table below, note the following:

• The subheadings represent the application names. The associated classifiers are listed under these subheadings. For example, Authentication is a type of application and Kerberos is a classifier for that application.
• The word monitored indicates that the applications are monitored by the WAAS Central Manager (WCM), which can display statistics for only 20 applications at a time.

WAAS Express Phase 2 extends support for active/active and active/standby configurations on multiple WAN links.

IP Cisco Express Forwarding can efficiently use multiple parallel links without additional hardware multiplexers. The load balancing functionality on a device distributes packets across multiple links based on Layer 3 routing information. The load balancing functionality is inherent to the forwarding mechanism of a device. Some of the load balancing features supported by Cisco software include:

• Per-destination load balancing: In this type of load balancing, all packets for a given destination are forwarded along the same path. This preserves packet order, with potential unequal usage of links. If one host receives major part of traffic, all packets use one link, leaving bandwidth on other links unused. A larger number of destination addresses lead to more equally used links. You can enable per-destination load balancing on WAN interfaces by configuring the ip load-sharing per-destination command
• Per-packet load balancing: This type of load balancing guarantees equal load across all links. However, the packets may arrive out-of-order at the destination because of differential delay in the network. You can enable per-packet load balancing on WAN interfaces by configuring the ip load-sharing per-packet command.

Both per-destination and per-packet load balancing require the ip cef command to be configured.

Note	WAAS Express does not support interoperability with a per-packet load balancing configuration or any other configuration that results in sending packets from one flow to be sent to a different WAN link.

WAAS Express supports backup interface configuration. During switch over between active and standby interfaces, you will need to re-establish a session.

Simple Network Management Protocol (SNMP) is an interoperable, application-layer protocol that provides a message format for communication between SNMP managers and agents. SNMP provides a standardized framework and a common language that is used for monitoring and managing devices in a network.

SNMP allows for monitoring of WAAS Express. WAAS Express supports only SNMPv2c for SNMP traps; WAAS Express SNMP notification will fail if the correct SNMP version is not used.

• Troubleshooting Tips

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    parameter-map type waas parameter-map-name

4.    tfo optimize {full | dre {yes | no compression {lz | none}}}

5.    tfo auto-discovery blacklist {enable | hold-time minutes}

6.    cpu-threshold maximum-threshold

7.    lz entropy-check

8.    exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	parameter-map type waas parameter-map-name Example: Device(config)# parameter-map type waas waas_global	Configures a parameter map of the type waas and enters parameter map configuration mode. Note    The only supported parameter map of the type waas is waas_global.
Step 4	tfo optimize {full | dre {yes | no compression {lz | none}}} Example: Device(config-profile)# tfo optimize dre no compression lz	Configures the compression for WAAS Express.
Step 5	tfo auto-discovery blacklist {enable | hold-time minutes} Example: Device(config-profile)# tfo auto-discovery blacklist hold-time 1000	(Optional) Enables, configures, and integrates a blacklist with autodiscovery for WAAS Express.
Step 6	cpu-threshold maximum-threshold Example: Device(config-profile)# cpu-threshold 90	(Optional) Sets the CPU threshold limit.
Step 7	lz entropy-check Example: Device(config-profile)# lz entropy-check	(Optional) Enables adaptive LZ through entropy checking.
Step 8	exit Example: Device(config-profile)# exit	Exits parameter map configuration mode.

Note	You can configure WAAS Express by using the default class and policy maps. Alternatively, you can first define the class and policy maps and then configure WAAS Express.

Perform these tasks to define class and policy maps if you do not want to use the default class and policy maps that are created when WAAS Express is enabled:

• Defining Class Maps
• Associating Class Maps with Policy Maps
• Troubleshooting Tips

Device(config)# class-map type waas waas_global
Device(config-cmap)# match tcp destination port 7000 7009
Device(config-cmap)# exit
Device(config)# class-map type waas waas_global
Device(config-cmap)# match tcp destination ip 209.165.200.225 0.0.0.31 port 80 80
Device(config-cmap)# match tcp destination ip 209.165.200.225 0.0.0.31 port 8080 8080

Device(config)# policy-map type waas waas_global
Device(config-pmap)# class AFS
Device(config-pmap-c)# optimize tfo lz application Web
Device(config-pmap-c)# exit
Device(config-pmap)# class Http
Device(config-pmap-c)# optimize tfo lz application Filesystem
Device(config-pmap-c)# exit
Device(config-pmap)# class class-default
Device(config-pmap-c)# exit
Device(config-pmap)# exit

Device# show policy-map type waas

Policy Map type waas waas_global
 Class AFS
  optimize dre lz application Web
 Class Http
  optimize lz application Filesystem
 Class class-default

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    interface interface-type/number

4.    waas enable

5.    exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	interface interface-type/number Example: Device(config)# interface GigabitEthernet0/0	Specifies an interface for configuration and enters interface configuration mode
Step 4	waas enable Example: Device(config-if)# waas enable	Enables WAAS Express on the WAN interface.
Step 5	exit Example: Device(config-if)# exit	Exits interface configuration mode.

• Troubleshooting Tips

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    parameter-map type waas parameter-map-name

4.   no dre upload

5.   exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	parameter-map type waas parameter-map-name Example: Device(config)# parameter-map type waas waas_global	Configures a parameter map of the type waas and enters parameter map configuration mode. Note    The only supported parameter map of the type waas is waas_global.
Step 4	no dre upload Example: Device(config-profile)# no dre upload	Disables the upload DRE operation.
Step 5	exit Example: Device(config-profile)# exit	Exits parameter map configuration mode.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    parameter-map type waas parameter-map-name

4.    accelerator cifs-express

5.    enable

6.    read-ahead enable

7.    read-ahead size value

8.    async-write enable

9.    async-write quota-threshold value

10.    ads-negative-cache enable

11.    ads-negative-cache timeout seconds

12.    end

13.    show waas accelerator cifs-express

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	parameter-map type waas parameter-map-name Example: Device(config)# parameter-map type waas waas_global	Configures a parameter map of the type waas and enters parameter map configuration mode. Note    The only supported parameter map of the type waas is waas_global.
Step 4	accelerator cifs-express Example: Device(config-profile)# accelerator cifs-express	Enters WAAS CIFS configuration mode and allows the configuration of CIFS-Express accelerator parameters.
Step 5	enable Example: Device(config-waas-cifs)# enable	Enables CIFS-Express accelerator. The CIFS-Express accelerator is enabled on ports 139 and 445. Disabling CIFS-Express accelerator will disable all CIFS-Express accelerator parameters.
Step 6	read-ahead enable Example: Device(config-waas-cifs)# read-ahead enable	(Optional) Enables the read ahead feature.
Step 7	read-ahead size value Example: Device(config-waas-cifs)# read-ahead size 200	(Optional) Configures the amount of data to read ahead per file.
Step 8	async-write enable Example: Device(config-waas-cifs)# async-write enable	(Optional) Enables async write operation.
Step 9	async-write quota-threshold value Example: Device(config-waas-cifs)# async-write quota-threshold 100	(Optional) Configures the quota threshold for async write to perform the optimization.
Step 10	ads-negative-cache enable Example: Device(config-waas-cifs)# ads-negative-cache enable	(Optional) Enables negative caching for alternate data streams.
Step 11	ads-negative-cache timeout seconds Example: Device(config-waas-cifs)# ads-negative-cache timeout 10	(Optional) Configures the timeout value for negative caching entries.
Step 12	end Example: Device(config-waas-cifs)# end	Exits WAAS CIFS configuration mode and returns to privileged EXEC mode.
Step 13	show waas accelerator cifs-express Example: Device# show waas accelerator cifs-express	(Optional) Displays the status and configuration of all CIFS-Express accelerator parameters.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    parameter-map type waas parameter-map-name

4.    accelerator http-express

5.    enable

6.    dre-hints enable

7.    suppress-server-encoding enable

8.    end

9.    show waas accelerator http-express

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	parameter-map type waas parameter-map-name Example: Device(config)# parameter-map type waas waas_global	Configures a parameter map of the type waas and enters parameter map configuration mode. Note    The only supported parameter map of the type waas is waas_global.
Step 4	accelerator http-express Example: Device(config-profile)# accelerator http-express	Enters WAAS HTTP configuration mode and allows the configuration of HTTP-Express accelerator parameters.
Step 5	enable Example: Device(config-waas-http)# enable	Enables HTTP-Express accelerator. Disabling HTTP-Express accelerator will disable all HTTP-Express accelerator parameters.
Step 6	dre-hints enable Example: Device(config-waas-http)# dre-hints enable	(Optional) Enables HTTP-Express accelerator to pass DRE hints to the DRE module.
Step 7	suppress-server-encoding enable Example: Device(config-waas-http)# suppress-server-encoding enable	(Optional) Suppresses server side encoding.
Step 8	end Example: Device(config-waas-http)# end	Exits WAAS HTTP configuration mode and returns to privileged EXEC mode.
Step 9	show waas accelerator http-express Example: Device# show waas accelerator http-express	(Optional) Displays the status and configuration of all HTTP-Express accelerator parameters.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    parameter-map type waas parameter-map-name

4.    accelerator http-express

5.    enable

6.    metadatacache enable

7.    metadatacache https enable

8.    metadatacache max-age seconds

9.    metadatacache min-age num

10.    metadatacache filter-extension ext1, ext2,...

11.   metadatacache request-ignore-no-cache enable

12.   metadatacache response-ignore-no-cache enable

13.   metadatacache redirect-response enable

14.    metadatacache unauthorized-response enable

15.    metadatacache conditional-response enable

16.    end

17.    show waas cache http-express metadatacache all

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	parameter-map type waas parameter-map-name Example: Device(config)# parameter-map type waas waas_global	Configures a parameter map of the type waas and enters parameter map configuration mode. Note    The only supported parameter map of the type waas is waas_global.
Step 4	accelerator http-express Example: Device(config-profile)# accelerator http-express	Enters WAAS HTTP configuration mode and allows the configuration of HTTP-Express accelerator parameters.
Step 5	enable Example: Device(config-waas-http)# enable	Enables HTTP-Express accelerator. Disabling HTTP-Express accelerator will disable all HTTP-Express accelerator parameters.
Step 6	metadatacache enable Example: Device(config-waas-http)# metadatacache enable	(Optional) Enables HTTP metadata caching.
Step 7	metadatacache https enable Example: Device(config-waas-http)# metadatacache https enable	(Optional) Enables HTTPS metadata caching.
Step 8	metadatacache max-age seconds Example: Device(config-waas-http)# metadatacache max-age 1000	(Optional) Configures the maximum time, in seconds, to retain cache entries in the metadata cache table.
Step 9	metadatacache min-age num Example: Device(config-waas-http)# metadatacache min-age 1000	(Optional) Configures the minimum time, in seconds, to retain cache entries in the metadata cache table.
Step 10	metadatacache filter-extension ext1, ext2,... Example: Device(config-waas-http)# metadatacache filter-extension html,css,jpg	(Optional) Configures the metadata cache to store only the file extensions specified in the list.
Step 11	metadatacache request-ignore-no-cache enable Example: Device(config-waas-http)# metadatacache request-ignore-no-cache enable	(Optional) Configures the metadata cache to ignore cache-control on requests.
Step 12	metadatacache response-ignore-no-cache enable Example: Device(config-waas-http)# metadatacache response-ignore-no-cache enable	(Optional) Configures the metadata cache to ignore cache-control on response.
Step 13	metadatacache redirect-response enable Example: Device(config-waas-http)# metadatacache redirect-response enable	(Optional) Enables the HTTP URL redirect feature.
Step 14	metadatacache unauthorized-response enable Example: Device(config-waas-http)# metadatacache unauthorized-response enable	(Optional) Enables the HTTP authentication-redirect feature.
Step 15	metadatacache conditional-response enable Example: Device(config-waas-http)# metadatacache conditional-response enable	(Optional) Enables responses for the HTTP conditional requests feature.
Step 16	end Example: Device(config-waas-http)# end	Exits WAAS HTTP configuration mode and returns to privileged EXEC mode.
Step 17	show waas cache http-express metadatacache all Example: Device# show waas cache http-express metadatacache all	(Optional) Displays HTTP-Express accelerator metadata cache entries.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    parameter-map type waas parameter-map-name

4.    accelerator ssl-express

5.    enable

6.   no empty-ssl-fragment-insertion

7.    waas-ssl-trustpoint label

8.    cipher-list list-name

9.    cipher cipher-suite

10.    exit

11.    services host-service peering

12.    peer-ssl-version ssl-tls-version

13.    peer-cipherlist list-name

14.    peer-cert-verify enable

15.    end

16.    show waas statistics accelerator ssl-express ciphers

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	parameter-map type waas parameter-map-name Example: Device(config)# parameter-map type waas waas_global	Configures a parameter map of the type waas and enters parameter map configuration mode. Note    The only supported parameter map of the type waas is waas_global.
Step 4	accelerator ssl-express Example: Device(config-profile)# accelerator ssl-express	Enters WAAS SSL configuration mode and allows the configuration of SSL-Express accelerator parameters.
Step 5	enable Example: Device(config-waas-ssl)# enable	Enables SSL-Express accelerator. Disabling SSL-Express accelerator will disable all SSL-Express accelerator parameters.
Step 6	no empty-ssl-fragment-insertion Example: Device(config-waas-ssl)# no empty-ssl-fragment-insertion	(Optional) Disables the sending of an empty SSL fragment as the first encrypted message sent to the client. Note    To solve issues of interoperability with older versions of client applications such as Internet Explorer 6, you can disable the sending of this empty SSL fragment with this step.
Step 7	waas-ssl-trustpoint label Example: Device(config-waas-ssl)# waas-ssl-trustpoint ssl-tp	Associates the specified trustpoint with SSL-Express accelerator.
Step 8	cipher-list list-name Example: Device(config-waas-ssl)# cipher-list clist	Creates a cipher list for a WAAS-to-WAAS session and enters cipher list configuration mode.
Step 9	cipher cipher-suite Example: Device(config-waas-cipher-list)# cipher rsa-with-3des-ede-cbc-sha	Adds the specified cipher suite to a cipher list.
Step 10	exit Example: Device(config-waas-cipher-list)# exit	Exits cipher list configuration mode and returns to WAAS SSL configuration mode.
Step 11	services host-service peering Example: Device(config-waas-ssl)# services host-service peering	Configures host peering service and enters SSL peering service configuration mode.
Step 12	peer-ssl-version ssl-tls-version Example: Device(config-waas-ssl-peering)# peer-ssl-version ssl3	Configures the SSL version to be used for WAAS-to-WAAS sessions. Note    Ensure that the version configured on the WAAS Express device matches the version configured on the peer WAAS device(s).
Step 13	peer-cipherlist list-name Example: Device(config-waas-ssl-peering)# peer-cipherlist clist	Configures the cipher list to be used for WAAS-to-WAAS sessions. Note    Ensure that the cipher list configured on the WAAS Express device overlaps the one configured on the peer WAAS device(s).
Step 14	peer-cert-verify enable Example: Device(config-waas-ssl-peering)# peer-cert-verify enable	Enables the verification of the peer certificate. Note    If the peer WAAS device is using a self-enrolled certificate, then disable the verification of the peer certification on this device; otherwise, all SSL connections being optimized with that peer will be reset due to WAAS-to-WAAS session SSL handshake failure.
Step 15	end Example: Device(config-waas-ssl-peering)# end	Exits SSL peering service configuration mode and returns to privileged EXEC mode.
Step 16	show waas statistics accelerator ssl-express ciphers Example: Device# show waas statistics accelerator ssl-express ciphers	(Optional) Displays statistics about the cipher suites being used for different SSL sessions.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    snmp-server enable traps waas [cpu-throttle-off] [cpu-throttle-on] [license-deleted] [license-expired] [license-revoked] [peer-overload] [tfo-conn-overload]

4.    snmp-server community community-string [ro | rw]

5.    snmp-server source-interface [traps | informs] interface

6.    snmp-server host {hostname | ip-address} [vrf vrf-name | informs | traps | version {1 | 2c | 3} [auth | noauth | priv]] community-string [udp-port port [notification-type]]

7.    exit

8.    show snmp mib

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Device> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Device# configure terminal	Enters global configuration mode.
Step 3	snmp-server enable traps waas [cpu-throttle-off] [cpu-throttle-on] [license-deleted] [license-expired] [license-revoked] [peer-overload] [tfo-conn-overload] Example: Device(config)# snmp-server enable traps waas peer-overload	Enables SNMP traps for WAAS Express.
Step 4	snmp-server community community-string [ro | rw] Example: Device(config)# snmp-server community public ro	Sets up the community access string to permit access to SNMP.
Step 5	snmp-server source-interface [traps | informs] interface Example: Device(config)# snmp-server source-interface traps gigabitethernet5/3	Specifies the interface from which an SNMP trap originates the notifications or traps.
Step 6	snmp-server host {hostname | ip-address} [vrf vrf-name | informs | traps | version {1 | 2c | 3} [auth | noauth | priv]] community-string [udp-port port [notification-type]] Example: Device(config)# snmp-server host 10.1.1.1 version 2c public waas	Specifies the recipient of an SNMP notification. WAAS Express requires version 2c to be configured.
Step 7	exit Example: Device(config)# exit	Exits global configuration mode and returns to privileged EXEC mode.
Step 8	show snmp mib Example: Device# show snmp mib	(Optional) Displays a list of MIB module instance identifiers (OIDs) registered on your device.

Device(config)# class-map type waas match-any http
Device(config-cmap)# match tcp destination port 80 80 
Device(config-cmap)# match tcp destination port 8080 8082 
Device(config-cmap)# exit
Device(config)# class-map type waas waas_global
Device(config-cmap)# match tcp destination port 5190 5193 
Device(config-cmap)# exit
Device(config)# class-map type waas match-any bittorrent
Device(config-cmap)# match tcp destination port 6969 
Device(config-cmap)# match tcp destination port 6881 6889 
Device(config-cmap)# exit
Device(config)# policy-map type waas waas_global
Device(config-pmap)# class http
Device(config-pmap-c)# optimize tfo lz application web-traffic
Device(config-pmap-c)# exit
Device(config-pmap)# class aol 
Device(config-pmap-c)# optimize tfo lz application IM
Device(config-pmap-c)# exit
Device(config-pmap)# class bittorrent 
Device(config-pmap-c)# optimize tfo lz application p2p
Device(config-pmap-c)# exit
Device(config-pmap)# exit
Device(config)# interface E0
Device(config-if)# description WAN Connection
Device(config-if)# waas enable
Device(config-if)# exit