The administration of WLC is lost and we feel the need to boot the WLC to recover the administration once made the reload the WLC loses all the mac-address filter, passwords, and users of visits created in the captive portal
The controller does not have a password recovery mechanism. If you use WCS to manage the controller,
you should be able to access the controller from WCS and create a new admin user without logging into
the controller itself. If you have not saved the configuration on the controller after deleting the user, then
rebooting (power cycling) the controller should bring it back up with the deleted user still in the system.
If you do not have the default admin account or another user account with which you can log in, your
only option is to default the controller to factory settings and reconfigure it from scratch or reload the
previously saved configuration.(You have to have access
through the console port, reboot the controller, and break into the bootloader as the system
The system then gives you five options. Select 5. Clear Configuration first. This is the only
option that resets the password, which means you need to reconfigure the rest of the box
again. Then, select 1. Run primary image to boot up the
Ok bbxie but what happens is that the administration is lost for no reason whatsoever, not because we have forgotten the user and password.
Are you saying you can't access the WLC. What code are you running......
We are having the same problem. A new 4402-50 was installed a couple of weeks ago and all of a sudden we cannot telnet, SSH or web manage the controller. Access is available via the console port still.
It is still allowing user traffic to pass but we are planning to reboot but need downtime to complete. The controller is running the latest code version 184.108.40.206. I have a show tech from it and wondered if anyone had seen the folloing errors below. Also noticed some interfaces share the same MAC address on the controller, is this correct??
Apr 22 14:10:23.014 sim.c:1098 SIM-3-MACADDR_GET_FAIL: Interface 1 source MAC address is not found.
ap-manager MAC Address - 00:1e:f7:32:2e:c7
management MAC Address - 00:1e:f7:32:2e:c0
service-port MAC Address - 00:1e:f7:32:2e:c1
virtual MAC Address - 00:1e:f7:32:2e:c0
vlan77 MAC Address - 00:1e:f7:32:2e:c7
We apologize for not having responded, but I was on vacation, have told me that has been resubmitted the problem, both versions 220.127.116.11 and 18.104.22.168. sslitle you find solution to your problem??
It has happened to someone this problem? Any help would be welcome.
There is a bug on the 5 code in which you loose the ability to communitcate to the WLC's, but all traffic still works. The work around is a reboot. I have seen this also in 4.2.112, but TAC say'd they have no knowledge of any complaints on that code.
The 4402 was passing user traffic from Access points and we were able to ping the management address.
We could log in using the console port but could not telnet, ssh, or web manage the controller on eitheir the managment IP address or service port.
The only thing that resolved the problem was to re-boot the 4402 controller. We are worried that it will happen again as we do not know why it happened??
It is a known issues with the 5 code. Especially if you have webauth configured. Will it happen again.... most likely. What is the fix... either downgrade to 4.2 or what of another release of 5 and hope that issue has been reloved.
Again, traffic will pass and console will work, but if you try to manage the wlc via the management ip, will not be able to.