Symptom

According to the CISCO-NTP-MIB, the MIB contains two traps: ciscoNtpGeneralConnFailure (This trap is sent when the device loses connectivity to all NTP servers.) and ciscoNtpGeneralConnRestore (This trap is sent when the connection with at least one NTP server has been restored (e.g. after a ciscoNtpGeneralConnFailure).). These traps have not been seen in either the customer environment or in the lab repro on multiple versions of code.

Conditions

"snmp-server enable traps" is configured, there is at least one SNMP server configured, and NTP is configured, and NTP is synchronized to an NTP server. If NTP becomes unsynchronized, the trap "ciscoNtpGeneralConnFailure " should be sent to the configured SNMP server. When connectivity to the NTP server is restored, the trap "ciscoNtpGeneralConnFailure " should be sent to the configured SNMP server.

Workaround

Create an EEM script to generate an SNMP trap based on the syslog entry ?Clock synchronization lost" or ?Clock is synchronized".

Further Problem Description