Users Guide

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.
Ignore_and_do_not_push Command
The ignore and do not push directive should typically be used when a value cannot be configured on the device,
but always appears in the running-config file. Lines enclosed in the ignore and do not push directive will not be
included in the startup-config file that is copied to each AP.
When AirWave is comparing the running-config file to the startup-config file for configuration verification, it will
ignore any lines in the running-config file that start with the text within the directive. Lines belonging to an ignored and
unpushed line, the lines immediately below the line and indented, are ignored as well. In the example below, if you
were to bracket the NTP server, the NTP clock period would behave as if it were bracketed because it belongs with or is
associated with the NTP server line.
The line <ignore_and_do_not_push>ntp clock-period</ignore_and_do_not_push> will cause lines starting with "ntp clock-
period" to be ignored. However, the line <ignore_and_do_not_push>ntp </ignore_and_do_not_push> causes all lines
starting with "ntp" to be ignored, so it is important to be as specific as possible.
Push_and_exclude Command
Instead of using the full tags you may use the parenthesis shorthand, (substring). The push and exclude directive is used
to push commands to the AP that will not appear in the running-config file. For example, some no commands that are
used to remove SSIDs or remove configuration parameters do not appear in the running-config file of a device. A
command inside the push and exclude directive are included in the startup-config file pushed to a device, but AirWave
excludes them when calculating and reporting configuration mismatches.
The opening tag may have leading spaces.
Below are some examples of using directives:
…
line con 0
</push_and_exclude>no stopbits</push_and_exclude>
line vty 5 15
!
ntp server 209.172.117.194
<ignore_and_do_not_push>ntp clock-period</ignore_and_do_not_push>
end
Using Conditional Variables in Templates
Conditional variables allow lines in the template to be applied only to access points where the enclosed commands will
be applicable and not to any other access points within the Group. For example, if a group of APs consists of dual-radio
Cisco 1200 devices (802.11a/b) and single-radio Cisco 1100 (802.11b) devices, it is necessary to make commands related
to the 802.11a device in the 1200 APs conditional. Conditional variables are listed in the table below.
The syntax for conditional variables is as follows, and syntax components are described in Table 92:
%if variable=value%
…
%endif%
Dell Networking W-AirWave 8.0 | User Guide Creating and Using Templates | 186