2 Replies Latest reply on Nov 25, 2014 9:24 AM by frank_enser

    ntp issue

    roadwarrior

      I have configured my meg appliance towards a ntp server.

      However time seems not in sync with ntp server; in fact i have a critical (red) signal on dashboard and if i run test in troubleshooting section i find this warning in ntp section

       

      Time Synchronization is not functioning correctly

           remote           refid      st t when poll reach   delay   offset  jitter

      ==============================================================================

      xxx.xxx.xxx.xxx  .INIT.          16 u    - 1024    0    0.000    0.000   0.000

      xxx.xxx.xxx.xxx  .INIT.          16 u    - 1024    0    0.000    0.000   0.000

      xxx.xxx.xxx.xxx .INIT.          16 u    - 1024    0    0.000    0.000   0.000

      Delay and Offset should not be 0

       

      I have found this kb:

      McAfee KnowledgeBase - Time Synchronization is not functioning correctly (NTP server test in System Test fails)

      McAfee KnowledgeBase - Failed to connect to the database when installing the ePO server or Agent Handler

       

      but poor help from both.

      On many tutorial i see:

      When upstream NTP is working properly, delay and offset values should be non-zero and the jitter value should be below 100.

       

      Has someone already experienced this problem?

       

      Thanks

        • 1. Re: ntp issue
          trishoar

          Hi,

           

          Are you sure that you can connect to the NTP servers?

           

          it should look like this

          ntpq> peers

               remote           refid      st t when poll reach   delay   offset  jitter

          ==============================================================================

          +domain1.org   xxx.xxx.xxx.xxx     2 u  363  512  377    0.438    0.248   0.153

          -domain2.org   xxx.xxx.xxx.xxx     2 u  443  512  377    0.396    1.459   0.079

          *domain3.org   xxx.xxx.xxx.xxx     2 u  267  512  377    0.440    0.116   0.189

          +domain4.org   xxx.xxx.xxx.xxx     2 u   72  512  377    0.444   -0.067   0.298

          LOCAL(0)        .LOCL.          10 l  25d   64    0    0.000    0.000   0.000

           

          Where mine has xxx.xxx.xxx.xxx you have .INIT. which says it is still trying to initialise a connection the the NTP server.

           

          Tris

          • 2. Re: ntp issue
            frank_enser

            Hi,

             

            .INIT. means that the NTP server cannot be reached. Try other NTP servers and check network connectivity (NTP uses UDP on port 123). Perhaps there is a firewall in between which drops 123/UDP packets?

             

            Regards,

            Frank