APController (Master) : 184.108.40.206
APMSController (Master) : 220.127.116.11
APNAME : (NEW-AP Should connect to APController) : 18.104.22.168
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 22.214.171.124
Even I’ve statically configured the 126.96.36.199 as master for the NEW AP, but when both Controller are up it is taking the 188.8.131.52 to be its master.
apboot> printenvbootdelay=2baudrate=9600autoload=nboardname=Ardmoreservername=aruba-masterbootcmd=boot apautostart=yesbootfile=e500.ariethaddr=b4:5d:50:cf:74:a6ipaddr=184.108.40.206netmask=255.255.254.0gatewayip=220.127.116.11dnsip=10.10.10.10domainname=domain.comuplink_vlan=56master=18.104.22.168masterip=22.214.171.124serverip=126.96.36.199name=APNAMEethact=eth0stdin=serialstdout=serialstderr=serial
Appriciate any help in advance!
Is this instant or a hardware-based controller?
Why are you statically configuring ip addresses instead of using dynamic discovery?
Oops i've accidentally clicked the accept solution. Can we modify it?
Anyway To answer your question.
the new ap is an instant
We need to set static ip because AP are set within a range of certain subnet. we also dont use dhcp reservation.
Maybe someone who deploys instant APs with static ip addresses can help you. I just know it is difficult and error-prone.
well i tried both ways for testing purposes but still i got the same results :(
Do you have "preferred master" set on either of the access points?
Can each instant AP reach the ntp server at pool.ntp.org?
Wait, you have two instant APs on the same VLAN serving different WLANS and you are trying to get a third AP to join one of them? I don't understand...
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.