SSH - NPM 12.0.1 issues?

cnorborg

So, was rather excited about the NPM SSH to allow folks who aren't on a controlled IP to get into our devices.  We lock them down via an ACL and they want some changes made which would require me changing the ACL which I'd rather not do.

So, I checked out this new feature and it seemed to work great.  But the others noticed issues with it where it slows down quite a bit, or doesn't accept keyboard input.  So I started stressing it a bit more.  Noticed if I opened one SSH session to one device it seemed to work mostly ok, maybe some pauses and such.   While this session was still running, opened another to a different device.  This one isn't accepting input at all, while the first is noticeably slow and bursty, ie: it shows nothing on the screen when your typing, but all of a sudden everything you typed is there.

Anyone else having issues with it?

I have noticed on the server in Task Manager, that while I have 2 SSH sessions opened I see 2 processes called "SSH, Telnet and Rlogin client (32 bit)" in the task list.

aLTeReGo

cnorborg​, I can't say I've seen the issue you are describe above in my own environment, even after opening a dozen SSH sessions to different devices simultaneously. A highly distributed architecture could impose some additional latency and delays in the SSH communication, and even a flaky wireless connection could result in some unexpected behavior. If the problem persists however, I would try narrowing down the cause. E.G. eliminate any Additional Web Servers from the equation by accessing the Orion web interface from the main Orion server only. Eliminate any Additional Polling Engines by accessing devices managed directly from the Main Orion server. Use a hardwired connection rather than wireless. SSH to devices local to the main Orion server rather than those accessible via a WAN. Last but not least, give another browser a try. Each browser behaves differently and the problem you are experiencing may be limited to particular browser or version.

If you've tried all these things and the problem continues to persist, please open a case with support so we can further help isolate the cause of the issue.