Mon Jul 13 17:02:56 2009: 00:23:04:b7:87:96 Successful transmission of LWAPP Discovery Response to AP 00:23:04:b7:87:96 on port 29
To me appears that they are finding the controller but the join process isn't being initiated. The APs and WLC are in the same subnet and vlan so I have configured the WLC as Layer 2. The only thing that is different from other installs I have done is that this customer has HP Switches.
The LAP's have not be previously deployed as this is a complete new install.
I am not sure if the LAP can ping the Management IP but I will check that in the morning ... but my question is why no errors ... I did a debug on errors and got nothing ... I did a sh ap join stats detailed on the 2 MAC Addresses that I connected and got no errors so I am truly puzzled as too why the APs are not attempting to initiate the join process ... I am thinking that is may be a DHCP issue so I am starting there tomorrow
How are the switchports configured on the HP switches? I have known the HP switches to be different to cisco with VLAN tagging/trunking. It might be worth trying a few different combinations on the switchports.. Also, have you tried priming the AP with an IP address and a Controller?
As far as I know the HP Switches are tagged with the same vlan the WLC is in. I don't have access to them but is it something else I should be asking the customer to check or do in regard to the HP Switches ... again I have only worked with Cisco Switches when it has came to Wireless
Thanks for that tidbit ... I didn't know that so luckily when I reconfigured the WLC because I thought it may be an XML issue from me downgrading to 4.2.205 I left the mode as LAYER 3.
But, the problem was that the Tech here didn't exclude the Mang Interface and AP Mang Interface from the DHCP scope so the APs were grabbing those IPs hence causing them to error once a duplicate IP was found.