Wireless Access

Hello,

 

Have already done a master-local redundancy and we have configued lms and bkup lms ip for the ap's to failover.

 

What we noticed is when the master fails all the ap's failover to the local controller without any issues but when the local fails the ap's are not failing over to the master it still waits for the lms-preempt to expire is this the correct behavior.

 

We are running 6.1.3.1 version.

That is the correct behavior.

 

So in case local fails after ap's failover then the ap's will be down ?

Access points will reboot and attempt to discover the first controller.

 

The access points did reboot but it came up only after the local came up and then gradually failed over to the master

What are the access points using for initial discovery, and what is it pointing to?  If it is using DNS, you can put two addresses in the A-record for Aruba-master so that not only will it try the local, but the master initially.

 

You could have the problem you describe if the initial discovery is only pointing to the local.  The access point only gets the lms and backup lms-ip when it has successfully contacted a controller after a reboot.  It still must contact an initial controller to get those two parameters.  Putting in a second address for the a-record of aruba-master could help deal with that.

 

we are using Static ip address on the access points with the server ip and the master ip pointing to the Master controller.

 

The ip address of the local controller is mentioned only on the ap system profile.

So that means if the master controller is down, the access points won't be able to come up when they reboot.

 

Your only options are to use dynamic discovery through DNS with two a-records, or keep using preempt.