actual ntp server 209.172.117.194
radius-server attribute 32 include-in-access-req format %h
…
10. Once the template is correct and all mismatches are verified on the
APs/Devices > Audit
configuration page, use
the
Modify Devices
link on the
Groups > Monitor
configuration page to place the desired devices into
Management
mode. This removes the APs from Monitor mode (read-only) and instructs the AP to pull down its
new startup configuration file from AirWave.
NOTE: Devices can be placed into Management mode individually from the
APs/Devices > Manage
configuration page.
Using Template Syntax
Template syntax is comprised of the following components, described in this section:
l
"Using AP-Specific Variables" on page 157
l
"Using Directives to Eliminate Reporting of Configuration Mismatches" on page 157
l
"Using Conditional Variables in Templates" on page 158
l
"Using Substitution Variables in Templates" on page 159
Using AP-Specific Variables
When a template is applied to an AP all variables are replaced with the corresponding settings from the
APs/Devices
> Manage
configuration page. This enables AP-specific settings (such as Channel) to be managed effectively on an
AP-by-AP basis. The list of used and available variables appears on the template detail configuration page. Variables
are always encapsulated between % signs. The following example illustrates this usage:
hostname %hostname%
…
interface Dot11Radio0
…
power local cck %CCK_POWER%
power local ofdm %OFDM_POWER%
channel %CHANNEL%
…
The
hostname
line sets the AP hostname to the hostname stored in AirWave.
The
power
lines set the power local
cck
and
ofdm
values to the numerical values that are stored in AirWave.
Using Directives to Eliminate Reporting of Configuration Mismatches
AirWave is designed to audit AP configurations to ensure that the actual configuration of the access point exactly
matches the Group template. When a configuration mismatch is detected, AirWave generates an automatic alert
and flags the AP as having a
Mismatched
configuration status on the user page.
However, when using the templates configuration function, there will be times when the running-config file and the
startup-config file do not match under normal circumstances. For example, the
ntp clock-period
setting is almost
never identical in the running-config file and the startup-config file. You can use directives such as
<ignore_and_
do_not_push>
to customize the template to keep AirWave from reporting mismatches for this type of variance.
AirWave provides two types of directives that can be used within a template to control how AirWave constructs the
startup-config file to send to each AP and whether it reports variances between the running-config file and the
startup-config file as "configuration mismatches.” Lines enclosed in
<push_and_exclude>
are included in the AP
startup-config file but AirWave ignores them when verifying configurations. Lines enclosed in
<ignore_and_do_
not_push>
cause AirWave to ignore those lines during configuration verification.
Dell PowerConnect W-AirWave 7.6 | User Guide
Creating and Using Templates | 157
Содержание PowerConnect W-AirWave 7.6
Страница 1: ...Dell PowerConnect W AirWave 7 6 User Guide ...
Страница 12: ...xii Dell PowerConnect W AirWave 7 6 User Guide ...
Страница 112: ...100 Configuring and Using Device Groups Dell PowerConnect W AirWave 7 6 User Guide ...
Страница 162: ...150 Discovering Adding and Managing Devices Dell PowerConnect W AirWave 7 6 User Guide ...
Страница 198: ...186 Using RAPIDS and Rogue Classification Dell PowerConnect W AirWave 7 6 User Guide ...
Страница 276: ...264 Creating Running and Emailing Reports Dell PowerConnect W AirWave 7 6 User Guide ...
Страница 324: ...312 Using VisualRF Dell PowerConnect W AirWave 7 6 User Guide ...
Страница 332: ...320 Index Dell PowerConnect W AirWave 7 6 User Guide ...