User's Guide

You should always apply a Device Action Manager template at the appliance level. When you do, the
profile is inherited for all the other levels. Then, if you have a level that needs a dierent Device Action
Manager template, you can apply that template to that level. For example, in the above screen shot, the
Device Action Manager templates for AirDefense could be the
Infrastructure_Device_Corporate template; then for a special case (in the following screen
shot) you could override the Device Action Manager templates at the AirDefense level and apply the
Infrastructure_Device_Guest templates to the Sanctuary Park network level.
Note
The Override settings option is available when you select (highlight) a network level below
the appliance level. Use the Expand button to reveal the other levels.
You can copy Device Action Manager templates to all your appliances by clicking the Copy settings to
all appliancesi button.
Note
You must have a Central Management license in order to copy settings to all appliances.
Click the Apply button to save your changes. Click the Reset button to discard your changes.
Sequence of Rules in Rule Sets
After you add Action Rules to a Rule Set, you should consider the order in which they appear in the list.
As AirDefense examines devices during auto-classification, it looks for the first match between a device
and an Action Rule in the Rule Set. You should place the least restrictive Action Rule at the top of the
list, and the most restrictive at the bottom of the list.
Device Age Out
Device Age Out allows you to specify an age out value that AirDefense uses to display devices in the
Network tab. For your convenience, a table is displayed listing the devices seen on your network.
Device Age Out
Configuration Tab
642 Extreme AirDefense User Guide for version 10.5.