I have what I believe to be a unique issue with the 3 WiSM's that I have on my network. I have a 6509 running 12.2(18)SXF8 and (3) WiSM's running 18.104.22.168 inside of that single chassis. They are running fine, but sometimes, one of the controllers will become unreachable through the GUI. It will then be unreachable through telnet or through the service interface from the switch. I can still console to the WiSM, but that's it. It never drops any of the AP's it is supporting, but if I can't manage it, what good is it?
I haven't, but I think the issue may be a little deeper than that due to the fact that I couldn't even get a response from the service interface. I should at least be able to get a telnet session started there. I'm not sure, I plugged into the console port and rebooted the controller from there and everything seems to be working fine since then.
I use to have problems with it even more than now when it was on 22.214.171.124 code, but the new code has truly minimized that.
I have considered going to 4.1, but I have heard some rather scary comments from both users and TAC engineers on the first release of 4.1. I am going to wait at least until the second release hits the streets I think. I hear there are some great additions to 4.1. Did you have to do the emergency release with 4.1?
As far as statically assigning the IP to the service interface, I will have to try that. That sounds like a great idea.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...
I have created a Powershell script to automatically add a Wireless Guest
User on Cisco WLCs. (tested on 2500 Series) The script should be
completely self explanatory. Prerequisites: Powershell SNMP Module
(Install-Module -Name SNMP) SNMP Write Access to y...