I recently began evaluating Cirrus for a possible wide deployment. We use several models of Cisco routers and switches, and so far I haven't encountered any trouble with these. However, we use a large number of Dell Powerconnects (3424, 3524, and 5324 for the most part) that I am having login issues when using SSH. If I change these switches to telnet (after enabling telnet on the switch of course) the login works. Using telnet long term is not an option, and this may be a deciding factor whether to purchase.
When adding a new node for a Dell Powerconnect I consistently get 'bad password' when verifying the login. While logged in to monitor what the switch is seeing, the connection is rejected. At this point I don't know if there are recommended SSH configurations on the Dell side that I can use, but if so I'd be very interested in a sample that works for others. Alternatively, if there are any options I am not seeing in Cirrus itself other than basic credentials and SSH version I wouldn't mind being pointed in the right direction.
Thanks in advance for any advice.
ScottL, we'd be happy to work with you to get SSH up and running on your Dell devices. To start, it would be helpful if you could post a session trace for the SSH download on those devices:
1) In Cirrus console, navigate to File > Settings > Session Tracing to enable session tracing
2) Perform an SSH download on the failing device. Maybe do a verify login before for good measure.
3) Go to <install dir>\Configuration Management\Session-Trace and copy and paste the session trace into your post
If you're more comfortable emailing the session trace, you can send me a private message instead. Are you currently working with someone on our sales engineering team? I want to ensure they're in the loop.
Chris LaPoint Sr. Product Manager NCM (Cirrus), ipMonitor, LANsurveyor SolarWinds Austin, TX
Thanks for the quick response. I've sent a PM with the requested session trace.
Has there been a resolution to this issue yet, I too have a dell powerconnect 3424 with the latest firmware version, and am running the latest version of orion, and still have issues with ssh logins. telnet works fine.
Scott and I discussed this offline. Based on the session trace provided, this device does not accept username and password when establishing the SSH session. Our SSH state machine expects to already be logged in at the point you see the "Username:" prompt appear and so it just times out waiting for a login prompt. We're tracking this issue internally as #1574 and it's scheduled to be fixed in 5.1
We believe we've addressed this issue in 5.1. If you're are willing to help test this fix using the 5.1 beta build (on a separate machine from your 5.0 production install), please send me a private message.
