Netonix Forums

I posted this is another topic but it looks like we have two different issues going on.

I have Solarwinds deployed and since updating to firmware 1.4.5rc7 the Netonix switches are reporting their interface speeds to be 7Gb. Then on the next poll the interface speed will change to 78Gb or some other random number. This is causing my event logs to fill up on the server because we have multiple Netonix switches.

Also another issue I noticed is that the "Last boot" date keeps changing but its actually not rebooting..

So basically I am having an issue with SNMP not reporting correctly after the firmware update.

we are investigating this issue for you...

I installed Solarwinds and let it run overnight, seems to be working fine. The "Last Boot" time is wrong, but it isn't changing.



Is there anything in the switch log?

Nope, just a bunch of ntp client issues which was why we upgraded firmware was to see if that would correct the NTP issue. Thats a seperate issue at the moment.


Jan 7 05:18:36 system: starting ntpclient
Jan 7 05:18:48 system: starting ntpclient
Jan 7 05:18:59 system: starting ntpclient
Jan 7 05:19:10 system: starting ntpclient
Jan 7 05:19:22 system: starting ntpclient
Jan 7 05:19:33 system: starting ntpclient
Jan 7 05:19:45 system: starting ntpclient
Jan 7 05:19:56 system: starting ntpclient
Jan 7 05:20:07 system: starting ntpclient
Jan 7 05:20:18 system: starting ntpclient
Jan 7 05:20:30 system: starting ntpclient

Here is some more info on what the Event logs are showing in Solarwind. The interface speeds are changing to all sorts of random numbers.

davidbaker wrote:Nope, just a bunch of ntp client issues which was why we upgraded firmware was to see if that would correct the NTP issue. Thats a seperate issue at the moment.


Jan 7 05:18:36 system: starting ntpclient
Jan 7 05:18:48 system: starting ntpclient
Jan 7 05:18:59 system: starting ntpclient
Jan 7 05:19:10 system: starting ntpclient
Jan 7 05:19:22 system: starting ntpclient
Jan 7 05:19:33 system: starting ntpclient
Jan 7 05:19:45 system: starting ntpclient
Jan 7 05:19:56 system: starting ntpclient
Jan 7 05:20:07 system: starting ntpclient
Jan 7 05:20:18 system: starting ntpclient
Jan 7 05:20:30 system: starting ntpclient

This is indicating it can not reach the NTP server or you have the NTP server mis-configured?

If the switch is located on a non rout-able IP it will not be able to reach a public NTP server and you will need to setup an internal NTP server within your network that can be reached.

Does your switch reside at a non-valid IP and what address is the switch trying to reach for NTP?

I just noticed also the CPU seems to be spiking up to 99% as well.





Also here is a screen cap showing last boot time that is being reported to Solarwinds but in the screen shot above you can see the system has been up for 7+ days.

sirhc wrote:

davidbaker wrote:Nope, just a bunch of ntp client issues which was why we upgraded firmware was to see if that would correct the NTP issue. Thats a seperate issue at the moment.


Jan 7 05:18:36 system: starting ntpclient
Jan 7 05:18:48 system: starting ntpclient
Jan 7 05:18:59 system: starting ntpclient
Jan 7 05:19:10 system: starting ntpclient
Jan 7 05:19:22 system: starting ntpclient
Jan 7 05:19:33 system: starting ntpclient
Jan 7 05:19:45 system: starting ntpclient
Jan 7 05:19:56 system: starting ntpclient
Jan 7 05:20:07 system: starting ntpclient
Jan 7 05:20:18 system: starting ntpclient
Jan 7 05:20:30 system: starting ntpclient

This is indicating it can not reach the NTP server or you have the NTP server mis-configured?

If the switch is located on a non rout-able IP it will not be able to reach a public NTP server and you will need to setup an internal NTP server within your network that can be reached.

Does your switch reside at a non-valid IP and what address is the switch trying to reach for NTP?

We have our own Internal NTP Server that the switch can reach. We have 3 total Netonix switches and only 1 of them seem to be working with the NTP server. Our thoughts were maybe that because the firmware was higher on the one that appear to work that we just needed to update the firmware on all of them. Well anyways no that did not work but honestly I need to troubleshoot more on the network side before I conclued anything is wrong with the Netonix switches. I still have a few things I want to try before I need to get some help from the experts!

Do you have any updates you could provide me?

davidbaker wrote:Do you have any updates you could provide me?

We can not see your pictures 2 posts up.

UPLOAD the pictures to the forum with the link below the BLUE submit button.