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
    • 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
    • DataMiner Insights
      • Security
      • System Architecture
      • DataMiner Releases & Updates
    • 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

SNMP TOO BIG Error

Solved1.44K views18th July 2023SNMP
0
Pedro Domingues [SLC] [DevOps Advocate]12 16th June 2021 0 Comments

Hi

I am getting these errors while polling a SNMP device.

I am able to get the values for systemSummaryAlarm() and moduleInfoTable(), but most of the time I get this TOO BIG error :

-> 11:13:10 - Get for systemSummaryAlarm () returned VT_BSTR : 1
-> 11:13:10 - Get for moduleInfoTable () returned VT_ARRAY|VT_VARIANT (12)
0 VT_ARRAY|VT_VARIANT (2)
0 VT_BSTR : 1
1 VT_BSTR : 40
1 VT_ARRAY|VT_VARIANT (2)
0 VT_BSTR : 3
1 VT_BSTR : 0
2 VT_ARRAY|VT_VARIANT (2)
0 VT_BSTR : test
1 VT_BSTR :
3 VT_ARRAY|VT_VARIANT (2)
0 VT_BSTR : 22544
1 VT_BSTR : CPU0086
4 VT_ARRAY|VT_VARIANT (2)
0 VT_BSTR : LH01533
1 VT_BSTR : CP0001...
-> 11:13:15 - Get for systemSummaryAlarm () returned VT_BSTR : 1
-> 11:13:15 - Get for moduleInfoTable () returned VT_ARRAY|VT_VARIANT (12)
0 VT_ARRAY|VT_VARIANT (2)
0 VT_BSTR : 1
1 VT_BSTR : 40
1 VT_ARRAY|VT_VARIANT (2)
0 VT_BSTR : 3
1 VT_BSTR : 0
2 VT_ARRAY|VT_VARIANT (2)
0 VT_BSTR : test
1 VT_BSTR :
3 VT_ARRAY|VT_VARIANT (2)
0 VT_BSTR : 22544
1 VT_BSTR : CPU0086
4 VT_ARRAY|VT_VARIANT (2)
0 VT_BSTR : LH01533
1 VT_BSTR : CP0001...
-> 11:13:16 - Get for hybrid22544MonitoringTable () returned VT_ARRAY|VT_VARIANT (30)
0 VT_ARRAY|VT_VARIANT (1)
0 VT_BSTR : 1
1 VT_ARRAY|VT_VARIANT (1)
0 VT_BSTR : F
2 VT_ARRAY|VT_VARIANT (1)
0 VT_BSTR : O
3 VT_ARRAY|VT_VARIANT (1)
0 VT_BSTR : N
4 VT_ARRAY|VT_VARIANT (1)
0 VT_BSTR : N...
-> 11:13:20 - Get for systemSummaryAlarm () had error : TOO BIG
-> 11:13:20 - Continuing get for systemSummaryAlarm ()
-> 11:13:20 - Get for moduleInfoTable () had error : TOO BIG
-> 11:13:20 - Continuing get for moduleInfoTable ()
-> 11:13:25 - Get for systemSummaryAlarm () had error : TOO BIG
-> 11:13:25 - Continuing get for systemSummaryAlarm ()
-> 11:13:25 - Get for moduleInfoTable () had error : TOO BIG
-> 11:13:25 - Continuing get for moduleInfoTable ()

what does this mean?

Thanks

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

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
0
Bert Vandenberghe [SLC] [DevOps Enabler]8.14K Posted 16th June 2021 0 Comments

In short TOO BIG means that the SNMP request received by the SNMP Agent is too big and the agent is not able to process the request (can happen on devices with limited resources).

Here in your case, you will probably have too many SNMP Gets in one request going to the device. So probably you'll have to limit the number of parameters in that group giving problems, or worst-case fall back on single Gets if the device does not even support multiple Gets in one SNMP request.

Bert Vandenberghe [SLC] [DevOps Enabler] Answered question 16th June 2021
You are viewing 1 out of 2 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