incorrect time on oc200

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

incorrect time on oc200

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
incorrect time on oc200
incorrect time on oc200
2022-02-09 06:39:23
Model: OC200  
Hardware Version: V1
Firmware Version: 1.14.3 Build 20220112 Rel.64116

Does anybody experience incorrect time on hardware controller?

 

I have found that my poe port schedule is not working as expected (the access point was on when it should be off and off when it should be on (on 1.14.2 firmware). This started after I have disconnected by mistake the wrong ups.

I have checked and found a new firmware available 1.14.3 and I have downloaded and installed.

Still same issue, the time is Jan 12, 2022 01:58 instead of Jan 08, 2022 22:35 (Pacific time).

 

Please help

  0      
  0      
#1
Options
3 Reply
Re:incorrect time on oc200
2022-02-10 04:37:22

@ady23 

Found the root cause.

I have reviewed the pfsense rules and turn off the internet access for the subnet that controller is part of and pointed the controller to get the NTP from pfsense directly. As soon I allow access to internet the system time was set correctly almost immediately. Disappointed in such behavior that actually is constraining users to allow internet to get the features that should work fine without it.

Does anybody know why the controller needs  access to internet to work the system time correctly and could not get the time from local NTP server?

  0  
  0  
#2
Options
Re:incorrect time on oc200
2022-02-10 13:09:17

@ady23 

 

If you have a local NTP Server, you can test whether the OC200's gateway can communicate with the local NTP Server.

Just striving to develop myself while helping others.
  0  
  0  
#3
Options
Re:incorrect time on oc200
2022-02-11 08:07:28

@Virgo 

Thanks for response.

I use pfsense NTP server, and I created a rule for OC200 and I can see some traffic for that rule, so I would assume the controller is accessing pfsense on port 123 for NTP.

Don't know how else to verify.

  0  
  0  
#4
Options

Information

Helpful: 0

Views: 618

Replies: 3

Related Articles