Launching GUI for WiSM causes it to reboot

[Bob MacLean]

1 of the 4 WiSMs here reboots itself when the web GUI is started. The other 3 do not do this.

sequence:

1. type in it's IP @ in a browser while you have a CLI session for it open

2. the CLI shows it go offline and then starts it reboot

3. obviously, it drops all WAPs and the attached clients and the WAP associate to one of the other 3 WiSMs

4. once the reboot is done, WAPs slowly begin to be moved to the bad boy WiSM

We are going to replace our entire WiFi, which will take months, since the WiSM is end-of-existence but I'm getting tired of this since my backup person does not know the WiSM CLI nor can I show co-workers anything concerning the WiSM configuration on the CLI. The GUI is more helpful for that.

TAC looked for a similar case but came up w/ nothing that applied.

They are all on the same v7.0.252.0 code.

[Leo Laohoo]

Go into CLI and post the complete output to the command "sh coredump summary" and "sh sysinfo".

[Bob MacLean]

(WiSM-slot13-1) >show coredump summary



Core Dump is disabled



(WiSM-slot13-1) >show sysinfo



Manufacturer's Name.............................. Cisco Systems Inc.

Product Name..................................... Cisco Controller

Product Version.................................. 7.0.252.0

RTOS Version..................................... 7.0.252.0

Bootloader Version............................... 7.0.252.0

Emergency Image Version.......................... 7.0.252.0

Build Type....................................... DATA + WPS



System Name...................................... WISM3-COREB

System Location..................................

System Contact...................................

System ObjectID.................................. 1.3.6.1.4.1.14179.1.1.4.4

IP Address....................................... 10.2XX.1.10

System Up Time................................... 142 days 0 hrs 18 mins 14 secs

System Timezone Location......................... (GMT -8:00) Pacific Time (US and Canada)



Configured Country............................... US - United States

Operating Environment............................ Commercial (0 to 40 C)

Internal Temp Alarm Limits....................... 0 to 65 C

Internal Temperature............................. +39 C





--More or (q)uit current module or to abort

State of 802.11b Network......................... Enabled

State of 802.11a Network......................... Enabled

Number of WLANs.................................. 17

Number of Active Clients......................... 152



Burned-in MAC Address............................ 00:26:0B:F1:XX:XX

Maximum number of APs supported.................. 150

[Leo Laohoo]

"sh sysinfo" shows the uptime to be 142 days?

[Bob MacLean]

Right, I have avoided using the GUI for that long so as not to cause it to crash/reboot.

[Bob MacLean · Accepted solution]

A reboot of the WiSM fixed this.

It seems not all reboots are equal. When it was crashing/rebooting, that reboot never fixed this but this plain old reboot did when not preceded by an invocation of the GUI in a browser. Thanks.