Cisco Bug: CSCvs38748 - After L2 upgrade UCM Subscriber node loose NTP configuration if NTP process does not start properly.
Nov 03, 2020
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: After L2 upgrade UCM Subscriber node lost NTP configuration if NTP process does not start. Conditions: UCM Version: 220.127.116.1100-103 Description: One of the subscriber node raising alarm "This secondary node does not have the primary node NTP server configured." we can check alarms /var/log/active/syslog using zgrep "primary node NTP" * | more But I dont see those alarm under inactive side /var/log/inactive/syslog, so looks like issue was not there before upgrade. The following alarm is just after upgrade: zgrep "primary node NTP" * | more messages:Nov 22 18:08:36 wdc-ucm-sub-05 user 2 platform: Secondary node does not have the primary node NTP server configured in /etc /ntp.conf. Create a remote account, enter 'cd /usr/local/bin/base_scripts/sd_ntp', then 'sd_ntp -defaultConf', 'sd_ntp -add -s <prim ary node IP address>' where <primary node IP address> is the IP address of the primary node, and then enter CLI command 'utils ntp r estart'.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases