Troubleshooting Aruba IAP not joining the Cluster.

[fusion_text]

Real Life Case Study

Problem Statement: An Aruba IAP 205 not joining a cluster of 5   Aruba  IAP 103.

Scenario 1 :

This is a LAN only setup with no internet connection.

1.5 IAP were deployed in the L2 network having OS verion: 6.4.2.3-4.1.1.4_49446. Everything working fine.

2. IAP 205 with OS: 6.4.2.6-4.1.1.6_50009 was implanted in the network, it was not clusterring with IAP 103 series.
3. When there was a power failure in the premises, IAP 103 were getting rebooted automatically but not IAP 205.

4.For testing purpose when we remove IAP 205 , IAP 103 were working fine in the network.

5.The below are the logs when IAP 205 was in the network and taken from IAP 205.

Following debug output was collected from Virtual controller to investigate further.

1/7/2016 16:19:22 PM  Target: 84:d4:7e:c3:fd:7c  Command: show log system

**************************************************************************

Jan  1 00:04:49  cli[3777]: <341097><WARN> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 recv_image_check: mac-04:bd:88:c7:b8:60, version-6.4.2.3-4.1.1.4_49446, ccode_idx-255.

Jan  1 00:04:49  cli[3777]: <341052><ERRS> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 recv_image_check, 1646: AP class not match, Master-30, Slave-26.

Jan  1 00:04:49  cli[3777]: <341004><WARN> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 Image_sync_via_isc

Jan  1 00:04:49  cli[3777]: <341004><WARN> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 send_image_mismatch url (ap classTaurus) to 169.254.181.71

Jan  1 00:04:50  cli[3777]: <341097><WARN> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 recv_image_check: mac-04:bd:88:c7:b7:ce, version-6.4.2.3-4.1.1.4_49446, ccode_idx-255.

Jan  1 00:04:50  cli[3777]: <341052><ERRS> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 recv_image_check, 1646: AP class not match, Master-30, Slave-26.

Jan  1 00:04:50  cli[3777]: <341004><WARN> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 Image_sync_via_isc

Jan  1 00:04:50  cli[3777]: <341004><WARN> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 send_image_mismatch url (ap classTaurus) to 169.254.35.71

Jan  1 00:04:50  cli[3777]: <341097><WARN> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 recv_image_check: mac-04:bd:88:c7:b7:7e, version-6.4.2.3-4.1.1.4_49446, ccode_idx-255.

Jan  1 00:04:50  cli[3777]: <341052><ERRS> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 recv_image_check, 1646: AP class not match, Master-30, Slave-26.

Jan  1 00:04:50  cli[3777]: <341004><WARN> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
Image_sync_via_isc

Jan  1 00:04:50  cli[3777]: <341004><WARN> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 send_image_mismatch url (ap classTaurus) to 169.254.209.70

Jan  1 00:05:12  cli[3777]: <341004><WARN> |AP 84:d4:7e:c3:fd:7c@169.254.73.133 cli| 
 Activate failed, enabling factory SSID

 

 

SCENARIO 2:

This is a LAN only setup with no internet connection.

1. IAP 205 was configured with two SSID, it was having OS version:  6.4.2.6-4.1.1.6_50009.
2. Other IAP 103 was put into the network having OS version: 6.4.2.3-4.1.1.4_49446.
3. IAP 103 started to reboot.
4. For testing purpose removed IAP 205, at that moment IAP 103 was working fine.

.

We replicated the scenarios at Airowire Lab and following were our learnings:

1. IAP 103 was connected  first in the network having os version: 6.4.2.3-4.1.1.4_49446. Later IAP 205 was put into the network,with OS: 6.4.2.6-4.1.1.6_50009. POE switch was connected with the internet. IAP 205 automatically downgraged to the IAP 103 version and it was present  in the cluster.
2. IAP 103 was removed from the network, IAP 205 was upgraded to 6.4.2.6-4.1.1.6_50009mannually (internet was removed).
3. IAP 103 was also included in the network (internet was removed) it did not broadcast the SSID. (Amber Light on 2.4 and 5 Ghz).
4. IAP 205 removed, IAP 103 started to broadcast SSID.
5. With internet in the network
   1. Started IAP 205 first.
   2. Started IAP 103 second.
   3. IAP 103 did not broadcast SSID.
6. Removed both IAP and connected IAP 103.
7. Upgrageded the OS (mannually) to that of IAP 205.
8. Both IAP are in cluster.

Steps to update OS firmware.

Uploading OS through the system.

1. Download the required up OS version from support.arubanetworks.com

https://support.arubanetworks.com/DownloadSoftware/tabid/75/DMXModule/510/EntryId/17008/Default.aspx

1. Save the file in the system.
2. Login into the virtual controller of IAP.
3. Click on maintenance tab as shown below.

 

4. Then Click on firmware tab.

 

1. Upgrade the OS version using image option. (browse through the system).
2. I waited for 15 min, it was still showing ugrading in the GUI.

Reconnected the SSID, firmware was updated in IAP. (SSID goes off and comes back within 5 min).
Blog Author :

Manjunath Kashyap
Airowire Networks

[/fusion_text]