Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

Client side ports in CUBE: how many are open during a connection to a DMA?

Solved173.38K views27th September 2024adl2099 client ports eventing netstat
6
Alberto De Luca [DevOps Enabler]4.58K 17th February 2023 4 Comments

Please, Dojo - I'm trying to detail the exact behaviour of a CUBE client connecting to a DMA via
.NET-Remoting>Eventing (this to facilitate FW configs).

On connection to a DMA, I seem to get at least one connection established, however the client switches to polling mode.

The output of a netstat on the client would show something like this:

It seems the ports in the "high port range"  (49152 through 65535) are allowed on the client - the connection is actually "ESTABLISHED" to port 8004 of the server - via client port 51134, but then why the client has a second connection open in "TIME WAIT" and eventually switches to polling?

Is more than one port required on the client for eventing?

Or could the server be configured to use polling regardless of the connection successfully established between client port 51134 and server port 8004?

Cube settings for the above test were like this:

Any steer will be helpful

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 27th September 2024
Marieke Goethals [SLC] [DevOps Catalyst] commented 7th July 2023

Hi Alberto,
I see that this question has been inactive for some time. Have you found a solution for this yet? If yes, could you share some more information about this, and select the best answer (using the ✓ icon)? If not, you can also contact techsupport@skyline.be for assistance.

Alberto De Luca [DevOps Enabler] commented 26th July 2023

Need to resume testing on this – I seem to have different numbers of connections depending on the environment – I will update the thread as soon as I gather some more data

Marieke Goethals [SLC] [DevOps Catalyst] commented 23rd August 2024

Hi Alberto,
I see that this question has been inactive for a long time. Do you still need more information about this? If not, could you select the best answer to indicate that no further action is needed here?

Marieke Goethals [SLC] [DevOps Catalyst] commented 27th September 2024

As this question has now been inactive for a very long time, I will close it. If you still want more information about this, could you post a new question?

8 Answers

  • Active
  • Voted
  • Newest
  • Oldest
5
Alberto De Luca [DevOps Enabler]4.58K Posted 20th February 2023 2 Comments

Wouter, Rene, Jens adding an additional trace here.
Based on this drawing, I'm led to think that only 1 connection is required from a CUBE client random port (random but in the 49152-->65535 range)
towards port 8004 on the server

however this netstat output shows me more than one port open towards server port 8004 and I'm not able to explain why multiple ports are used - actually 11 ports have an established connection in this example - so a bit strange to see the client reverting to "polling" mode when 11 connections are established towards server port 8004 - any other checks I may have to do?

If the connection is "Established" can I exclude there are any FW still blocking the required port?

Alberto De Luca [DevOps Enabler] Posted new comment 6th March 2023
Bert Vandenberghe [SLC] [DevOps Enabler] commented 20th February 2023

Hi Alberto,
Since you are connected with ‘polling’ instead of ‘eventing’, your Cube client is represented on the left-hand side in the schematic you added in your answer here above, and you only have connections going from your client to the server (towards port 80/443 and port 8004 of that server). The originating ports from where your client machine is initiating the connection, are always random. And there can indeed be multiple connections made at the same time to allow multithreading. A webbrowser will also make multiple connections to port 80/443 of a website when navigating to it, and this will also be originating from a random port in the higher ranges. So the connections we are seeing here, have nothing to do with eventing if I’m not mistaken…

Alberto De Luca [DevOps Enabler] commented 6th March 2023

I’m not understanding why the client connects through polling though.
Options have been added to apply the case in the middle of this diagram.

The server is configured to allow eventing by default, and so are my client side options (configured in CUBE) – the netstat output would also show that the connection is established though one of the client ports in the eventing range – so, when connections are even established, what could still trigger the failback to polling?

You are viewing 1 out of 8 answers, click here to view all answers.
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin