opt-map

Description

The Silver Peak appliance allows you to configure how your traffic is optimized by creating optimization maps. Optimization maps make it easy for you to explicitly filter for the traffic you want to optimize, and then apply an action to that flow.

Optimization maps — like Route maps and QoS maps — are made up of ordered entries. Each map entry consists of a match statement paired with a set action. Set actions are specific to the type of map.

A map entry can match traffic that satisfies either a pre-defined ACL or any of the following attributes:

n

Protocol

n	Source IP Address / Subnet

n	Destination IP Address / Subnet

n	Source Port Number

n	Destination Port Number

n	Application (standard or user-defined, or a user-defined application group)

n	DSCP value

n

VLAN

If you want to reuse the same match criteria in more than one map, you can pre-define ACLs, which are, essentially, reusable match statements.

Set actions are specific to the type of map. An optimization map has set actions related to optimization and compression features:

n	Network Memory

n	IP header compression

n	Payload compression

n	TCP acceleration

n	Protocol acceleration (CIFS, SSL, SRDF)

Map entries are ordered according to their assigned priorities. Priorities identify, as well as order, entries within a map. Across entries, all priority values must be unique (in other words, no two entries in a given map can have the same priority value).

In the following example, we’ll add a new entry, with a priority of 50, to the default map, map1. The first statement matches all traffic associated with the application, AOL. The second statement enables CIFS acceleration as the action for that traffic:

(config) # opt-map map1 50 match app aol

(config) # opt-map map1 50 set cifs enable

If you enter a new priority statement for an existing optimization map, the CLI adds that entry to the optimization map. However, if the map already has a match or set statement with the same priority, the new entry overwrites the previous one (and the CLI does not provide a warning).

If you want to create a new optimization map, the CLI creates the map the first time you name it in a match statement.

Every optimization map automatically includes a default entry with the priority, 65535, the highest possible number. That default entry applies all the optimization and compression features to all traffic subject to the optimization map.

By default, optimization maps have additional entries that enable protocol-specific optimizations for CIFS, SSL, iSCSI, SRDF, Citrix, and their common ports.

By default, one optimization map is always active. You can change the active map at any time, simply by activating a different map.

See Also

See the following related commands:

n	“opt-map match”

n	“opt-map set”

n	“opt-map activate”

n	“no opt-map”

n	“opt-map modify-priority”

n	“show opt-map”

 

Please send comments or suggestions regarding user documentation to techpubs@silver-peak.com.