Sounds like he is not using LAG. LAG or etherchannel is a way of bonding the physical ports 1-4 to a single logical IP address. If you do not do this then you need to setup an AP manager IP address for each sfp port on the controller that you have active.
I am not using LAG. I have setup an AP-manager on port 1 not on port 3. But all AP's are connected on port 3. At the moment I have 48 AP's.
I add 15 new AP's on the same switch, three of them can connect to port 1 (ap-manager), for all the other I see the following message :AP cannot join because the maximum number of APs on interface 3 is reached. Very strange.
Additional information: port 2 has a different interface, it also isn't an ap-manager, and it is connected to the same switch as port 1 and 3, but in another VLAN.
I can try the following:
I disconnect port 3, normally the first 48 AP's has to switch to port 1. I create a new ap-manager2, linked to port 3.
Go to controller/interfaces/ap-manager/ and verify that the physical interface is port one and that it is on the same vlan as the APs. Quite often, a bug in the code resets the physical port to 0 (zero) when you reboot for the very first time. Other than that and a possible vlan misconfiguration on the switches, I'd call TAC.
The Cisco docs clearly state that you can only have 48 APs associated to each ap-manager interface. If you are not running LAG, and I can't think of a good reason not to, then you will need 3 physical interfaces to be configured with unique ap-manager ip addresses in order to register 100 APs. Since the APs point to the management ip (via DNS or DHCP) to get the ap-manager interface, they will automatically load balance.
Note that unless you are running VERY recent code, there are significant ARP bugs related to the additional ap-manager interfaces responding to ARP requests. The best-practice is to add a static ARP entry in the router/L3 switch that is the ap-manager's default-gateway. This is an artifact of the ap-manager interfaces not responding to any traffic accept LWAPP, including ARP. This has been a serious problem for a lot of enterprise customers because this impacts most CEF switching devices like the Catalyst 6500 since most IOS versions also have a CEF adjacency/ARP timeout bug.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...