Cisco Prime Startup/Running config problem

[JASI]

Hi everyone

I have a problem with a Device on our Cisco Prime (see Picture)

Since we have upgraded to Cisco Prime 3.4, Prime seems to recocnise the NTP Clock period change as a configuration change and logs it in Cisco Prime.

Now that shouldn't be happening, and it didn't log those events before either. Any idea how to resolve this issue?

Kind Regards

Jan

[Mark Elsen]

 - That is shouldn't be happening is debatable and or related to the behavior of Prime 3.4 (probably) ; you could try removing it from the config with no ntp clock-period.  There's an interesting thread about this , see full link below from which I cut and paste this :

the ntp clock-period command was always a concern for developers, since the config file should ideally consist only of user-entered commands.  However, back when NTP was first implemented in IOS,  the NVRAM was the only possible place to store clock-period information across reboots.

Ref : https://community.cisco.com/t5/other-network-architecture/ntp-clock-period-not-being-configured/td-p/1497904

M.

[iportuga]

This specific event should't be classified as a configuration change.

Take a look this thread: https://community.cisco.com/t5/switching/ntp-clock-period-value-constantly-changing/td-p/2152976