Wireless Access

last person joined: 23 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Server 2012R2 NTP to controller fails

This thread has been viewed 1 times
  • 1.  Server 2012R2 NTP to controller fails

    EMPLOYEE
    Posted Feb 08, 2016 01:59 PM

    Does anyone have a controller running 6.4.3.5 getting time via NTP from Windows Server 2012R2? - Ours will not get the time. Here are a couple commands which show to me, it is configured right. The Server does supply time to a Hewlett Packard 2920al switch, but the controller will not sychronize.

     

    (ControllerA) #show ntp peer 10.1.21.100

    remote ::, local ::
    hmode client, pmode client, stratum 16, precision -19
    leap 11, refid [73.78.73.84], rootdistance 0.00000, rootdispersion 5.19585
    ppoll 10, hpoll 10, keyid 0, version 4, association 47521
    reach 000, unreach 236, flash 0x1620, boffset 0.00000, ttl/mode 0
    timer 0s, flags config, bclient
    reference time:      00000000.00000000  Thu, Feb  7 2036  1:28:16.000
    originate timestamp: 00000000.00000000  Thu, Feb  7 2036  1:28:16.000
    receive timestamp:   da636016.b5f10a60  Mon, Feb  8 2016 13:42:30.710
    transmit timestamp:  da636016.b5f10a60  Mon, Feb  8 2016 13:42:30.710
    filter delay:  0.00000  0.00000  0.00000  0.00000
                   0.00000  0.00000  0.00000  0.00000
    filter offset: 0.000000 0.000000 0.000000 0.000000
                   0.000000 0.000000 0.000000 0.000000
    filter order:  0        1        2        3
                   4        5        6        7
    offset 0.000000, delay 0.00000, error bound 3.99217, filter error 0.00000
    remote host:          10.1.21.100
    local interface:      10.1.11.100
    time last received:   554s
    time until next send: 520s
    reachability change:  237788s
    packets sent:         236
    packets received:     236
    bad authentication:   0
    bogus origin:         0
    duplicate:            0
    bad dispersion:       236
    bad reference time:   0
    candidate order:      0
    flags:   config, bclient


    (ControllerA) #show ntp server

    NTP Server Table Entries

    ------------------------

     

    Flags:     * Selected for synchronization

               + Included in the final selection set

               # Selected for synchronization but distance exceeds maximum

               - Discarded by the clustering algorithm

               = mode is client

     

      remote                                  local                                    st   poll   reach    delay     offset      disp

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

    =10.1.21.100                              10.1.11.100                              16 1024       0    0.00000     0.000000    3.99217



  • 2.  RE: Server 2012R2 NTP to controller fails

    EMPLOYEE
    Posted Feb 08, 2016 07:26 PM

    What is the difference in time between the controller and the NTP server?  Do you have the Timezone as well as the clock summer-time parameter set?

     



  • 3.  RE: Server 2012R2 NTP to controller fails

    EMPLOYEE
    Posted Feb 08, 2016 07:34 PM

    The time difference is 47 seconds. Both are set to Eastern Standard time, both have summer-time set.

     



  • 4.  RE: Server 2012R2 NTP to controller fails

    EMPLOYEE
    Posted Feb 09, 2016 03:09 AM

    You should let it sit to see if it gets closer.



  • 5.  RE: Server 2012R2 NTP to controller fails

    Posted Mar 18, 2016 09:34 PM

    Hi,

     

    Did you solve the problem? What's the solution? I have the same issue.

     

    Regards,

    Patrick



  • 6.  RE: Server 2012R2 NTP to controller fails

    Posted Mar 29, 2016 01:55 AM

    Don't worry. I found the solution.

     

    If the Windows Server has no Internet, you can make the Windows Server more trustworthy by reduce the Dispersion to 0 (in Registry).