APController (Master) : 1.1.1.45
APMSController (Master) : 1.1.1.50
APNAME : (NEW-AP Should connect to APController) : 1.1.1.46
Scenario 1:
- Both APController and APMSController are UP and on the same VLAN but offering different group or SSID.
- Configure AP as per apboot (See details below)
- APNAME boot but instead it gets the Master IP from APMSController (1.1.1.50), so there is no configuration pushed. NOT WORKING
Scenario 2:
- Shutdown APMSController
- Configure AP (exactly the same as below)
- AP Works getting the correct master which is 1.1.1.45
For scenario two is working, but the problem is when we turn back on the APMSController, then if the new APNAME restart it will get the APMSController again which is 1.1.1.50
Even I’ve statically configured the 1.1.1.45 as master for the NEW AP, but when both Controller are up it is taking the 1.1.1.50 to be its master.
apboot> printenv
bootdelay=2
baudrate=9600
autoload=n
boardname=Ardmore
servername=aruba-master
bootcmd=boot ap
autostart=yes
bootfile=e500.ari
ethaddr=b4:5d:50:cf:74:a6
ipaddr=1.1.1.46
netmask=255.255.254.0
gatewayip=1.1.1.1
dnsip=10.10.10.10
domainname=domain.com
uplink_vlan=56
master=1.1.1.45
masterip=1.1.1.45
serverip=1.1.1.45
name=APNAME
ethact=eth0
stdin=serial
stdout=serial
stderr=serial
Appriciate any help in advance!
Thank you!