The WAAS software includes over 200 predefined optimization policy rules that help your WAAS system classify and optimize some of the most common traffic on your network. Table A-1 lists the predefined applications and class maps that WAAS will either optimize or pass through based on the policy rules that are provided with the system.
Before you create an optimization policy, we recommend that you review the predefined policy rules and modify them as appropriate. Often, you can more easily modify an existing policy rule than create a new one.
When reviewing Table A-1, note the following information:
•The subheadings represent the application names, and the associated class maps are listed under these subheadings. For example, Authentication is a type of application and Kerberos is a class map for that application.
•Applications and class maps with the word (monitored) next to them are monitored by the WAAS Central Manager, which can monitor statistics for up to 25 applications and 25 class maps at a time. To view statistics for one of the unmonitored applications, use one of the following methods:
–Use the WAAS CLI, which can display statistics for all applications and class maps on a WAAS device. For more information, see the Cisco Wide Area Application Services Command Reference.
•WAAS Express devices have similar default policy rules but provide application acceleration only for HTTP, SSL, and SMB traffic. Where a different application accelerator is listed in Table A-1, it is not part of the WAAS Action for a WAAS Express device.
The WAAS software uses the following optimization technologies based on the type of traffic that it encounters:
•TFO (transport flow optimization)—A collection of optimization technologies such as automatic windows scaling, increased buffering, and selective acknowledgement that optimize all TCP traffic over your network.
•DRE (data redundancy elimination)—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. DRE can use bidirectional, unidirectional, or adaptive caching. Unless noted in Table A-1, DRE caching is bidirectional.
•LZ (compression)—Another compression technology that operates on smaller data streams and keeps limited compression history compared to DRE.
•Application accelerator—A collection of individual application accelerators for the following traffic types: CIFS, EPM, HTTP, ICA, MAPI, NFS, SSL, and streaming video. (Some application accelerators are not available on WAAS Express devices.)