Netonix Forums

WS-24-400-A ver 1.4.3rc5

The log fills up quickly with the following....main page shows "TIME NOT SET" ....all other equipment on the subnet has no problem with ntp...


Jan 3 15:57:24 system: starting ntpclient
Jan 3 15:57:35 system: starting ntpclient
Jan 3 15:57:47 system: starting ntpclient
Jan 3 15:57:58 system: starting ntpclient
Jan 3 15:58:09 system: starting ntpclient
Jan 3 15:58:20 system: starting ntpclient
Jan 3 15:58:32 system: starting ntpclient
Jan 3 15:58:43 system: starting ntpclient
Jan 3 15:58:54 system: starting ntpclient
Jan 3 15:59:05 system: starting ntpclient
Jan 3 15:59:16 system: starting ntpclient
Jan 3 15:59:27 system: starting ntpclient
Jan 3 15:59:38 system: starting ntpclient
Jan 3 15:59:50 system: starting ntpclient
Jan 3 16:00:01 system: starting ntpclient
Jan 3 16:00:12 system: starting ntpclient
Jan 3 16:00:23 system: starting ntpclient
Jan 3 16:00:34 system: starting ntpclient
Jan 3 16:00:45 system: starting ntpclient
Jan 3 16:00:56 system: starting ntpclient
Jan 3 16:01:08 system: starting ntpclient
Jan 3 16:01:19 system: starting ntpclient
Jan 3 16:01:30 system: starting ntpclient
Jan 3 16:01:41 system: starting ntpclient
Jan 3 16:01:53 system: starting ntpclient
Jan 3 16:02:04 system: starting ntpclient
Jan 3 16:02:15 system: starting ntpclient
Jan 3 16:02:26 system: starting ntpclient
Jan 3 16:02:37 system: starting ntpclient
Jan 3 16:02:48 system: starting ntpclient
Jan 3 16:02:59 system: starting ntpclient
Jan 3 16:03:11 system: starting ntpclient
Jan 3 16:03:22 system: starting ntpclient
Jan 3 16:03:33 system: starting ntpclient
Jan 3 16:03:44 system: starting ntpclient
Jan 3 16:03:56 system: starting ntpclient
Jan 3 16:04:07 system: starting ntpclient

Well obviously the switch can not reach the NTP server you have specified.

Maybe do a search for similar issues, I found this pretty fast
viewtopic.php?f=17&t=266&p=1052&hilit=ntp+server#p1052
viewtopic.php?f=17&t=1890&p=14012&hilit=NTP#p14012


So anyway a common mistake people do is their switch has an invalid non rout-able IP then they wonder why it can not reach an NTP server out on the web.

Verify your switch can actually reach the specified NTP server.

Personally I run my own NTP server inside my WISP network so all my invalid IPs can reach it.

Double check your NTP settings such as netmask, default gateway, and so on

Remember if using VLANs this can block/hinder access

Use the ping tool and or drop to linux shell and verify you can ping the NTP server.

If using an access list make sure the switch access list allows communications from the NTP server

Since there are thousands of people out there using our switches and using NTP the odds are there is something with your config more than a bug as this bug would have been spotted long ago.

Switch can ping our own NTP server inside our WISP network...

PING 10.10.0.1 (10.10.204.1): 56 data bytes
64 bytes from 10.10.204.1: seq=0 ttl=64 time=0.710 ms
64 bytes from 10.10.204.1: seq=1 ttl=64 time=0.675 ms
64 bytes from 10.10.204.1: seq=2 ttl=64 time=0.695 ms
64 bytes from 10.10.204.1: seq=3 ttl=64 time=0.677 ms
64 bytes from 10.10.204.1: seq=4 ttl=64 time=0.686 ms
--- 10.10.204.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.675/0.688/0.710 ms

As I said, other equipment on the same subnet/vlan...ubnt...cisco...unix... all have no issues with NTP...just this switch.

Everything is on the same subnet and vlan

So, does the switch eventually use your NTP or does that go on forever? Did you set the NTP by IP or hostname?

Maybe there is a standards compliance issue?

Problem fixed by hard "power cycle" reboot. I hadn't done that after the recent upgrade to 1.4.3rc5. Fortunately this site is not in heavy production.