Netonix Forums

We are having issues only with Netonix and our Zabbix server. All other manufactures we monitor seem to be fine. We are running firmware 1.4.4

The 2 issues we see monitoring via SNMP are:
1: Monitoring sysUptime reports the wrong uptime which we also see via snmpwalk.
2. We get lots of errors like these in our logs. We use the standard discovery to discover and monitor the interfaces and that works fine, but our logs get filled with these errors.
contains variable bindings that do not match the request: sent ".1.3.6.1.2.1.2.2.1.7.3", received ".1.3.6.1.2.1.2.2.1.8.3"

Any help would be appreciated.

please update to latest release...your code is very old...

And the version you should be upgrading to is v1.4.7rc16 as there were SNMP fixes
ALWAYS UPGRADE TO LATEST VERSION AND REVIEW RELEASE NOTES PLEASE

Tried 1.4.6 and no change. The sysUptime is still reported wrong. We didn't go to the newer firmware because of issues we saw in the forums and we didn't see any fixes for this.

We didn't do 1.4.7 as we don't do beta firmware on production equipment.

mike@surfglobal.net wrote:We didn't do 1.4.7 as we don't do beta firmware on production equipment.

v1.4.7rcX is not BETA it is all the BUGS FIXED that were reported since v1.4.6 was released.

In fact after we release v1.4.7 we are no longer going to use RC and simply will add a "."# to the end

So OK let's pretend you found a bug that is in v1.4.6 we would FIX it and release v1.4.7rcX with the fix but you would refuse to use it?

Try version v1.4.7rcX (the latest version) and see if your issue is still there. If it is there then we will investigate it.

Rc firmware is safe as houses. Beta is kind of a misnomer, as letter builds are used internally for regression testing and validation and are never released.

If you asked me why rc16apr2 was doing something odd, I'd tell you to roll back to rc16 and get off my hard drive.

I'm told after the release of 1.4.7 final we will be revising our naming convention to 1.4.7.1,2,3, etc. due to the misconception that seeing rc in a build number engenders.

Thanks for the info on the firmware versioning. I did try 1.4.7rc16 and it did resolve the port errors we were seeing, but it still doesn't resolve the snmp error on the sysUptime

I have ping our software engineer Eric and hopefully he will chime in soon.

You'll need to be more specific about what you think is wrong with sysUptime.