Vubiq Networks Inc. V10G-L Manuale Utente
26
Vubiq HaulPass V10g User Manual
© 2018 Vubiq Networks, Inc. All Rights Reserved
5.5 Changing the Clock Time
The HaulPass V10g terminal boots with the standard UNIX Epoch time of midnight January 1, 1970 UTC and
counts up from there. This is the time that is used for the internal logs. This time is sufficient for many installations,
but there are situations that require the use of the current time. Using the current time can make reviewing the
internal logs easier to correlate with real world events. This section describes how to use a time server to change
the HaulPass V10g to the current time.
counts up from there. This is the time that is used for the internal logs. This time is sufficient for many installations,
but there are situations that require the use of the current time. Using the current time can make reviewing the
internal logs easier to correlate with real world events. This section describes how to use a time server to change
the HaulPass V10g to the current time.
Configuring the Network
The first step is to configure your network so that the HaulPass V10g can communicate with a time server. If you
cannot reach the Internet from the HaulPass V10g, you will not be able to reach a timer server. Once you have
configured your network so that the HaulPass V10g can reach the Internet, you are ready to test the connection with
a ping. Most time servers do not support ping, so you will need to ping another host on the Internet. The
vubiqnetworks.com server is at 23.229.216.200. You can ping the vubiqnetworks.com server from both the Web
GUI and the command line.
cannot reach the Internet from the HaulPass V10g, you will not be able to reach a timer server. Once you have
configured your network so that the HaulPass V10g can reach the Internet, you are ready to test the connection with
a ping. Most time servers do not support ping, so you will need to ping another host on the Internet. The
vubiqnetworks.com server is at 23.229.216.200. You can ping the vubiqnetworks.com server from both the Web
GUI and the command line.
# ping ip 23.229.216.200
PING server 23.229.216.200, 56 bytes of data.
64 bytes from 23.229.216.200: icmp_seq=0, time=20ms
64 bytes from 23.229.216.200: icmp_seq=1, time=10ms
64 bytes from 23.229.216.200: icmp_seq=2, time=10ms
64 bytes from 23.229.216.200: icmp_seq=3, time=10ms
64 bytes from 23.229.216.200: icmp_seq=4, time=10ms
Sent 5 packets, received 5 OK, 0 bad
#
PING server 23.229.216.200, 56 bytes of data.
64 bytes from 23.229.216.200: icmp_seq=0, time=20ms
64 bytes from 23.229.216.200: icmp_seq=1, time=10ms
64 bytes from 23.229.216.200: icmp_seq=2, time=10ms
64 bytes from 23.229.216.200: icmp_seq=3, time=10ms
64 bytes from 23.229.216.200: icmp_seq=4, time=10ms
Sent 5 packets, received 5 OK, 0 bad
#
Pointing to the NIST Internet Time Servers
We recommend using the
their list are 129.6.15.28, 129.6.15.29, and 129.6.15.30, so these are the three used in this example.