I have a subtable that I need to poll for a SNMPv2 driver. The OIDs the protocol is polling for matches with the driver, and I have confirmed that the indexes do exist in the device. However, some values just do not show up on DataMiner.
The element’s streamviewer for that particular SNMP group shows that it was unable to read the message with an error code 12, indicating inconsistent value detected.
After using wireshark to capture the SNMP packets, I’ve found that because the values of the problematic columns can contain negative values, it’s raising the following issues in Wireshark:
Is there any way to work around this?
Hi,
The data source seems to be replying with a wrong format. Like Wireshark is indicating, the value type is set as an integer32 (=4 byte) while the value in the response itself contains 5 bytes so that is not valid.
I’m afraid there’s not much that can be done about it. This is something that would have to be fixed on the data source side (e.g. firmware fix) to be able to deal with this.
Regards,
The device is not replying with the correct format as defined in the RFC. On one side it is indicating that the content has a size of 5 bytes, and on the other side it is setting the type of the content to an Integer32 (=4 byte). Like Wireshark is indicating, that is a wrong value length and the library that DataMiner is using will be returning an error code because this response is wrong. This is a firmware issue to be fixed on device side
Hi Laurens, I’ve checked again using GetNext operations on MIB browser, and the values seem to be showing.
I also should mention that the protocol is using a subtable feature to call this information with instance bulk:2, so a getNext + multipleGet operation is performed on DataMiner’s end.