If you are like me you start the working day with a coffee then log into your AirWave server to check all is good in the world. But what do I, and many other people, often see? ‘Mismatched’!! Most people don’t like this because the word “mismatched” sounds like a bad thing to have. Now, what does this actually mean? Every device (WLAN controller, Access Point or switch) managed by AirWave has a running configuration and AirWave stores a copy of that running configuration and compares the two. A mismatch simply means that there is at least one character different between the running configuration on the device and the one stored on AirWave.
It all depends on if you want to use AirWave for configuration management or not. If not, then it is better to switch off “Audit Configuration on Devices” on the group level and remove it from the header bar and columns in the different views.
Devices can be added in two different modes. AirWave calls them “Monitor Only” and “Manage Read/Write”. As the name already implies a device in monitor only mode cannot be configured from AirWave and a device in manage read/write mode can.
Warning! If you don’t want to have a bad day then never add an already configured device in manage read/write mode to AirWave. Always start by adding in monitor-only mode and later decide to change to manage read/write mode if needed. What could happen when you add an already configured device in manage read/write mode is that AirWave will compare the running production configuration on your device with the factory default configuration on AirWave and thus overwrite the production configuration with a factory default configuration. That is not what I call a good start to the day. It depends on the version of AirWave if this happens but I like to be on the safe side and use monitor-only mode first.
So we start with adding a Group to AirWave and then add the device to that group. The only thing that you need is the IP address of the device and to select the right Group and Folder. In the example below I made sure that the credentials were properly configured in the Device Setup -> Communication page. Also, make sure to add in Monitor Only mode.
After some minutes the device will be visible in AirWave and also the complete running configuration has been imported. Name, Location, Contact etc. can be found in the AP/Devices -> Manage page. At the bottom of this page, you will also find an “Import Settings” button to import manually if the device was previously added to AirWave and the settings were not imported or changed.
And the complete configuration can be found in Groups -> Controller Config
When looking at the monitor page of the device you can see that the configuration is good and that the device is still in monitor-only mode.
Now, where does mismatched come from? If I, for example, go to the WebUI of the controller directly and add an SSID then this will be seen by AirWave as a mismatch. You should never change any configuration via the WebUI or CLI when AirWave is used for configuration management. In the example below I have added a new SSID profile on the controller and after clicking “Audit” it will lead to the mismatch. Clicking the “Import” button will import the new configuration and clear the mismatch.
The example above only shows how mismatches are created and what you really should do, of course, is move the device from monitor-only mode to manage read-write mode and start using AirWave for configuration management. In Groups -> Controller Config you will find the complete configuration and that is where you do your add/remove/changes.
If we see the word “mismatched” in AirWave, we now know everything will be okay. Now, finish your morning coffee and have a great work day. That’s how simple the solution is.
For more info on AirWave visit our solution page: http://www.arubanetworks.com/products/networking/management/airwave/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.