10-23-2013 04:34 PM - edited 03-16-2019 08:02 PM
Hi All,
We have 1 pub and 3 sub. We added a new subscriber to our CUCM cluster but we didnt had the node licenses. Then we got a temp license from Cisco
We added those licenses to our CUCM pub but still we see the node license is not activated
Units authorized: 5
Units used : 4
Units remaining: 1
I am not sure if we have to restart just CM services to activate it or restart Pub and subs??
Any help is much appreciated
Thanks in advance
10-23-2013 05:07 PM
Correct, you will see it used once you start the CM service.
Chris
Sent from Cisco Technical Support iPhone App
10-23-2013 05:09 PM
Thanks Chris.
So, we will have to restart only Pub CM service??
10-23-2013 05:11 PM
No need to restart anything, simply activate the service.
Sent from Cisco Technical Support iPhone App
10-23-2013 06:24 PM
I did restart CM service on Pub but I still see units used 4.
Units authorized: 5
Units used : 4
Units remaining: 1
Not sure why it is not taking the node license
10-23-2013 07:14 PM
Is CM service activated on all 5 servers?
Sent from Cisco Technical Support iPhone App
10-23-2013 07:36 PM
CM service is activated on all 4 servers, but not on the newly added subscriber.
When we try to activate the CM service on new sub, we are getting this error
pdate Failed for the Service(s): Cisco CallManager Service cannot be Activated or Deactivated due to Database Update Failure.
10-23-2013 07:38 PM
Check your database replication, this has nothing to do with licensing.
Sent from Cisco Technical Support iPhone App
10-23-2013 10:39 PM
Hi,
can u share old lic file and new lic file provided by Cisco?
also , share the output of utils dbreplication runtimestate from Publisher.
regds,
aman
10-24-2013 12:55 PM
Hi All,
I opened a TAC case to work on this issue and came to know that it is a known issue, TAC gave me a python script to upload on all servers. I ran that script through root access and the issue got fixed.
Once we activated the services on CUCM sub, it consumed one node license.
Thanks for all your help!!!
10-24-2013 07:02 PM
Hi,
thanks for update.
Did u ever change the security password on Publisher before installing the new Subscriber?
regds,
aman
10-25-2013 09:06 AM
Hi Aman,
I forgot to mention in my last update, yes we changed the security password on all servers.So to sync all db passwords, we had to run that script.
Thanks,
Uday
10-24-2013 07:40 PM
This issue is for a caveat when you change the Security Password and passwords are not sincronized locally.
10-25-2013 09:13 PM
Hi,
Your problem was due to these bugs
DB service is down, after changing the security password.
CLI "set password user security" did not set the correct apps password
regds,
aman
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide