Setting time and date

[Kingsley]

Can the time and date be set via CLI without an NTP server?

I find it surprising the time and date can't be set in the web gui without an NTP server.

We have setup a customer network consisting of about 20 switches, this is a private monitoring network with cameras and weather stations that doesn't have internet access.

I want to get the time and date set to use the power off at night settings to save power on solar sites.

[sirhc]

The switch does not have a clock or an internal battery to keep time, I am unaware of a Layer 2 switch that does have one. I think you would be hard pressed to find many Layer 3 switches with a clock?

Now if you are talking a Cisco Catalyst switch well yea it does.

If the switch is inside a NAT network it can access public clocks on the internet or if they have an internal server you can run a local time server.

There are time servers you can run on your workstations as well.

I am not aware of any device that does not have an internal clock and lithium ion battery that allows you to manually set the time, maybe you could provide an example of such a device?

[Eric Stern]

You could do it with the CLI by using the "cmdline" command to drop to the command line and then use the "date" command. But you will lose the time every time you reboot.

It would be a far better idea to set up a private NTP server on the monitoring network, which could then be used by all the devices and you'd never have to worry about it again.

[jakematic]

I use these (also available on Amazon) https://www.css-timemachines.com/produc ... r-tm1000a/

Had one standalone for years, now use a pair to feed a Linux machine that acts as the NTP server
Haven't found anything that comes even close to that price.

Code: Select all

root@ubu:/etc/dhcp# chronyc sources
210 Number of sources = 6
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^* time.jakematic.lan 1 10 377 785 +373us[ +344us] +/- 342us
^+ time2.jakematic.lan 1 10 377 83 +149us[ +149us] +/- 279us


[lligetfa]

Haven't found anything that comes even close to that price.

We paid a lot more for a GPS IP clock years ago for our process control network and it was a steaming pile of dung. The thing could not handle many clients so it had to serve one NTP server that in turn served the clients.

I often wished the timeclock in the GPS built into some Ubiquiti kit could be exposed to use as an NTP time source.

[jakematic]

We paid a lot more for a GPS IP clock years age for our process control network and it was a steaming pile of dung.

Spent years searching, even for used gear on fleaBay, and nothing came close.
Most of the dual setups I've run into in data centers or shop floors are exactly as you describe.

I often wished the timeclock in the GPS built into some Ubiquiti kit could be exposed to use as an NTP time source.

Yep, would be nice. All they would need to do is add the ntp server code.

[lligetfa]

I wouldn't even care if it degraded the performance of the radio. I would gladly dedicate some old RM5Ti to such a role. Would probably stick an omni on it and use it to just listen most of the time. Maybe turn it up for a minute with a UBNT SSID to recover a defaulted client radio.

[George Bradlink]

I have set up a NTP server on a Windows Server 2008 box on the local network at 192.168.254.69. I have tested the NTP service from another computer with the command "w32tm /stripchart /computer:192.168.254.69" and received back:
Tracking 192.168.254.69 [192.168.254.69:123].
The current time is 9/12/2017 4:14:32 PM.
16:14:32, d:+00.0253241s o:-11.8623831s [@ | ]
16:14:34, d:+00.0117721s o:-11.8572090s [@ | ]

The WISP switch's IP address is set to 192.168.254.40 and is able to ping the NTP server at 192.168.254.69 using the WISP switch ping utility.

The WISP switch stills says "TIME NOT SET" in the top of the screen. I have tried to set its time using the "Device", "Configuration", checking the "NTP Enable" checkbox and defining the local NTP server's IP address as 192.168.254.69.

The WISP switch log shows:


Dec 31 16:04:54 UI: NTP_Host: changed from '192.168.254.68' to '192.168.254.69'
Dec 31 16:04:58 system: starting ntpclient
Dec 31 16:05:02 system: starting ntpclient
Dec 31 16:05:14 system: starting ntpclient
Dec 31 16:05:25 system: starting ntpclient
Dec 31 16:05:36 system: starting ntpclient
Dec 31 16:05:47 system: starting ntpclient
Dec 31 16:05:58 system: starting ntpclient
Dec 31 16:06:10 system: starting ntpclient
Dec 31 16:06:21 system: starting ntpclient
Dec 31 16:06:32 system: starting ntpclient
Dec 31 16:06:43 system: starting ntpclient
Dec 31 16:06:55 system: starting ntpclient
Dec 31 16:07:06 system: starting ntpclient
Dec 31 16:07:17 system: starting ntpclient
Dec 31 16:07:28 system: starting ntpclient

It has page after page of the "starting ntpclient" message to at least 17:30 and continues if we refresh the page.

Thoughts would be appreciated.

George

[sirhc]

Please be using v1.4.8rc10

Please post up screen grabs of the following TABs:
Status
Ports
VLAN
Device/Configuration
Device/Status

[George Bradlink]

Hello:

Please be using v1.4.8rc10 Please post up screen grabs of the following TABs: Status Ports VLAN Device/Configuration Device/Status

We attached the screen shots and updated to v1.4.8rc10.

Thank you for your comments,

George