Monitoring, Management & Location Tracking

Unable to push the complete config to IAP from Airwave

Aruba Employee

Environment Information - Airwave managing any supported IAP versions  [we could find the supported                                                      version of IAP's in Airwave, in the Airwave release notes, under documents section of support.arubanetworks.com.

 

Symptoms - When we search for the mac address on Airwave, we could see the duplicate entry of that Virtual                       controller, on which Airwave is pushing the config, the primary device on which airwave initiated config push, would show as down, and the second device will comeup automatically and shows up with incomplete config as shown below:

rtaImage.jpg

If we look at the UUID's for both devices, they will be different:

from the Airwave cli

#  dbc "select UUID from ap where id = 9192;"
-[ RECORD 1 ]--------------------------------------------
uuid | 3da534280151f0e1df2f577de622f756b2f8d369dacf6e214e

duplicate device from the same

# dbc "select UUID from ap where id = 9197;"
-[ RECORD 1 ]--------------------------------------------
uuid | 953f094d01c3ddbec1ff9b526758a2b9116f58ecfc47d085c6

We could find the ID number from the devices in question to execute the above commands, if we navigate to that device's monitor page, we could see the URL as below:

https:// < airwave IP>/ap_monitoring?id=9192

The highlighted number in the URL above is the ID of the device.

 

Cause- The duplicate entry of the device and the incomplete config push, happened because of the typo in the              config template, as shown below:

clock timezone %clock_timezone%

    rf-band %rf_band%

    ams-ip ams-ip <airwave IP>

    ams-key %password%

    ams-identity %ams_identity%

Due to the typo in the above template,  the ams-ip which is highlighted is supposed to be only once, as shown below:

clock timezone %clock_timezone%

    rf-band %rf_band%

    ams-ip <airwave ip>

    ams-key %password%

    ams-identity %ams_identity%

because of the two "ams-ip", incorrect conifg is getting pushed and the primary IP shows as down, creates a duplicate device.

Resolution - Correcting the typo on the template by removing the additional ams-ip, would resolve the                                    issue and pushes the complete config to the IAP. as shown below:

clock timezone %clock_timezone%

    rf-band %rf_band%

    ams-ip <airwave ip>

    ams-key %password%

    ams-identity %ams_identity%

For Additional troubleshooting, when we use airwave to push  the config to IAP's or only monitoring the IAP's, we could use the below command from IAP CLI to see the connectivity between the IAP and airwave

From IAP CLI:

# show ap debug airwave

 

Version history
Revision #:
1 of 1
Last update:
‎04-07-2015 11:08 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: