Users Guide
2. Select an AP from the Group to serve as a model AP for the others in the Group. You should select a device that is
configured currently with all the desired settings. If any APs in the group have two radios, make sure to select a
model AP that has two radios and that both are configured in proper and operational fashion.
3. Go to the Groups > Templates configuration page. Select Add to add a new template.
4. Select the type of device that will be configured by this template.
5. Select the model AP from the drop-down list, and select Fetch.
6. AirWave automatically attempts to replace some values from the configuration of that AP with variables to enable
AP-specific options to be set on an AP-by-AP basis. Refer to "Using Template Syntax" on page 185
These variables are always encapsulated between % signs. On the right side of the configuration page is the
Additional Variables section. This section lists all available variables for your template. Variables that are in use in
a template are green, while variables that are not yet in use are black. Verify these substitutions to ensure that all of
the settings that you believe should be managed on an AP-by-AP basis are labeled as variables in this fashion. If you
believe that any AP-level settings are not marked correctly, please contact Dell customer support at dell.com/support
before proceeding.
7. Specify the device types for the template. The templates only apply to devices of the specified type.
n Specify whether AirWave should reboot the devices after a configuration push. If the Reboot Devices after
Configuration Changes option is selected, then AirWave instructs the AP to copy the configuration from
AirWave to the startup configuration file of the AP and reboot the AP.
n If the Reboot Devices after Configuration Changes option is not selected, then AirWave instructs the AP to
copy the configuration to the startup configuration file and then tell the AP to copy the startup configuration file
to the running configuration file.
n Use the reboot option when there are changes requiring reboot to take effect, for example, removing a new SSID
from a Cisco IOS device. Copying the configuration from startup configuration file to running configuration file
merges the two configurations and can cause undesired configuration lines to remain active on the AP.
8. Restrict the template to apply only to the specified version of firmware. If the template should only apply to a
specific version of firmware, select Yes and enter the firmware version in the Template Firmware Version text field.
9. Select Save and Apply to push the configuration to all of the devices in the group. If the devices are in monitor-only
mode (which is recommended while you are crafting changes to a template or creating a new one), then AirWave
will audit the devices and compare their current configuration to the one defined in the template.
Ifyou set the reboot flag to No, then some changes could result in configuration mismatches until the AP is rebooted.
For example, changing the SSID on Cisco IOS APs requires the AP to be rebooted. Two other settings that require
the AP to be rebooted for configuration change are Logging and NTP. A configuration mismatch results if the AP is
not rebooted.
If logging and NTP service are not required according to the Group configuration, but are enabled on the AP, you
would see a configuration file mismatch as follows if the AP is not rebooted:
IOS Configuration File Template
…
(no logging queue-limit)
…
Device Configuration File on APs/Devices > Audit Configuration Page
…
line con 0
line vty 5 15
actual logging 10.51.2.1
actual logging 10.51.2.5
Dell Networking W-AirWave 8.0 | User Guide Creating and Using Templates | 184