Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SCP and SFTP

Upgrade to 5.5.2 went nicely...thanks for that !

So now i thought i'd try and play with new SCP server that came with the new version of NCM to automatically backup F5 products (having no luck).

So proceed to test the server using a separate SCP client, and it reveals the error "Server refused to start a shell/command".

Testing using SFTP works fine.

Can anyone else confirm this ?...perhaps i'm doing something wrong?

Any input is much appreciated.

Dave

Find more posts tagged with

Accepted answers

chris.lapoint

Good news. We've updated the SCP server to support both v1 and v2. If you'd like to test out the updated version, please send me an email.

All comments

Derek

Currently NCM 5.5.2 only has a SCP device template for Cisco IOS. We would be interested in working with you to get your device to work with SCP. Please send me the session trace (you can turn on session tracing in the Settings section of the NCM Win32 under Settings)

I'm not sure why your SCP client application could not connect, but it may be related to the fact that the SolarWinds SCP Server does not support SCP1 and only supports SCP2.

Another reason might be related to the fact that the client may be sending unrecognized commands. We did see an issue on a Cisco device SCP server which would not accept an SCP connection could not be established due to a banner being set. That being said we have not seen the issue on the NCM SCP Server. What client are you using for your testing?

dstj

Thanks for the reply Derek.

I'm actually trying to use the SCP server as a standalone server and the F5 device auto backs up to it on daily basis. (no NCM scheduling).

F5 devices fails to connect to it.

And the windows SCP client i'm testing with is called WinSCP.

I think if i can get the WinSCP client to work, i'm thinkin the F5 devices won't have any issues connecting either.

Dave

jswan

Even though there are security problems with SSHv1, it would be nice to see the SCP server support it. Cisco IDS appliances don't yet support SCP with SSHv2. The bug on this (CSCse05771) has been open through two major revisions of the IDS code, so I'm not holding my breath.

chris.lapoint

Good news. We've updated the SCP server to support both v1 and v2. If you'd like to test out the updated version, please send me an email.