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
  • Blog
  • Questions
  • Learning
    • E-learning Courses
    • 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
    • Tutorials
    • 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
    • DataMiner Insights
      • Security
      • Integration Studio
      • System Architecture
      • DataMiner Releases & Updates
      • DataMiner Apps
    • 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
  • Downloads
  • More
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
      • General Inquiries
      • DataMiner DevOps Support
      • Commercial Requests
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

Differing MTU Sizes in one DMS

Solved1.03K views13th July 2023DMS MTU SLNet
5
Jack Perrott-Webb52 25th August 2022 0 Comments

We have a requirement to increase the MTU size of some of the DMAs in our cluster to process jumbo frame MTU. This will mean that these agents will run on 9000 MTU compared to the standard 1500 running on the other agents in the cluster.

However, we have concerns as to what this can lead to for DataMiner - since we only have one NIC Team for these agents, it will be using the same NIC for jumbo frame MTU and for general SLNet comms etc.

Questions:

  1. Are there any known issues having agents communicating over SLNet to each other over differing MTU sizes?
  2. Are there any known issues for other, less obvious, SL Processes due to higher MTU (thinking about SLDataGateway with more data being pulled at once for trending, for example)?
  3. Any other information we should be aware of when modifying MTU size in a cluster (whether single agent or all agents)?

Edit: Bonus Question: We have one Staging environment where we already have this configuration partially established - whilst this doesn't have the same data rate (and smaller in DMS size) as our Production environment, is there anything I should be monitoring in particular as an overall "health check"?

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 13th July 2023

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
5
Bert Vandenberghe [SLC] [DevOps Enabler]8.11K Posted 26th August 2022 0 Comments

Hi Jack,

I don't believe this setting will have any impact on the DataMiner software. MTU is a setting in layer 3, and our software is located in the higher layers. SLNet and SLDataGateway might indeed have a connection to other machines, but the OS should handle the TCP/IP stack correctly with the settings you defined.

The only process I would potentially be worried about, is SLPort. This process is going quite low level in terms of communication and packets going in and out. Yet again, it's using standard TCP or UDP connections of the OS, so I think this will also be transparent for SLPort.

In other words, there are no known issues and we are also not expecting any issues when defining a higher MTU. This setting only defines the max size of the packets on the wire, and the OS should handle this correctly. If this is running fine in your staging environment, connectivity is fine, all data comes in, no timeouts, etc. Then I believe this should be fine in production as well.

Bert

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 13th July 2023
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

Recent questions

Alarm Dashboard PDF/CSV Export 1 Answer | 0 Votes
Is the Microsoft SharePoint Connector Still Usable 0 Answers | 0 Votes
Is the Microsoft SharePoint Connector Still Usable 0 Answers | 0 Votes

Question Tags

adl2099 (115) alarm (62) Alarm Console (82) alarms (100) alarm template (83) Automation (223) automation scipt (111) Automation script (167) backup (71) Cassandra (180) Connector (108) Correlation (68) Cube (150) Dashboard (194) Dashboards (188) database (83) DataMiner Cube (57) DIS (81) DMS (71) DOM (139) driver (65) DVE (55) Elastic (83) Elasticsearch (115) elements (80) Failover (104) GQI (159) HTTP (76) IDP (74) LCA (151) low code app (166) low code apps (93) lowcodeapps (75) MySQL (53) protocol (203) QAction (83) security (88) services (51) SNMP (86) SRM (337) table (54) trending (87) upgrade (62) Visio (539) Visual Overview (345)
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