Deployment Guide

Dell Networking W-Instant in W-AirWave 8.0 | Deployment Guide Best Practices and Known Issues | 39
Chapter 6
Best Practices and Known Issues
This section describes some best practices to follow when using AirWave to monitor and configure Instant
devices. It also includes some known issues to take into consideration when using AirWave. This list is inclusive of
the AirWave release notes and Instant release notes.
Best Practices
l Keep Instant devices in Monitor Only mode to audit the device and to ensure that configurations are not
automatically pushed. This practice is consistent with the rest of AirWave.
l Be sure that the default configuration is validated and has been pre-tested in a non-production environment
prior to applying it to a production network. Any changes that are made to this configuration will follow the
same process each time and will be applied to other Instant networks.
l If you modify an IAP device's configuration through the Instant user interface, we recommend that you put
the device in Manage Mode, and then use the Import Settings button from the APs/Devices > Manage
page. When using this method instead of Instant Config, you can import settings and update the template
from a single page. Import the settings and then wait approximately a minute. If you find that you need to
also update the template, the APs/Devices > Manage page for the Virtual Controller provides a link to
quickly access the template.
Known Issues with the Instant Integration with AirWave
l If the Organization String configured on the Instant device is different than what is statically written in the
template, AirWave will overwrite the configured Organization String to match the template.
l The Instant primary device sends an update message to AirWave every minute. If the send fails, then the
device will continue to send a state message every two seconds. If the send fails 25 times, then Instant will
determine that AirWave is down.