AP's fail to register in a WLC

Question

Hello
We are having problems with one of the two controllers of a WISM. APs fail to register in the first controller, but they register fine in the second one.
Our network is comprised of 3 WiSM (6 Controllers) running version 6.0.196.0 and 100  LAP1140's
WISM 1
Controller 1 (Works OK) -
Manager Interface       -  VLAN 70 - IP Address  10.200.100.21 /28
AP Manager Interface -  VLAN 71  - IP Address 10.200.100.34 /29
Controller 2 (Works OK) -
Manager Interface       -  VLAN 70 - IP Address  10.200.100.22 /28
AP Manager Interface -  VLAN 72  - IP Address 10.200.100.42 /29
WISM 2
Controller 3 (DOES NOT WORK) -
Manager Interface       -  VLAN 70 - IP Address  10.200.100.23 /28
AP Manager Interface -  VLAN 73  - IP Address 10.200.100.50 /29
Controller 4 (Works OK) -
Manager Interface       -  VLAN 70 - IP Address  10.200.100.24 /28
AP Manager Interface -  VLAN 74  - IP Address 10.200.100.58 /29
WISM 3
Controller 5 (Works OK) -
Manager Interface       -  VLAN 70 - IP Address  10.200.100.25 /28
AP Manager Interface -  VLAN 75  - IP Address 10.200.100.66 /29
Controller 6 (Works OK) -
Manager Interface       -  VLAN 70 - IP Address  10.200.100.26 /28
AP Manager Interface -  VLAN 76  - IP Address 10.200.100.74 /29
APs register correctly in 5 controllers but fail to register to Controller 3
There isn't  any Firewalls between APs and Controllers and the six controllers are in the same Mobility Group. We use DHCP option 43.
Debugging commands in WLC 3 shows the following output:
*Dec 10 15:08:23.016: 58:bc:27:bf:03:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 150, joined Aps =0
*Dec 10 11:26:31.017: 58:bc:27:bf:03:80 Received a Discover Request from 58:BC:27:BF:03:80 via IP broadcast address but the source IP address (192.168.28.64) is not in any of the configured subnets. Rejecting t
*Dec 10 15:08:23.017: 58:bc:27:bf:03:80 State machine handler: Failed to process  msg type = 1 state = 0 from 192.168.28.64:10256
*Dec 10 15:08:23.017: 00:08:e3:ff:ff:20 Failed to parse CAPWAP packet from 192.168.28.64:10256
I replaced one AP by a PC. It received correctly one IP Address by DHCP and I could ping to Controller 3 (Manager Interface  10.200.100.23 and AP Manager Interface 10.200.100.50)
¿Any idea?
Thanks

Answer 1

Hello,
leolaohoo, Scott, thank you for your answer.
We put all AP Manager IP addresses and Management IP addresses on the same subnet and all the controller works ok now.
Thank you for your help.