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
    • YouTube Videos
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Agility
      • Book your Agile Fundamentals training
      • Book you Kanban workshop
      • Learn more about 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)
    • >> Go to DataMiner Docs
  • DevOps
    • About the DevOps Program
    • Sign up for the DevOps Pogram
    • DataMiner DevOps Support
    • Feature Suggestions
  • Swag Shop
  • Downloads
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Solutions
    • Deal Registration
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
    • Global Feedback Survey
  • >> Go to dataminer.services

Need Help Configuring Net Insight Nimbra Connector

82 views23rd June 2025Net Insight Nmmbra
2
Mike Dilworth [DevOps Advocate]46 20th June 2025 1 Comment

We are trying to connect into a Net Insight Nimbra frame for monitoring using the Net Insight Nimbra connector, but cannot make a successful connection.

A firewall between the DM node and the Nimbra device has a rule to allow UDP traffic on ports 161 and 162.

Attached is a screen capture showing the configuration of the Nimbra SNMP, and the DataMiner configuration.

Are there any other steps required to set this connector up?

João Severino [SLC] [DevOps Catalyst] Answered question 23rd June 2025
Mike Dilworth [DevOps Advocate] commented 20th June 2025

For reference: We are running a Nimbra 688 chassis with firmware version GX6.3. We have version 4.1.3.13 of the connector installed.

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
1
João Severino [SLC] [DevOps Catalyst]13.40K Posted 23rd June 2025 2 Comments

Hi Mike,

According to the documentation it appears you have configured things correctly.

Could you check using the Stream Viewer or the element log file to see if there is any indication of an error?

João Severino [SLC] [DevOps Catalyst] Posted new comment 25th June 2025
Mike Dilworth [DevOps Advocate] commented 24th June 2025

Here is the output of the stream viewer:
-> 14:28:52 – Get for itsIf2022rxStreamTable () had error : TIMEOUT
-> 14:28:52 – Retrying get for itsIf2022rxStreamTable ()
-> 14:28:57 – Get for itsIf2022rxStreamTable () had error : TIMEOUT
-> 14:28:57 – Retrying get for itsIf2022rxStreamTable ()
-> 14:29:02 – Get for itsIf2022rxStreamTable () had error : TIMEOUT
-> 14:29:02 – Continuing get for itsIf2022rxStreamTable ()
-> 14:29:08 – Get for etsTxStatisticsSNMPTable () had error : TIMEOUT
-> 14:29:08 – Retrying get for etsTxStatisticsSNMPTable ()
-> 14:29:13 – Get for etsTxStatisticsSNMPTable () had error : TIMEOUT

And here is the log – I don't see any specific errors.
Logfile "Nimbra Test Node" from agent "10.114.69.58"…

2025/06/23 09:01:07.192|SLLog|ApplyLogLevels|CRU|-1|Log Levels: Info: 5; Error: 5; Debug: 5 (init)
2025/06/23 09:01:07.198|SLDataMiner.exe – Nimbra Test Node|4484|CElement::SetState|DBG|0|** Setting state finished.
2025/06/23 09:01:07.199|SLDataMiner.exe – Nimbra Test Node|4484|CElement::CreateObjects|INF|-1|** Creating objects for element Nimbra Test Node (19)
2025/06/23 09:01:07.199|SLDataMiner.exe – Nimbra Test Node|4484|CElement::Start|INF|-1|** Creating objects for element Nimbra Test Node (19)
2025/06/23 09:01:07.225|SLDataMiner.exe – Nimbra Test Node|4484|CElement::GetPortInfoAsString|DBG|5|0 0 3 0 2 0 3 0 5000 161 10.232.91.26 30000 0 0 0 -1 0 0 0 0
2025/06/23 09:01:07.226|SLProtocol – 17768 – |13872|CProtocol::InitFunc|CRU|0|– Start Init
2025/06/23 09:01:07.226|SLProtocol – 17768 – |13872|CProtocol::Init|INF|1|Creating protocol NetInsight Nimbra
–> version Production (4.1.3.13)
–> instance GUID abd67d6e-b426-4fe1-a060-8239da63d9a4

2025/06/23 09:01:07.228|SLProtocol – 17768 – |13872|CProtocol::InitFunc|CRU|0|ReadSettings
2025/06/23 09:01:07.229|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|INF|0|Reloading notify protocol command factory after reading out settings
2025/06/23 09:01:07.257|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|Log elementInProtocol
2025/06/23 09:01:07.262|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeMetrics
2025/06/23 09:01:07.262|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeDefinitions
2025/06/23 09:01:07.262|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|Start Priority thread
2025/06/23 09:01:07.262|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeParameters
2025/06/23 09:01:07.263|SLProtocol – 17768 – Nimbra Test Node|10864|CProtocol::ProtocolThreadFunc|CRU|0|[NetInsight Nimbra/4.1.3.13] Nimbra Test Node – ProtocolThread | Name: Priority Protocol Thread
2025/06/23 09:01:07.264|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::LoadElementDataAllPIDs|CRU|-1|Querying elementdata
2025/06/23 09:01:07.268|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::LoadElementDataAllPIDs|CRU|-1|Querying elementdata completed
2025/06/23 09:01:07.268|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitializeParameters|CRU|-1|Begin processing parameters
2025/06/23 09:01:07.286|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitializeParameters|CRU|-1|Done processing parameters
2025/06/23 09:01:07.286|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeCommands
2025/06/23 09:01:07.286|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeResponses
2025/06/23 09:01:07.286|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializePairs
2025/06/23 09:01:07.286|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeGroups
2025/06/23 09:01:07.286|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeTimers
2025/06/23 09:01:07.286|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeTriggers
2025/06/23 09:01:07.286|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeActions
2025/06/23 09:01:07.287|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeQActions
2025/06/23 09:01:07.289|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|Cleaning QAction Instances
2025/06/23 09:01:07.289|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeSessions
2025/06/23 09:01:07.289|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|SetupParameters 2674(#) * 800(b) = 2139200
2025/06/23 09:01:07.512|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|LinkReadWrite
2025/06/23 09:01:07.513|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeAlarmLevelLinks
2025/06/23 09:01:07.513|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeReplication
2025/06/23 09:01:07.513|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|InitializeVirtualFunctionBinding
2025/06/23 09:01:07.513|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|SetupCommands 0(#) * 208(b) = 0
2025/06/23 09:01:07.513|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|SetupResponses 0(#) * 400(b) = 0
2025/06/23 09:01:07.513|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|SetupPairs 0(#) * 144(b) = 0
2025/06/23 09:01:07.513|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|SetupGroups 90(#) * 208(b) = 18720
2025/06/23 09:01:07.513|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|SetupTimers 5(#) * 864(b) = 4320
2025/06/23 09:01:07.513|SLProtocol – 17768 – Nimbra Test Node|13872|CTimer::InitTimerThread|DBG|2| Timer thread started (0000000000008E80 – 16320) (bInitial = 1, m_uiDataDisplayTime = -1, m_uiTime = 1000)
2025/06/23 09:01:07.513|SLProtocol – 17768 – Nimbra Test Node|13872|CTimer::InitTimerThread|DBG|2| Timer thread started (0000000000005920 – 13020) (bInitial = 1, m_uiDataDisplayTime = -1, m_uiTime = 60000)
2025/06/23 09:01:07.513|SLProtocol – 17768 – Nimbra Test Node|16320|CTimer::TimerThreadFunc|DBG|2|Launched Timer thread
2025/06/23 09:01:07.514|SLProtocol – 17768 – Nimbra Test Node|13872|CTimer::InitTimerThread|DBG|2| Timer thread started (0000000000002E3C – 23736) (bInitial = 1, m_uiDataDisplayTime = -1, m_uiTime = 10000)
2025/06/23 09:01:07.514|SLProtocol – 17768 – Nimbra Test Node|13020|CTimer::TimerThreadFunc|DBG|2|Launched Timer thread
2025/06/23 09:01:07.514|SLProtocol – 17768 – Nimbra Test Node|23736|CTimer::TimerThreadFunc|DBG|2|Launched Timer thread
2025/06/23 09:01:07.514|SLProtocol – 17768 – Nimbra Test Node|13872|CTimer::InitTimerThread|DBG|2| Timer thread started (00000000000075EC – 24432) (bInitial = 1, m_uiDataDisplayTime = -1, m_uiTime = 3600000)
2025/06/23 09:01:07.514|SLProtocol – 17768 – Nimbra Test Node|13872|CTimer::InitTimerThread|DBG|2| Timer thread started (00000000000061CC – 17576) (bInitial = 1, m_uiDataDisplayTime = -1, m_uiTime = 90000)
2025/06/23 09:01:07.514|SLProtocol – 17768 – Nimbra Test Node|24432|CTimer::TimerThreadFunc|DBG|2|Launched Timer thread
2025/06/23 09:01:07.514|SLProtocol – 17768 – Nimbra Test Node|13872|CTimer::InitTimerThread|DBG|2| Timer thread not started (bInitial = 0, m_uiDataDisplayTime = -1, m_uiTime = 30000)
2025/06/23 09:01:07.514|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|SetupActions 191(#) * 136(b) = 25976
2025/06/23 09:01:07.514|SLProtocol – 17768 – Nimbra Test Node|17576|CTimer::TimerThreadFunc|DBG|2|Launched Timer thread
2025/06/23 09:01:07.514|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|SetupTriggers 102(#) * 168(b) = 17136
2025/06/23 09:01:07.515|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|MakeCommands
2025/06/23 09:01:07.515|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|SetupQActions 117(#) * 344(b) = 40248
2025/06/23 09:01:07.519|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|SetupSessions 0(#) * 280(b) = 0
2025/06/23 09:01:07.519|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|– Total not filled in size is 2245600 b
2025/06/23 09:01:07.519|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::InitFunc|CRU|0|– Done Init
2025/06/23 09:01:07.520|SLDataMiner.exe – Nimbra Test Node|4484|CElement::InitializeElement_SLElement|DBG|-1|Initializing SLElement…
2025/06/23 09:01:07.522|SLElement.exe|9952|CElement::InitFunc|DBG|-1|** Initializing IElement …
2025/06/23 09:01:07.522|SLElement.exe|9952|CElement::ReadSettings|DBG|-1|** Read Settings…
2025/06/23 09:01:07.523|SLElement.exe|9952|CElement::ReadSettings|DBG|-1|** Initialize Connections…
2025/06/23 09:01:07.523|SLElement.exe|9952|CElement::ReadSettings|DBG|-1|** Read Settings Complete…
2025/06/23 09:01:07.523|SLElement.exe|9952|CElement::InitFunc|DBG|-1|** Initializing IElement Complete…
2025/06/23 09:01:07.523|SLDataMiner.exe – Nimbra Test Node|4484|CElement::InitializeElement_SLElement|DBG|-1|Notifying view settings…
2025/06/23 09:01:07.523|SLDataMiner.exe – Nimbra Test Node|4484|CElement::Start|DBG|-1|Starting protocol…
2025/06/23 09:01:07.523|SLLog|ApplyLogLevels|CRU|-1|Log Levels: Info: 0; Error: 0; Debug: 0 (custom)
2025/06/23 09:01:07.523|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::Start|CRU|-1|Starting SLElement
2025/06/23 09:01:07.523|SLElement.exe|9952|CElement::StartFunc|CRU|-1|** Starting
2025/06/23 09:01:07.523|SLElement.exe|9952|CElement::LoadProtocol|DBG|-1|** Loading protocol
2025/06/23 09:01:07.523|SLElement.exe|9952|CElement::LoadProtocol|CRU|-1|** Read Templates
2025/06/23 09:01:07.523|SLElement.exe|9952|CElement::LoadProtocol|CRU|-1|** Read Templates
2025/06/23 09:01:07.524|SLElement.exe|9952|ElementStarter::LoadDescriptionParameters|CRU|-1|** Loading parameters from description.xml.
2025/06/23 09:01:07.524|SLElement.exe|9952|ElementStarter::LoadProtocolParameters|CRU|-1|** Loading parameters from protocol's xml.
2025/06/23 09:01:07.525|SLElement.exe|9952|ElementStarter::LoadControlProtocolParameters|CRU|-1|** Loading parameters from element control protocol.
2025/06/23 09:01:07.569|SLElement.exe|9952|CElement::ReadDB|DBG|-1|** Read DB
2025/06/23 09:01:07.580|SLElement.exe|9952|CElement::ReadDB|DBG|-1|** Completed Read DB
2025/06/23 09:01:07.580|SLElement.exe|9952|CElement::NotifyAlarmState|DBG|0|** Element Alarmstate changed to 7.
2025/06/23 09:01:07.580|SLElement.exe|9952|CParameter::SetElementState|DBG|0|** parameter alarmstate 64501// from 0 to 7
2025/06/23 09:01:07.580|SLElement.exe|9952|CElement::NotifyAlarmState|DBG|0|** Element Alarmstate changed to 7.
2025/06/23 09:01:07.580|SLElement.exe|9952|CElement::StartFunc|CRU|-1|** Setting alarm count
2025/06/23 09:01:07.580|SLElement.exe|9952|CElement::StartFunc|CRU|-1|** Initializing alarm socket
2025/06/23 09:01:07.580|SLElement.exe|9952|CElement::StartFunc|CRU|-1|** Checking masked info
2025/06/23 09:01:07.584|SLElement.exe|9952|CElement::StartFunc|CRU|-1|** Setting trend info
2025/06/23 09:01:07.584|SLElement.exe|9952|CElement::StartFunc|CRU|-1|** Notifying connected elements
2025/06/23 09:01:07.584|SLElement.exe|9952|CElement::StartFunc|CRU|-1|** Start Complete
2025/06/23 09:01:07.588|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::StartFunc|CRU|-1|LoadProperties returnes. 0x00000000
2025/06/23 09:01:07.588|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::Start|CRU|-1|Initializing Port
2025/06/23 09:01:07.588|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::Start|CRU|-1|Starting Timers
2025/06/23 09:01:07.588|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::StartTimers|CRU|0|Starting protocol thread.
2025/06/23 09:01:07.588|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::Start|CRU|-1|Starting Protocol done
2025/06/23 09:01:07.588|SLDataMiner.exe – Nimbra Test Node|4484|CElement::Start|DBG|-1|Complete.
2025/06/23 09:01:07.588|SLDataMiner.exe – Nimbra Test Node|4484|CElement::SetState|DBG|0|** Setting state from 1 to 10 (RealState = 4)
2025/06/23 09:01:07.588|SLProtocol – 17768 – Nimbra Test Node|25840|CProtocol::ProtocolThreadFunc|CRU|0|[NetInsight Nimbra/4.1.3.13] Nimbra Test Node – ProtocolThread | Name: Main Protocol Thread
2025/06/23 09:01:07.588|SLProtocol – 17768 – Nimbra Test Node|25840|CProtocol::ProtocolThreadFunc|DBG|0|– Waiting for Polling to be enabled.
2025/06/23 09:01:07.588|SLDataMiner.exe – Nimbra Test Node|4484|CElement::Activate|DBG|0|** Alarm template : <No monitoring>
2025/06/23 09:01:07.588|SLDataMiner.exe – Nimbra Test Node|4484|CElement::Activate|DBG|0|** Trend template : <No Trending>
2025/06/23 09:01:07.588|SLDataMiner.exe – Nimbra Test Node|4484|CElement::InitializeLock|DBG|0|** Initializing lock status
2025/06/23 09:01:07.589|SLProtocol – 17768 – Nimbra Test Node|25840|CProtocol::ProtocolThreadFunc|DBG|0|– Polling enabled.
2025/06/23 09:01:07.591|SLDataMiner.exe – Nimbra Test Node|4484|CElement::InitializeLock|DBG|0|** Not locked.
2025/06/23 09:01:07.591|SLDataMiner.exe – Nimbra Test Node|4484|CElement::NotifyRedundancy|DBG|0|** Redundancy Changes
2025/06/23 09:01:07.591|SLDataMiner.exe – Nimbra Test Node|4484|CElement::NotifyServiceTriggers|DBG|0|** Service Triggers
2025/06/23 09:01:07.611|SLElement.exe|9952|CElement::NotifyAlarmState|DBG|0|** Element Alarmstate changed to 7.
2025/06/23 09:01:07.625|SLElement.exe|9952|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 09:01:07.625|SLElement.exe|9952|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 09:01:07.625|SLElement.exe|9952|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 09:01:07.625|SLElement.exe|9952|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 09:01:07.625|SLElement.exe|9952|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 09:01:07.625|SLElement.exe|9952|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 09:01:17.091|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::HandleAnotherTelnetClient|DBG|0|Telnet clients connected Primary = 1, Derived = 0
2025/06/23 09:03:07.729|SLProtocol – 17768 – Nimbra Test Node|13872|CProtocol::HandleAnotherTelnetClient|DBG|0|Telnet clients disconnected
2025/06/23 09:03:16.723|SLElement.exe|21640|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 11:23:12.332|SLElement.exe|27644|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 11:23:12.332|SLElement.exe|27644|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 11:23:12.332|SLElement.exe|27644|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 11:23:12.332|SLElement.exe|27644|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 11:23:12.332|SLElement.exe|27644|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/23 11:23:12.332|SLElement.exe|27644|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 02:54:30.489|SLElement.exe|27400|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 02:54:30.489|SLElement.exe|27400|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 02:54:30.489|SLElement.exe|27400|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 02:54:30.489|SLElement.exe|27400|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 02:54:30.489|SLElement.exe|27400|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 02:54:30.489|SLElement.exe|27400|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:16.083|SLElement.exe|22140|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:16.083|SLElement.exe|22140|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:16.083|SLElement.exe|22140|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:16.083|SLElement.exe|22140|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:16.083|SLElement.exe|22140|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:16.083|SLElement.exe|22140|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:44.019|SLElement.exe|30640|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:44.019|SLElement.exe|30640|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:44.019|SLElement.exe|30640|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:44.019|SLElement.exe|30640|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:44.019|SLElement.exe|30640|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 11:53:44.019|SLElement.exe|30640|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 14:25:05.661|SLElement.exe|27512|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 14:25:05.661|SLElement.exe|27512|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 14:25:05.661|SLElement.exe|27512|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 14:25:05.661|SLElement.exe|27512|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 14:25:05.661|SLElement.exe|27512|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 14:25:05.661|SLElement.exe|27512|SubscriptionManager::UpdateSubscribers|INF|-1|subscribe (400082/19): 4294967295/4294967295/-1
2025/06/24 14:28:48.135|SLProtocol – 17768 – Nimbra Test Node|12208|CProtocol::HandleAnotherTelnetClient|DBG|0|Telnet clients connected Primary = 1, Derived = 0
2025/06/24 14:30:10.642|SLProtocol – 17768 – Nimbra Test Node|12208|CProtocol::HandleAnotherTelnetClient|DBG|0|Telnet clients disconnected
**********

João Severino [SLC] [DevOps Catalyst] commented 25th June 2025

Hi Mike, given that StreamViewer is showing Timeouts and considering that what you are trying to poll are tables which in some devices can contain large amounts of data I would suggest you to increase the 'Timeout of a single command (ms)" value from the default to something larger like 5000 ms or even 10000 ms.
This should allow us to determine whether the issue is simply that it takes a bit longer to poll the device or if there is another underlying issue.

You are viewing 1 out of 1 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