The working device CRS1 (Version 6.12) sends a valid value for
msgAuthoritativeEngineTime in its “SNMP report” packet as an answer to the
initiating get-request. This value is then reused for all subsequent SNMP
request/responses during that session.
The failing device CCR1 (Version 6.18) sends a value of “0” for
msgAuthoritativeEngineTime in its “SNMP report” packet as an answer to the
initiating get-request. In this case, the previously existing value for
msgAuthoritativeEngineTime (stemming from last SNMP request against CRS1) is used. This gives the bad results.
So we have questions:
- Why does one device return “valid data”, while the other one does not? Is
there perhaps an issue with the firmware of CRR1?