Digi Remote Manager - "SESSION NOT INITIALIZED: Concurrent session limit reached" when connecting to ~100 devices via API

Digi Remote Manager Web Services (API)
1

Digi Remote Manager - “SESSION NOT INITIALIZED: Concurrent session limit reached” when connecting to ~100 devices via API

Hi everyone,

We’re building our own platform that communicates with Digi-connected devices using our own backend APIs.

Our use case requires establishing terminal/shell sessions with approximately 100 Digi devices concurrently. However, once multiple sessions are opened in parallel, we begin receiving the following error:

At the time of the below screen shot there was only 1 active connection to the Digi for that particular device and yet I face this issue where i see “Concurrent session limit reached” How can i resolve this.

img
img1152×720 39.9 KB

SESSION NOT INITIALIZED
Concurrent session limit reached

I’ve attached a screenshot of the error for reference.

Current Setup

  • Approximately 100 Digi-connected devices
  • Connections are initiated programmatically through our backend APIs
  • We need to support a high number of concurrent terminal sessions
  • Sessions are created automatically rather than manually through the Digi Remote Manager UI

Questions

  1. Is there a configurable limit on the number of concurrent terminal sessions in Digi Remote Manager?
  2. If so, can this limit be increased (account-level, organization-level, device-level, or server-side)?
  3. Are there any recommended best practices for supporting a large number of simultaneous terminal sessions?
  4. Is session pooling or session reuse recommended instead of creating a new terminal session for each request?
  5. Has anyone successfully supported 100+ concurrent terminal sessions? If so, what architecture or approach did you use?

Additional Information

Our goal is to execute commands on many devices in parallel with minimal latency. We’re trying to understand whether this limitation is:

  • A licensing restriction
  • An account or organization configuration limit
  • A device firmware limitation
  • An API limitation
  • Or simply a recommended concurrency threshold

Any guidance, documentation, or suggestions would be greatly appreciated.

Thank you!

2

I am not sure I understand what it is you are doing. Are you creating a service that creates more than 100 connections to a devices Console?

3

Yes we did a create a service that is capable of running each digi console connection on independent threads/processes for checking modifying configs etc. Now the challenge that we are facing is that, even for a single single device with only a single connection, the connection to the console is being terminated stating the above reason.

I would appreciate you insights on this issue

4

What is the exact product you are working with?

What firmware version is installed on that device?

5

We’re using Juniper JFX devices 250 and 350 models and the versions being 18 and 24

6

Perhaps I need to be more specific. What is the part number of the Digi device you are working with?

7

@harsh_98 , there is a 5 concurrent session limit on Digi Remote Manager per account, so this is no doubt why you’re running into that error. Being that’s a per-account limit platform-wide, there is no way to increase that.

If this is a policy which you’re in disagreement with, you’ll want to take that up through your Digi Sales channel, who can then describe your use-case to Digi Product Management (who may then evaluate your request further), or perhaps different solution involving the python support on your device? Digi has a Professional Development Services group which could discuss alternative applications with you, which might stay within the established limits.

One other thing you could do is make use of the Feedback option when logged into your Digi Remote Manager account, as that would also go straight to a PM/engineering team for evaluation. Hope these suggestions help!

2 Likes
8

Can you please confirm if the concurrency limit is based on device or an Account. Based on the information provided by one of my colleagues it’s based on devices and he seems to have gotten this info form digi support.

Your confirmation on this would help us plan our next action

.

9

Hi @harsh_98, I did mention that this is a per account limit, so I’ve boldened those statements now in my previous comment. I’ve worked with customers that have hit that before, which is how I knew the answer so I could reply you.