Controllerless Networks

I would like to ask for advise if someone has encounter similar issue as mine:

  1. i have 2 IAP(IAP 515 and IAP 315) running on Firmware version 8.5.0.1 with DRT ver 1.0_72057

  2. When I turn on the IAP 515 and create ssid, setup VC, client to connect to SSID, etc no issue(as a single IAP running on the vlan). Same apply to the IAP 315.

3. When I power on both IAP on the same VLAN, only the master is showing up. The second IAP(slave either 515 or 315) can be ping and connected via ssh but its not showing in the cluster.

 

Hope you can help to resolve my issue. Thanks.

 

 

The 315 and 515 might not automatically synchronize their versions of Instant. I would manually upgrade the 315 cluster/AP to match the version of the 515 before adding the 515 to the cluster.

Hi cjoseph,

 

                the 2 AP have the same firmware version. I tried adding manually its MAC address to the master(cluster) also not working(disabled Auto Join). 

 

 

 

You should boot one IAP up first. After five minutes add the second IAP to the cluster. Please post the output of "show swarm" for both devices after 10 minutes so we can see what is going on.

Hi cjoseph,

 

           Please refer below:

 

 

 

 

 

When you execute "show APs" on either IAP, do you see two access points?

Hi cjoseph,

 

             please refer results:

 

 

Please reboot both access points.  I see that one has been up for 17 hours ..

Hi cjoseph,

 

       I have rebooted both of the IAP's but still the same results.

Okay.

When you type "show version" on both access points, do they have the exact version?

"show log system" on each access point might reveal a specific issue that each access point might have synchronizing with the other.

Hi cjosepch,

I noticed something, the clock of the IAP 515 keeps on going back to default everytime I reboot. I tried to power on the IAP 315(master AP) but still the same. Could this be the culprit? Im not sure if this be resolve by upgrading or downgrading the current IAP firmware :(

It could be a problem.  The AP should really be able to access the internet to set the clock properly.

 

There is no battery in the AP to keep the time, so the AP will set its clock from scratch every time it is booted up from an internal NTP source, so the internet should have port 123 allowed so that it can set its clock.

Hi cjoseph,

         AP is able to access the internet. DNS, NTP are set but still not working. I have log the case to Aruba support, checked but still not working. Last move will be RMA. 

Any update after working with TAC? 

Check if one of them is set to standalone?  I don't know what the boot_env would be for that off the top of my head.