NTP: Receive timeout, retrying NTP Server: <NTP server name>

The SG is attempting to reach its configured NTP server, but it did not receive a response.
The SG response timeout for an NTP packet is 1 second.  The SG will make 10 attempts to
reach its configured NTP server before giving up and waiting until the next interval to try again.
The default NTP interval is 60 min.

NTP: Wrong originate timestamp in response received from NTP Server: <NTP server name>
Sent <some value>, received <some other value>

RFC 1035 defines the NTP protocol.  When the SG's NTP client originates a request, it will
set its "Originate Time Stamp" field to NULL, and set its "Transmit Time Stamp" to an arbitrarily high
value (way into the future).
When a response is received (within the 1 second timeout), the response's "Originate Time Stamp" is
compared with the "Transmit Time Stamp" sent in the original request.
If they do not match, the event log message is triggered and a new NTP request is generated.

NTP: Receive timeout, exceeded maximum retries to NTP Server: <NTP server name>

The SG will attempt to reach its configured NTP server 10 times.  In the example above,
the SG did not receive a response to its NTP requests after 10 tries.  By default, the SG will
attempt to contact the NTP server every 60 minutes.  Another 10 attempts will occur in 60 min.

NTP: Periodic query of server <NTP server name>, time within acceptable variance, <x> seconds, <y>ms fast/slow
compared to NTP time.

This is an indication that the SG sent and received 3 valid NTP requests/responses and after averaging
the time within the 3 NTP responses, that average was within the acceptable variance of  200ms.