Guest

Preview Tool

Cisco Bug: CSCuj69536 - cert regenerate script is stuck during network change

Last Modified

Jul 24, 2017

Products (3)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Intercompany Media Engine
  • Cisco Unified Communications Manager Version 10.0

Known Affected Releases

10.0(0.98000.378) 10.0(1)

Description (partial)

Symptom:
Changing both hostname and ipaddress from PCD on a UCM.  The last line of the notify.sh.log shows regenerate_all_certs.sh and no more.  

10/08/2013 11:48:00 notify.sh|calling: /usr/local/platform/bin/drf_notify_hostname_change.py --hostname b7k-vmc038 --old_hostname b7k-vmc037|<LVL::Info>
10/08/2013 11:48:08 notify.sh|calling: /usr/local/bin/base_scripts/regenerate_all_certs.sh --hostname b7k-vmc038 --old_hostname b7k-vmc037|<LVL::Info>
"/common/log/taos-log-a/syslog/notify.sh.log" 34L, 3748C                                                                      34,1          Bot

Conditions:
when you change the hostname from CLI set network hostname or gui

Related Community Discussions

<key>CSCuj69536</key> - cert regenerate script is stuck during network change
I was able to get around this bug by regenerating any expired certificates I found on the server.  Here are the commands:   set cert regen CAPF set cert regen CallManager set cert regen ipsec set cert regen tomcat set cert regen TVS
Latest activity: Jan 29, 2018
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.