04-10-2008 03:32 AM - edited 07-03-2021 03:41 PM
After an upgrade of both controllers on a WiSM module from 4.1.171.0 to 5.0.148.0 the first stays in
"Operational Status of the Controller : Started KeepAlive"
Even after setting to factory defaults or repowering the module.
Any idea what's problem
04-10-2008 04:15 AM
How did you perform the upgrade.... from 4.1.171.0 to 5.0.1.148? Or did you upgrade to 4.2 then to 5.0? Verify the service port info and also verify the switch service port vlans. You see this info when you do a show wism status on the switch correct?
04-10-2008 04:28 AM
04-10-2008 05:42 AM
Had to edit this since I was nto looking at your txt file correctly. You don't have an ip address configured for the management ip. You do have your service port configured. You need to console into that WLC and configure the management ip..... Then verify the rest of your configurations.
04-11-2008 01:03 AM
the service port is configured to get an IP from the dedicated management vlan where a local dhcp service is provided.
...and in the meantime after several controller and module resets it works without config changes....
So I'm wondering whether this is usable in an productive environement.
04-11-2008 04:58 AM
Well since you are using DHCP for you service port, this also means the ip is routable which is not good practice. You need to configure a static ip that is not routable.
04-18-2008 12:30 AM
I went back to 122-18.SXF8 and 4.2.112.0.
Now everything works as promised.
-> Be aware of newest versions...
04-18-2008 04:55 AM
Good fix.... that is why I haven't deployed any 5.0 code yet.... Issues Issues Issues.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: