01-27-2014 08:05 PM
i am stucked in the state which AP cannot register to controller.
below is my design.
I have two controller form a master/local(Active/Passive) design.
master ip : 172.16.1.1/24
local ip : 172.16.1.2/24
Active controller ip : 192.168.10.2/24
Passive controller ip: 192.168.10.3/24
VRRP IP 192.168.10.1/24
AP vlan/subnet: vlan 100, ip range: 192.168.10.10/24~192.168.10.254/24
a) guest, vlan 200, bridge local.
b) employee, vlan 300, bridge local.
so , the AP port i need to trunk all vlan (100,200,300)
the controller port i just need to trunk vlan 100.
am i concept right??
but the APs are still cannot register on Controller?
would anyone mind give me some idea??
thx a lot.
01-27-2014 08:15 PM
For you design I would consider using another VLAN for your APs and don't share it with your controller management VLAN
VLAN 20 - 192.168.20.0 /24
You need to trunk back to the switchs where the APs are connected :
Master ip : 192.168.10.2 , interface vlan 100
Local ip : 192.168.10.3 , interface vlan 100
From your switch the APs need to be able to reach the controller on VLAN 100.
Your APs will find your controller using these options:
DHCP option 43
ADP (this is enabled by default on the controller)
Static configuration on your APs
Also make sure you have an IP assigned under your AP-System Profile (LMS IP : 192.168.10.1 :VRRP VIP)
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
01-28-2014 01:58 AM
Did you ever get any access points to associate to the controller before? If the answer is no, you should start simple first and make sure that happens before you add any redundancy. If it worked at one time, retrace your steps and remove everything you added before it stopped working.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base