Richard Burts Wed, 11/14/2007 - 12:43
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Cole


I do not believe that there is any way to force sync to NTP. Some people believe that it can help if you set the time on the client to be close to the time of the server since the larger the difference the longer it may take to sync. In my experience sometimes I have rebooted a device and had it sync more quickly.


If the 6509 has been configured for a while and is consistently not sync then I would look for signs of a problem. Are you sure that the address configured on the 6509 is an active NTP server? Are you sure that there is good IP connectivity between the 6509 and the NTP server? Have you configured authentication or access-group for NTP that could be affecting the attempt to sync?


If none of these improve the situation then perhaps it would help to run debug ntp sync, debug ntp packet and post the output.


HTH


Rick

colegisselbeck Wed, 11/14/2007 - 13:07
User Badges:

Here's some output it appears to me that something is off (dec 1899) but that's just from comparing it to our other 6500. Thanks



ov 14 15:02:40: NTP: xmit packet to 192.168.12.240:

.Nov 14 15:02:40: leap 3, mode 3, version 3, stratum 0, ppoll 64

.Nov 14 15:02:40: rtdel 0000 (0.000), rtdsp 3E002 (3875.031), refid 7F7F0701 (127.127.7.1)

.Nov 14 15:02:40: ref CAE5B102.0D080538 (11:38:10.050 CST Wed Nov 14 2007)

.Nov 14 15:02:40: org 00000000.00000000 (18:00:00.000 CST Thu Dec 31 1899)

.Nov 14 15:02:40: rec 00000000.00000000 (18:00:00.000 CST Thu Dec 31 1899)

.Nov 14 15:02:40: xmt CAE5E0F0.55E2528C (15:02:40.335 CST Wed Nov 14 2007)

.Nov 14 15:03:44: NTP: xmit packet to 192.168.12.240:

.Nov 14 15:03:44: leap 3, mode 3, version 3, stratum 0, ppoll 64

.Nov 14 15:03:44: rtdel 0000 (0.000), rtdsp 3E002 (3875.031), refid 7F7F0701 (127.127.7.1)

.Nov 14 15:03:44: ref CAE5B102.0D080538 (11:38:10.050 CST Wed Nov 14 2007)

.Nov 14 15:03:44: org 00000000.00000000 (18:00:00.000 CST Thu Dec 31 1899)

.Nov 14 15:03:44: rec 00000000.00000000 (18:00:00.000 CST Thu Dec 31 1899)

.Nov 14 15:03:44: xmt CAE5E130.55E1DC2C (15:03:44.335 CST Wed Nov 14 2007)

.Nov 14 15:04:48: NTP: xmit packet to 192.168.12.240:

.Nov 14 15:04:48: leap 3, mode 3, version 3, stratum 0, ppoll 64

.Nov 14 15:04:48: rtdel 0000 (0.000), rtdsp 3E002 (3875.031), refid 7F7F0701 (127.127.7.1)

.Nov 14 15:04:48: ref CAE5B102.0D080538 (11:38:10.050 CST Wed Nov 14 2007)

.Nov 14 15:04:48: org 00000000.00000000 (18:00:00.000 CST Thu Dec 31 1899)

.Nov 14 15:04:48: rec 00000000.00000000 (18:00:00.000 CST Thu Dec 31 1899)

.Nov 14 15:04:48: xmt CAE5E170.55E1B522 (15:04:48.335 CST Wed Nov 14 2007

Richard Burts Wed, 11/14/2007 - 14:10
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Cole


Thanks for posting the debug output. What I see in the output is multiple times when your 6509 transmits but I do not see any receives. Could you do a traceroute to 192.168.12.240 and post the output?


HTH


Rick

Actions

This Discussion