topic Re: NTP Problem in NME-WAE's in Application Networking

NTP Problem in NME-WAE's

b.petronio — Tue, 07 Jul 2009 20:37:09 GMT

Hi all,

After configuring ntp server, the time is syncronized with no problem at all.

The issue occurs when the router reloads/turns off, and when it goes up, the hour in the NM-WAE, will never sync automatically.

I always have to delete the ntp configuration line and re-apply it manually.

Any ideias ?

Plataform: NME-WAE-302 and NME-WAE-502.

Software Version: 4.1.1c.16

Best Regards,

Bruno PetrÃ³nio

Re: NTP Problem in NME-WAE's

dstolt — Tue, 07 Jul 2009 21:01:55 GMT

Bruno,

I have not seen this. When you do a "show NTP Status" does it show that it's communicating with the router? What happens if you create a secondary NTP server that is available via the WAN?

Dan

Re: NTP Problem in NME-WAE's

b.petronio — Tue, 07 Jul 2009 21:07:17 GMT

Well,

Im not having access right now, but i will get that info.

Im configuring 1 only WAN ntp server, in Central Site. I could try to configure the router as the server, just for testing.

Cmpts,

Bruno PetrÃ³nio

Re: NTP Problem in NME-WAE's

b.petronio — Wed, 08 Jul 2009 13:53:59 GMT

Here it is a brand new example :

wae1#show version

Cisco Wide Area Application Services Software (WAAS)

Cisco Wide Area Application Services Software Release 4.1.1c (build b16 Nov 5 2008)

Version: nme-wae-302-4.1.1c.16

Compiled 10:10:31 Nov 5 2008 by cnbuild

System was restarted on Fri May 5 01:00:53 2006.

The system has been up for 1 hour, 38 minutes, 30 seconds.

wae1#show ntp status

ntp enabled

ntp authentication disabled

server list:

Server Key

10.10.210.248 -

remote refid st t when poll reach delay offset jitter

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

ama-dc01.lc.pt lclx-dc01.lc.pt 2 u 13 128 377 32.331 1002714 4.829

wae1#ping 10.10.210.248

PING 10.10.210.248 (10.10.210.248) 56(84) bytes of data.

64 bytes from 10.10.210.248: icmp_seq=1 ttl=123 time=22.7 ms

64 bytes from 10.10.210.248: icmp_seq=2 ttl=123 time=33.7 ms

64 bytes from 10.10.210.248: icmp_seq=3 ttl=123 time=27.7 ms

64 bytes from 10.10.210.248: icmp_seq=4 ttl=123 time=25.9 ms

--- 10.10.210.248 ping statistics ---

5 packets transmitted, 4 received, 20% packet loss, time 3998ms

rtt min/avg/max/mdev = 22.798/27.572/33.787/3.999 ms, pipe 2

wae1#

wae1#show clock

Local time: Fri May 5 02:43:15 WEST 2006

wae1#

Any ideias?

Best Regards,

Bruno PetrÃ³nio

Re: NTP Problem in NME-WAE's

dstolt — Wed, 08 Jul 2009 15:51:04 GMT

Bruno,

Please validate, is it when you reload your local router (and NME) when the time synch difference occures? Also, it seems that it's with multiple NME-WAEs or just a couple? Do you see any syslog messages referencing NTP after boot?

Thanks,

Dan

Re: NTP Problem in NME-WAE's

b.petronio — Wed, 08 Jul 2009 16:13:35 GMT

Tks Daniel,

Yes, only when i reload the router.

I have 1 NME in each router only.

Syslog:

2006 May 5 00:01:51 NO-HOSTNAME Nodemgr: %WAAS-NODEMGR-5-330082: [CLI_VER_NTP] requests stop service ntpd.

2006 May 5 01:02:18 Vimioso-wae1 ver_ntp: %WAAS-NTP-4-340008: failed to pre-sync system time and calendar.

2006 May 5 00:02:18 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330080: [CLI_VER_NTP] requests start service ntpd

2006 May 5 00:04:09 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330040: Start service 'ntpd' using: '/usr/sbin/ntpd -g -p /etc/ntpd.pid' with pid: 4524

2006 May 5 01:04:09 Vimioso-wae1 ntpd[4524]: %WAAS-NTP-5-340000: ntpd 4.0.99j Wed Nov 5 11:35:54 PST 2008 (1)

2006 May 5 01:04:09 Vimioso-wae1 ntpd[4524]: %WAAS-NTP-5-340000: using kernel phase-lock loop 0040

2006 May 5 02:41:18 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330032: Stopping service: 'ntpd'.

2006 May 5 03:41:18 Vimioso-wae1 ntpd[4524]: %WAAS-NTP-5-340000: ntpd exiting on signal 15

2006 May 5 02:43:46 NO-HOSTNAME Nodemgr: %WAAS-NODEMGR-5-330082: [CLI_VER_NTP] requests stop service ntpd.

2006 May 5 03:44:12 Vimioso-wae1 ver_ntp: %WAAS-NTP-4-340008: failed to pre-sync system time and calendar.

2006 May 5 02:44:13 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330080: [CLI_VER_NTP] requests start service ntpd

2006 May 5 02:46:04 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330040: Start service 'ntpd' using: '/usr/sbin/ntpd -g -p /etc/ntpd.pid' with pid: 4604

2006 May 5 03:46:04 Vimioso-wae1 ntpd[4604]: %WAAS-NTP-5-340000: ntpd 4.0.99j Wed Nov 5 11:35:54 PST 2008 (1)

2006 May 5 03:46:04 Vimioso-wae1 ntpd[4604]: %WAAS-NTP-5-340000: using kernel phase-lock loop 0040

2006 May 5 03:02:32 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330084: [CLI_VER_NTP] requests restart service ntpd

2006 May 5 03:02:32 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330032: Stopping service: 'ntpd'.

2006 May 5 04:02:32 Vimioso-wae1 ntpd[4604]: %WAAS-NTP-5-340000: ntpd exiting on signal 15

2006 May 5 03:02:32 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330040: Start service 'ntpd' using: '/usr/sbin/ntpd -g -p /etc/ntpd.pid' with pid: 11047

2006 May 5 04:02:32 Vimioso-wae1 ntpd[11047]: %WAAS-NTP-5-340000: ntpd 4.0.99j Wed Nov 5 11:35:54 PST 2008 (1)

2006 May 5 04:02:32 Vimioso-wae1 ntpd[11047]: %WAAS-NTP-5-340000: using kernel phase-lock loop 0041

2006 May 5 03:27:47 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330082: [CLI_VER_NTP] requests stop service ntpd.

2006 May 5 03:27:47 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330032: Stopping service: 'ntpd'.

2006 May 5 04:27:47 Vimioso-wae1 ntpd[11047]: %WAAS-NTP-5-340000: ntpd exiting on signal 15

*******

After this line i inserted manualy...

2009 Jul 8 16:39:08 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330080: [CLI_VER_NTP] requests start service ntpd

2009 Jul 8 16:39:08 Vimioso-wae1 Nodemgr: %WAAS-NODEMGR-5-330040: Start service 'ntpd' using: '/usr/sbin/ntpd -g -p /etc/ntpd.pid' with pid: 20238

2009 Jul 8 17:39:08 Vimioso-wae1 ntpd[20238]: %WAAS-NTP-5-340000: ntpd 4.0.99j Wed Nov 5 11:35:54 PST 2008 (1)

2009 Jul 8 17:39:08 Vimioso-wae1 ntpd[20238]: %WAAS-NTP-5-340000: using kernel phase-lock loop 0041