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

Executing a script using SSH vs Telnet

We want to apply some config changes to a bunch of Cisco switches using the Execute Script in NCM. The problem is that NCM, by default, pushes these changes using Telnet. First off, how do we change it so that it uses SSH? And can we change it globally, so that NCM by default uses SSH instead of Telnet?

Thanks.

Find more posts tagged with

config_change

ssh

execute_script

telnet

Accepted answers

chris.lapoint

You'll need to go to the NCM client application (on your NCM server). If you select a device in the tree and edit its device details, you will see a Communication section. You'll see a list of transfer options for executing scripts and transferring configs (Telnet, SSH Auto, etc.).

If you want to set this globally, leave the device settings and go to File > Settings > Global Macro Settings > Transfer Protocols.

All comments

chris.lapoint

If you want to set this globally, leave the device settings and go to File > Settings > Global Macro Settings > Transfer Protocols.

jedi755

You can also edit multiple nodes at once by highlighting them in the node list, right clicking and choosing "edit multiple nodes". This is helpful if you have a mixed telnet/ssh environment.

mleinio

Note that if you import nodes from NPM, NCM always resets the transfer options for merged existing nodes.

So, for example, if you had default connection method set as SSH but then you have some nodes manually set as Telnet, after doing an NPM import, all nodes try to use SSH.

There is ticket 91668 open in the support (about the all the import problems we are facing), but for some reason I don't get any answers to this issue.

chris.lapoint

Are you using the scheduled Orion Node import job or are you using the File > Import Devices? The Orion Node import job should merge properly.