Buy or Renew
Buy or Renew
Cisco Virtual Engineer generative AI bot now active in Wireless Discussion Forum. Learn more.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1068
Views
0
Helpful
23
Replies

WiSM rebooting randomly

Victor Fabian
Level 1
Level 1

‎05-13-2009 09:45 AM - edited ‎07-03-2021 05:35 PM

I have 3 WiSMs two of them (WiSM-a and WiSM-b) are seated on the CORE1 switch (6509) and the WiSM-c is seated on CORE2 also a 6509 .

One of the controllers from WiSM-a/b keeps rebooting let's called it Con-1a and Con-2b reboots but usually more than the other one the controllers (WiSM located on CORE2 never reboot .

Both COREs have the same software code. The WiSM have been online for about a year with 4.2.99.0 version and they never rebooted until 3 months from now so a Cisco Tech suggested upgrading to 4.2.176.0 but it keeps doing it .

""IOS (tm) s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXF9, REL"

Thank you

Vic

Labels:
0 Helpful
23 Replies 23

George Stefanick
VIP Alumni
VIP Alumni

‎05-13-2009 09:08 PM

check the crash logs on the controller ... do these show anything?

"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
___________________________________________________________
0 Helpful

Victor Fabian
Level 1
Level 1
In response to George Stefanick

‎05-14-2009 05:09 AM

It doesn't show anything , somebody suggested removing the service vlan from all the trunks but that didn't help .

Could SSH cause problems on the Wireless controllers ??

0 Helpful

Victor Fabian
Level 1
Level 1
In response to Victor Fabian

‎05-14-2009 05:20 AM

Does anybody knows what debug i can use to troubleshoot what the controllers does while i am login through SSH ?

0 Helpful

jeff.kish
Level 7
Level 7
In response to Victor Fabian

‎05-14-2009 05:28 AM

Hate to say it, but debugs are really Cisco TAC's specialty. Not a lot of forum users really know detailed debugs like what you're looking for.

What you have may well be a hardware issue that requires a replacement. I'd open a TAC case and see where it goes.

Sorry for not being able to help :/

0 Helpful

b.smeets
Level 1
Level 1

‎05-15-2009 01:08 AM

We experienced exactly the same problem for months, driving us and Cisco crazy. The cause is an as yet unsolved ssh bug in all codes up to and including at least 4.2.176.0. Cisco told us we were almost the only user in the world having this problem, so I'm "glad" here's another victim. Try this workaround: enable an ACL in the controllers, blocking all ssh traffic (TCP port 22) from 'any' to the controller's interface in all VLANs associated to wireless clients.

0 Helpful

Victor Fabian
Level 1
Level 1
In response to b.smeets

‎05-15-2009 05:08 AM

But did that completely resolve the issue???

Because this is driving me nuts

0 Helpful

b.smeets
Level 1
Level 1
In response to Victor Fabian

‎05-15-2009 06:37 AM

Well, the controllers have never crashed since then, so for me it's over. But Cisco never told us if they resolved the bug yet.

0 Helpful

ericgarnel
Level 7
Level 7
In response to b.smeets

‎05-15-2009 05:25 AM

How was this workaround discovered? It sounds like this bug could be a huge security issue! Have you tested whether or not ssh traffic from a wlan to the controller has an impact?

0 Helpful

b.smeets
Level 1
Level 1
In response to ericgarnel

‎05-15-2009 06:46 AM

It took Cisco's TAC people months of studying several crash files and reproducing our configuration in their labs, and only the fifth (or so) patch at last worked. And speaking of security, we noticed many many ssh connections from the wired Internet to this controller port which apparently slipped through the firewall - you might call it a continuous DoS attack that every few weeks succeeds. So, a hole in our firewall revealed an obscure ssh bug in the controllers. Ssh connections from the WLAN did not seem to have any impact.

0 Helpful

Victor Fabian
Level 1
Level 1
In response to b.smeets

‎05-15-2009 05:39 AM

What is the purpose of TCP port 22 ?

0 Helpful

b.smeets
Level 1
Level 1
In response to Victor Fabian

‎05-15-2009 06:53 AM

Logging in to the controller's console using ssh (instead of telnet) for management purposes. Usually you use http or manage controllers via the WCS, but some management commands can only be issued from the console. But then you connect to the controller's management IP address, never to its WLAN interface address, so shutting off this WLAN interface for ssh is shutting off something you don't need.

0 Helpful

Victor Fabian
Level 1
Level 1
In response to b.smeets

‎05-15-2009 07:53 AM

Can you please provide me the command that you use to implement it ?

thank you

Vic

0 Helpful

b.smeets
Level 1
Level 1
In response to Victor Fabian

‎05-18-2009 01:51 AM

We've done it from the WCS. Here are the relevant screenshots. For 'IP address' you should fill in the controller's address in the wireless clients' subnet, not the management subnet.

Preview file
171 KB
0 Helpful

Victor Fabian
Level 1
Level 1
In response to b.smeets

‎05-19-2009 04:36 AM

What do you mean by this ?

For 'IP address' you should fill in the controller's address in the wireless clients' subnet .

0 Helpful
Getting Started

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:

Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card