WAE clock needs to be synchronized

[Dan Loring]

After reload getting ther following alarm.  How do you synchronize the clock with the CM?

WARN HAS_ALARM 1 Major Alarms are raised in the device.

Please find the  list below.

1. WAE clock needs to be synchronized with the primary CM to  make time-sensitive features like statistics, status monitoring and event  scheduling work correctly.

[Bhavin Yadav]

Hi Dan,

This error message means WAE is not able to sync up with NTP. Please make sure NTP is configured in WAE and is reachable from WAE. Please do not use CM as NTP server on WAE.

Regards.

[Dan Loring]

Yes, the ntp server is configured in the config and I can ping the ntp serverr from the device.  The ntp server is a seperate box from the CM.

[Bhavin Yadav]

Hi Dan,

Just make sure NTP is syncing up and port 123 is open between WAE and NTP server. Following CLI commands on WAE will tell you if NTP is working / syncing up on WAE.

WAE7341-1#sh ntp stat
ntp enabled
ntp authentication disabled
server list:
Server           Key
12.1.3.1      -

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
12.1.3.1     .INIT.          16 u    - 1024    0    0.000    0.000   0.000
WAE7341-1#

[Bhavin Yadav]

Hi Dan,

Further, I ran tcpdump on my lab WAE and saw some packet dumps. I would suggest you to run this on your WAE too to make sure there is open communication channel between WAE and ntp.

WAE7341-1#tcpdump -i any port 123
tcpdump: WARNING: Promiscuous mode not supported on the "any" device
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes

12:50:34.775318 IP localhost.10006 > localhost.ntp:  [len=12]NTPv2 res1, strat 1, poll 0, prec 1
12:50:34.775419 IP localhost.ntp > localhost.10006:  [len=16]NTPv2 res1, strat 129, poll 0, prec 1
12:50:34.776782 IP localhost.10006 > localhost.ntp:  [len=12]NTPv2 res1, strat 2, poll 0, prec 2
12:50:34.776890 IP localhost.ntp > localhost.10006:  [len=432]NTPv2 res1, strat 162, poll 0, prec 2
12:50:34.776923 IP localhost.ntp > localhost.10006:  [len=204]NTPv2 res1, strat 130, poll 0, prec 2
13:02:19.063655 IP WAE7341-1..xx.com.ntp > 12.1.3.1.ntp: NTPv4 client, strat 0, poll 10, prec -20
13:19:22.062888 IP WAE7341-1..xx.com.ntp > 12.1.3.1.ntp: NTPv4 client, strat 0, poll 10, prec -20
13:36:28.063287 IP WAE7341-1..xx.com.ntp > 12.1.3.1.ntp: NTPv4 client, strat 0, poll 10, prec -20
13:53:31.063596 IP WAE7341-1..xx.com.ntp > 12.1.3.1.ntp: NTPv4 client, strat 0, poll 10, prec -20

[Dan Loring]

Here are the outputs from those two commands.   I ran the following command at 8:47 am EST, but it is off by 4 hours.  I went into the cm, edit the deice, configure, time zone and it is set to EST.  I tenet to the device sh clock and it is set to 4:47 EST.  So it is definitely not communicating with the NTP server.

WAE-AA#tcpdump -i any port 123

tcpdump: Setting virtual memory/file size limit to 209715200

tcpdump: WARNING: Promiscuous mode not supported on the "any" device

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes

04:47:10.267139 IP User.company.local.ntp > company-wave4.company.local.ntp:  [len=68]NTPv3 client, strat 5, poll 12, prec -6

04:47:10.267148 IP user.company.local.ntp > company-wave4.company.local.ntp:  [len=68]NTPv3 client, strat 5, poll 12, prec -6

04:47:10.268716 IP company-wave4.company.local.ntp > user.company.local.ntp:  [len=68]NTPv3 server, strat 4, poll 12, prec -6

04:47:10.268727 IP company-wave4.company.local.ntp > user.kamco.local.ntp:  [len=68]NTPv3 server, strat 4, poll 12, prec -6

WAE-AA#sh ntp status

ntp enabled

ntp authentication disabled

server list:

Server           Key

192.168.100.95     -

     remote           refid      st t when poll reach   delay   offset  jitter

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

192.168.100.95    .Ç

■.          16 u  301 1024    0    0.000    0.000   0.000

[Bhavin Yadav · Accepted solution]

It looks like the communication in one way. Means, something is not good between ntp and waas.

How about removing ntp and try to synchronize manually.

disable ntp:

wae# conf t

wae(conf)# no ntp server

wae(conf)#exit

wae# ntpdate

you can also set the clock manually here by using cli command "clock set "

Let's know see if that works.

Regards.

[Dan Loring]

Bhavin,

Thanks for all your help.  It looks like it is an NTP server issue.  The Consulting company that set this up for us for what ever reason set the NTP server to a cisco sdm express application that is sitting on our mpls router????   So I got an email going to them to see why we are setup this way.

WAE-AA#ntpdate 192.168.10.95

14 Mar 12:01:10 ntpdate[20429]: the NTP socket is in use,

Failed to set software clock using NTP server 192.168.10.95