BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

ssh access to OA takes 30 seconds?

Doug O'Leary
Honored Contributor

ssh access to OA takes 30 seconds?

Hi;

 

I have four full blade enclosures, two each in two different data centers.  I can access onboard admins for the two enclosures in our primary DC in less than 3 seconds via ssh.  The two OAs for the other DC take 30 seconds before I get a password prompt.  

 

If these were standard UNIX/Linux systems, I'd suspect a name resolution issue as that's invariably ssh trying to do reverse IP lookups.  But, as far as I can tell and test, name resolution is working on all the enclosures.  In fact, as far as I can tell, the enclosure configs are exactly the same (differences in IP/network addressing, obviously).

 

It's not a secondary DC networking issue as there are close to 700 hosts in that secondary DC and it's only the enclosures which are showing this 30 second delay.  

 

Has anyone seen this before and/or have a tip on where I should look for the config difference?

 

Any hints/tips/suggestions greatly appreciated.

 

Doug O'Leary


------
Senior UNIX Admin
O'Leary Computers Inc
linkedin: http://www.linkedin.com/dkoleary
Resume: http://www.olearycomputers.com/resume.html
2 REPLIES
Doug O'Leary
Honored Contributor

Re: ssh access to OA takes 30 seconds?

Hey;

 

Turns out its not an enclosure issue.  It's specific to my linux desktop.  Putty, from a windows workstation, goes right in, so does ssh from a vmware linux guest.  

 

I actually know ssh fairly well; but, damned if I can think of a ssh config that would have this issue on these OAs like this.  I've checked 

* ~/.ssh/config

* ~/.ssh/known_hosts (no duplicates, garbled, etc)

* name resolution works forward and reverse

 

Anyone have any hints, I'll gratefully take 'em.

 

Thanks

 

Doug O'Leary


------
Senior UNIX Admin
O'Leary Computers Inc
linkedin: http://www.linkedin.com/dkoleary
Resume: http://www.olearycomputers.com/resume.html
Doug O'Leary
Honored Contributor

Re: ssh access to OA takes 30 seconds?

Hey;

 

I found what it's hanging on.  After I realized it wasn't an enclosure issue, I dove into the configuration on my system.  Turns out, the ssh session/enclosures, something, doesn't like my ssh-agent running.  I worked around the problem by creating a per-host ssh config in ~/.ssh/config setting:

 

host ${host}

    hostname ${host}

    pubkeyauthentication no

 

lets me in at speed.  Not sure why one set of enclosures works and another doesn't, but that's a different troubleshooting exercise.

 

Hope this helps someone.

 

Doug O'Leary


------
Senior UNIX Admin
O'Leary Computers Inc
linkedin: http://www.linkedin.com/dkoleary
Resume: http://www.olearycomputers.com/resume.html