Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We are having a very strange issue trying to connect to our infrastructure switches via SSH. When you first try connecting to them, the switches will prompt for the password - and then just sit there after it is entered.

If you create a second SSH session to the switch (while letting the first one remain open and just sitting there) it will let you log right in.

The switches are doing the same thing with RADIUS and local authentication.

The other strange part to all of this, is that about 10 switches started doing it all at the same time. As far as actual configuration of the switches, nothing has changed.

Occasionally, one switch will start working like normal, but then stop again.

These are all HP ProCurve managed switches, but all different models/firmware.

Some switches that are not working are using the same firmware as others that are working.

UPDATE: 20130312

I am also seeing this same behavior when trying to use telnet. The first telnet session just hangs there, and the second telnet session will let me log in.

Rebooting the switches seems to get them working, but I still have 5 production switches that cannot easily be rebooted because of their production roles.

Is anyone aware of anything else that can be switched on/off that may reset the logon for remote management or something like that?

share|improve this question
    
Which model switches are you using? And does using the serial port work any better? –  tegbains Apr 4 '13 at 7:20
    
It is very strange as it is a bunch of different models (2610, 2810, 2910). The issue is with console, telnet, and SSH. So far only a reboot seems to fix it - have a couple remaining but no luck figuring it out yet. –  BriGuy May 2 '13 at 3:21
    
This has happened to me for quite a long time now and I always need to reboot to overcome - it seems to happen especially after firmware updates and on varying models and versions of procurve. The workaround of logging in twice is enough for me and I then reboot to clear the issue. It would be interesting to know what is causing this though! –  user177816 Jun 14 '13 at 9:44
    
I have had the exact same problem using SSH, i.e. the session 'hangs' after entering the password. However on some occasions I can connect from a different source subnet (provided its permitted in 'ip authorized-managers). On other occasions, I connected via SSH twice, both sessions hung after entering the password, but a third attempt (all from the same source) succeeded (leaving the first two 'hung' sessions open as the OP says). –  user199093 Nov 12 '13 at 15:02
add comment

protected by Chris S Nov 12 '13 at 16:17

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Browse other questions tagged or ask your own question.