Auto Manage in WLSE

[nazhmeto]

Hello,

Here is the problem. I am applying a startup config to new AP1200 from the DHCP server configured to get the config template from WLSE. The startup config only has the parameters to make the AP discoverable on the network (CDP, SNMP, Telnet/SSH). It gets the config OK. Then when the WLSE discovers it to apply the AutoManage config it fails. During that discovery the AP changes its IP. The fail error says "authentication open" command is not valid. Then when you delete the discovered AP and run the discovery again, it works fine. Any thoughts why this happens?

Thank you!

[jkemery]

What versions are you running on the WLSE and AP? Using the latest versions made a difference for me.

[bauerdp]

Hello, I work with this unit also, thanks for your reply. The WLSE is on 2.7u, I've tried upgrading it to 2.7.1, but have not been able to...the downloaded files from Cisco don't work for me...I have to figure that one out yet.

The access points are new and the firmware versions are whatever they are shipped with, currently most of them are coming with 12.2(13)JA4.

Thanks for any help.

[jkemery]

If you are upgrading using a windows workstation?

Do the following:

Extract the files to the root directory, ie. c:\

Then execute the autorun.bat file located at the root. You should get an IE window with instructions on the upgrade.

Word of caution, make sure you are updating with the right file, this will be noted in the IE windows instructions. I accidently reinstalled a full version upgrade recently and it corrupted the database. I had to wipe the system and start over, many hours of work lost. BTW, this also brings to mind the importance of a good working backup of the WLSE. I export mine to an FTP server on a daily basis.

After thinking about this, you should not have this problem on the versions your runnigh though. I've been using this same setup for months and it works fine. I suspect that your templete is corrupt. I suggest you create a new one from scratch and try that. I would do this before upgrading as I don't think thats your problem.

Let me know how it goes. I've installed about 90 WAPs using the autoconfig and it works like a champ.

Best regards,

JK

[jkemery]

Sounds like you need to add parameters for the authentication setup in the startup config template?

[nazhmeto]

Hi again.

Thank you for all your quick and helpful responses! We finally figured both issues out: the upgrade of WLSE and the startup and auto manage configurations for new AP’s through WLSE.

WLSE upgrade problem was easily fixed-- we just tried it from another PC and it worked :). Not sure what it was, thinking --maybe the version of Java installed on the "unlucky" machine.

The startup and auto manage configs took longer. If you remember, it was the auto upgrade config we tried to apply to AP’s (after applying startup config and discovering them) that gave us "error applying 'authentication open' command". The upgrade of WLSE didn't fix it. So, then we got rid of that line command by taking the SSID from the Basic Settings of the template and setting it in the Security section. Now the error was caused by 'ip address dhcp' command, which was coming from the same Basic Setting block of code. The Configuration Server Protocol of Basic Settings was set to 'DHCP' by default (which, I assume invoked a new DHCP lease for the newly discovered AP), we set it to 'Static IP' and that seemed to eliminate the Basic Settings block completely and our problems with it.

I wonder how you didn't come across the same problem if you didn't…

Anyway, thank you again and good luck!

Oksana