unable to access controller via http/ssh

Unanswered Question
Jun 26th, 2008
User Badges:

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.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Scott Fella Thu, 06/26/2008 - 09:17
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

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.

Robert Rowland III Thu, 06/26/2008 - 09:44
User Badges:

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.

j.delossantos Thu, 06/26/2008 - 09:54
User Badges:


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?



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.



This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode