topic Re: unable to access controller via http/ssh in Wireless

unable to access controller via http/ssh

j.delossantos — Sat, 03 Jul 2021 23:05:11 GMT

We are running 4.2.112 code on the 2 controllers on our WiSM blade. While making multiple ldap/local EAP changes on one of the controllers via http, that particular controller becomes inaccessible via http/ssh but it still processes traffic and it can still be configured by using WCS. We just reboot from WCS to regain access.

Is this a known bug? Anyone else experiencing the same problem?

What is the most stable code release?

Thanks in advance for any input.

Re: unable to access controller via http/ssh

Scott Fella — Thu, 26 Jun 2008 16:17:08 GMT

I haven't heard of that issue on any 4.1 or 4.2 code.. only 5.0. If you don't have any 1252 ap's to support, 4.1.185 is a very stable code.

Re: unable to access controller via http/ssh

Robert Rowland III — Thu, 26 Jun 2008 16:44:27 GMT

can you get to the controller from the 6500 via

"session slot xx processor yy" ?

where xx is the blade number and yy is 0 or 1.

and/or does it recover on its own after awhile ?

I have seen lack of connectivity but it does recover.

Re: unable to access controller via http/ssh

j.delossantos — Thu, 26 Jun 2008 16:54:04 GMT

Scott,

Good info, thank you. Yes we do not have 1252s but I think we will need the LDAP features of 4.2. Does 4.1.185 have similar LDAP features as 4.2?

---

Robert,

I haven't tried that since it is much easier to just reboot, it's just a test setup for now. But I will try it your suggestion the next time it occurs.

Thanks to both of you.