Hello,
I have an two of four Elements Timing out , I see Stream Viewer shows an "Undefined" group ~ Redundant Polling, change connection
I compare side by side timing our and not timing out element / stream viewer windows and see the following undefined group with the following messages
RedundantPolling, change connection, entering 1 RedundantPolling, change connection, leaving 1 RedundantPolling, change connection, entering 0 RedundantPolling, change connection, leaving 0 RedundantPolling, change connection, entering 1
Elements are running same protocol version, devices are running same firmware, nothing has changed, all four were connected until we started noticing timing out. Ive tried duplicating and assigning the element to another DMA but issue persist. Ive checked firewall rules and nothing has changed all SNMP traffic is allow.
Heres a screen shot of groups side by side
Hi Juan,
The connector in question uses the redundant polling feature (docs), which allows DataMiner to switch to a secondary connection if the primary one times out. This is why you are seeing the "change connection" message in the Stream Viewer.
To troubleshoot further, have you tested connectivity to the target IP and Port from the host where DataMiner is installed? You can use PowerShell’s Test-NetConnection cmdlet for this purpose.
If the test is successful, you might also want to use a MIB browser to verify whether the device is responding to SNMP requests. This can help confirm that the SNMP communication is functioning as expected.
Hope this helps!
To update this thread,
we found the issue may have been related between IPX and Magnum. Not sure why when the cache in magnum is full stops snmp traffic or at least as it deletes/gets hits threshold the element timeouts/connects. During our maintenance window we cleared the cache in Magnum and rebooted the IPX. This restore snmp connection to the device.
We never changed protocol.xml file and we are running latest version available for the IPX.
Also we looked at configshell logs between the devices and see immediately there was no SNMP traffic.
This led Evertz too look at cache as possible culprit for the loss of traffic.
Hi Juan,
As I checked the screnshot I was looking for snmp secondary connection can you help me where you from get the snmp connection have you made any changed in protocol.xml file.can you please help