This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Orion Core: Setup to startup a Telnet and SSH session from Node Details page link with KiTTY (Putty fork)

One of the nice features that the Orion Web Console has is the ability to start a Telnet or SSH Session when in the Node Details. The selection is available at the top right of the page just under the Export to PDF. ToolsetIntegration-Bar.png

While PuTTY has always been my goto SSH application, the putty developers did not add the ability to connect via SSH through ssh://. I did find that one of the forks of putty called KiTTY is able to do both telnet:// and ssh://

To setup accounts to see the Telnet and SSH buttons at the Top Right of the Node Details page to be able to Telnet and SSH:

  • Go into Settings> Manage Accounts
  • Select the checkbox next to the account(s) and select Edit
  • In the Account Settings, change Allow Browser Integration to Yes and select Submit.

Downloading KiTTY client:

Setting up on the Local System to Telnet or SSH with KiTTY:

     In my example registry script, I have placed KiTTY into C:\kitty\ seen as C:\\kitty\\ in the .reg file. You can right click on the KiTTY_Telnet_SSH.reg file and select Edit, and in Notepad use Ctrl+H and replace C:\\kitty\\ with the folder location of the kitty.exe file.

  • Place kitty.exe into C:\kitty so that it will be executed as C:\kitty\kitty.exe
  • Then in order to be able to use Telnet and SSH you will run the attached KiTTY_Telnet_SSH.reg file.
  • You will need to execute this on every system that wants to connect via telnet or ssh when in the Web Console. It will apply to all users that use the system the registry it is applied to.

I have tested this and it is working successfully in Windows 7, Server 2008 R2, and Server 2012 R2.

KiTTY_Telnet_SSH.reg
  • I noted a post regarding Java; however, there are gaping security issues with Java....and as hard as I'm trying to push Cisco away from using it for their ASA management I find it distasteful in moving the opposite direction wherein I found your post.

    Where this works for those hosts that I can access directly from my desk....I'm looking from something much more elaborate.  For example, I have several APE's all setup with dual NICs.  1 NIC customer facing (172.16/23, 10/8, 192.168/16 networks with no Internet access), and 1 NIC that faces internal management (with Internet access).  I used to use Foglight (Quest product that Dell bought that's no longer supported).  Using this tool I could use the agents (same principal as the APEs) to establish an SSH session with any device seen from the master server (basically right-click, connect, then select Telnet, SSH, or RDP).  In addition, I could setup profiles so that when you connected to the device, username/password info was automatically sent so the NOC staff didn't have to remember 100's of (potentially infinate) username/password combinations.

    So, what functionality I'm looking for is from the Orion NPM with multiple APEs installed, I'm looking for the ability to select a Node and SSH into it (profile info passed so that one goes straight to # prompt) without having to RDP into the customer's APE and from that APE then opening a Putty/KiTTY (or whatever SSH tool is installed on that APE and then put in the IP info followed by the device's credentials just to get access to the # prompt.

    Now if SolarWinds figured out how to do this such that NCM can pull configs via SSH, then one would think that the same ability would exist within the NPM.  Being a "newbie" and only new to the product for 6 "painful" weeks I'm still looking for this last piece of the puzzle.

    Any and all help is appreciated.  It seems that you've gotten further than most...just looking to take it to the next level.

  • Is there any record (logs) in the Orion of these connections?