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.
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.
Hi Alex,
As Wouter mentioned, this is indeed an error that happens when SLSNMPManager does not know about the existence of a certain element.
In order for it to know about an element, at startup, DataMiner tries to register the element with the correct SNMP manager but since SNMPv1 is incompatible with SNMPv2 for some polling options an issue arises since the element still thinks it is SNMPv1 and the connector “asks” for SNMPv2.
Due to the incompatibility, the registration process fails, and once the element starts polling it will behave in a very similar manner as to when an element is still starting up.
Just a restart will not be enough, you will need to edit the element and make sure the connection(s) have SNMPv2 or SNMPv3, and then click ‘Apply’ to make those settings take effect.