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.
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:
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).
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.