Controllerless Networks

Reply
Occasional Contributor II

IAPs suddenly rebooted and each became a separate VCs

One of our clients has four Aruba 225 and two Aruba 93 IAPs. I was adding a new Aruba 225 to the IAP cluster and after connecting it all the IAPS suddenly rebooted. After this event when I accesed the VC IP address, I was able to see only one AP in the VC cluster. On further examination I realized that all Aruba 225 had became "independent" virtual controllers. Each of them trying to respond to the VC IP address, and controlling only one AP. I had to do reboot a couple of times most of the APs for them to become a cluster again.

 

- What could have caused this problem?

- Are there any commands to debug the master election process?

- Is there a way to prevent the cluster from "separating" from itself?

 

About our client's topology:

- All APs were running OS 6.3.1.1-4.0.0.1

- The AP management lan is the untagged VLAN on the cable.

- The two SSIDs, use a tagged VLAN each.

- The new AP had the same OS as the cluster.

Re: IAPs suddenly rebooted and each became a separate VCs

Hello Rodrigo

Thats definitly not normal...

I would open a support case with ArubaNetwork TAC, this looks like a bug... and it needs to be addresed!

 

Cheers

Carlos

----------------------------------------------------
Product Manager - Aruba Networks
Alternetworks Corp
Aruba Employee

Re: IAPs suddenly rebooted and each became a separate VCs

What version was running on the AP225/AP93 cluster?

Re: IAPs suddenly rebooted and each became a separate VCs

Hello Yan

HE mentioned the version running on the original post.

 

Cheers

Carlos

----------------------------------------------------
Product Manager - Aruba Networks
Alternetworks Corp

Re: IAPs suddenly rebooted and each became a separate VCs

I have seen similar where there were dhcp issues and then the APs couldn't get an ip and seemingly reset themselves.

 

When they came back online I found that they were all back to factory default and I had to reconfigure again. 


If my post is helpful please give kudos, or mark as solved if it answers your post.

ACCP, ACMP, ACMX #294
mclarke@arubanetworks.com
Frequent Contributor II

Re: IAPs suddenly rebooted and each became a separate VCs

Hello Rodrigo,

 
Could it be a problem on the wired network? If the IAPs for some reason don't see each other, then they think to be alone and so they become VC.
 
 
Massimo
------------------------------------------------------------
Massimo Gallina
Telecommunications engineer - ACMP2013
Occasional Contributor II

Re: IAPs suddenly rebooted and each became a separate VCs

Thanks for your replies.

 

I checked with the switch staff on that company and there was a configuration change that rendered the network stable during the period we experienced the downtime. After the unstability was resolved and a couple of reboots our 225 joined and became a Virtual Controller. Our APs 93 did not join so I contacted Support. It appears that there is an issue that affected 4.0.0.1, that we can solve by updating to 4.0.0.3.

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: