Napatech and system clock will not sync after force
search cancel

Napatech and system clock will not sync after force

book

Article ID: 116756

calendar_today

Updated On:

Products

CA Application Delivery Analysis MTP (NetQoS / ADA)

Issue/Introduction

Errors on the VMTP state that the Napatech and system clocks are not within 5 minutes of eachother.

After running:

/opt/NetQoS/scripts/syncNapatechClock --force

We see no change in time discrepancy

Environment

CentOS 6.X

Cause

During the 11.0 VMTP upgrade, the Napatech drivers were changed and some of our NetQoS scripts were not updated to reflect these changes.

Resolution

The nqcapd processes would not start due to their internal clocks not being within 5 minutes of the system clock. This is a defect in 11.0.2 that is remedied by editing the syncNapatechClock script

1) 'nano /opt/NetQoS/scripts/syncNapatechClock'

2) Locate the following line:

if [ "`/sbin/lsmod | /bin/grep ntki`" != "" ] ; then

change it to the following:

if [ "`/sbin/lsmod | /bin/grep nt3gd`" != "" ] ; then

3) Save and Exit

4) Execute the Napatech sync and monitor for drift:

sudo /opt/NetQoS/scripts/syncNapatechClock --force