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

Stream Viewer: Element not known yet

Solved1.22K views14th July 2023SNMP stream viewer
2
Alex Johnson [SLC] [DevOps Advocate]836 25th April 2022 0 Comments

Hi Dojo,

When testing snmpv1 and snmpv2, I've been occasionally getting a strange streamviewer message:

This happens when uploading a new protocol (eg: copying and pasting) where the previous protocol was snmpv1 and the new one is snmpv2. The funny thing is, when I switch the version back to a previously released version that uses snmpv1 and then back to the version i'm working on, the stream viewer error goes away.

The customer also reported seeing this error on a few elements when setting an snmpv2 version to production from a previous version that uses snmpv1.

What does this error mean? Is it a software issue? We are on DM 10.2.3.0-11516.

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

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
3
Wouter Demuynck [SLC] [DevOps Advocate]5.94K Posted 26th April 2022 0 Comments

As far as I can see, the error message pops up when a protocol wants to do an SNMP Get and the SLSNMPManager process doesn't know about the element. It will then retry this every second.

I would guess that your case could be a software issue/race condition when switching drivers between SNMP versions, leaving a mismatch between processes.

Another workaround might also be to restart the elements once more after changing the driver.

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