Uderc programming article aggregator sites

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

Advertisement
Hi all,
Although all the edges and CM have the same ntp configuration , I still have this  major alarm on three Edge-WAAS even after synchronization .
Is it possible to learn more about this - what caused it, ect.
Any ideas on how to proceed? (software version 4.1.3.b)
Advertisement
The best answer: Excuse my english , i'm not native speaker .
Alarm doesn't disappear  even after 24 h from the synchronization .
These are the outputs of commands entered in the same time on the WAE and the CM :
Output on the WAE :
Edge-BrancheOffice#sh  alarm
Critical Alarms:
None
Major Alarms:
     Alarm ID             Module/Submodule     Instance
   1 cms_clock_alarm      cms                                     
Minor Alarms:
None
Edge-BrancheOffice#sh clock
Local time: Fri Feb  1 10:42:07 GMT 2013
Edge-BrancheOffice#sh ntp stat
ntp enabled
ntp authentication disabled
server list:
Server           Key
192.168.6.7      -
     remote           refid                st t when poll reach   delay   offset  jitter
==============================================================================
192.168.6.7     192.168.6.6      3 u  112  128  375  245.491  13739.6   5.756
Edge-BrancheOffice#
Output on the CM :
CM-manager#sh clock
Local time: Fri Feb  1 10:30:36 GMT 2013
CM-manager#sh ntp stat
ntp enabled
ntp authentication disabled
server list:
Server           Key
192.168.6.7      -
     remote           refid           st t   when   poll   reach     delay      offset        jitter
==============================================================================
192.168.6.7    192.168.6.6      3 u    -       128  377      0.608      713549.     20.935
CM-manager#
Thank you .