Error: 'CHR0371: The endpoint clocks could not be synchronized.' (NETIQKB12841)

Error: 'CHR0371: The endpoint clocks could not be synchronized.'

• If you are using a newer hardware platform to run the Performance Endpoint you will need to restart the machine and go into the BIOS and DISABLE the SpeedStep features. This feature is used to dynamically adjust the CPU clock speeds to save power and has been known to cause the time within the OS to shift time.
• Make sure that any firewall between the endpoints allows UDP traffic to pass in both directions on port 10115. For more information about firewall configuration, consult the User Guide for Vivinet Assessor.   Change the assessment configuration to include only endpoints running on the Windows, Linux, and Solaris operating systems.
• Use the /usepmtimer switch outline in the following Microsoft KB article to switch the clock method. http://support.microsoft.com/kb/895980

• Intel SpeedStep is enabled in the system BIOS.
• A firewall or some other device between the endpoints is blocking UDP data traffic on port 10115.
• The endpoint operating system does not support the clock synchronization that is necessary for calculating one-way delay. Currently, this feature is only available on Windows, Linux, and Solaris operating systems.
• The Time Stamp Counter is drifting. This problem occurs when the computer has the AMD Cool'n'Quiet technology (AMD dual cores) enabled in the BIOS or some Intel multi core processors. Multi core or multiprocessor systems may encounter Time Stamp Counter (TSC) drift when the time between different cores is not synchronized. The operating systems which use TSC as a timekeeping resource may experience the issue. Newer operating systems typically do not use the TSC by default if other timers are available in the system which can be used as a timekeeping source. Other available timers include the PM_Timer and the High Precision Event Timer (HPET).

Formerly known as NETIQKB12841

The endpoint clocks could not be synchronized to measure network delay. Because the amount of delay could not be measured, a call quality score could not be calculated.

If you need further assistance with the subject matter discussed in this Knowledge Base Article, please contact NetIQ Technical Support .