CallManager on 6.1 Sub Active but Not Running

Unanswered Question
Mar 15th, 2008
User Badges:

Hi All,

I have got a strange problem that I have never seen before on other versions of CallManager.

We have a new installation of CUCM 6.1. It was initially CUCM 6.0 and than, before going live, it was upgraded to 6.1. The installation consists of one Pub and one Sub. The CallManager service is activated on both servers but is running only on the Pub - on the Sub it is shown as Active but Not Running. If I start CallManager service on the Sub manually (from the Serviceability web page) it keeps running for about 30 seconds (it is show as running) and after this time it goes back to Not Running. Any idea what it could be before I open TAC case?

Thanks a lot.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
mhurley131 Sat, 03/15/2008 - 06:32
User Badges:

Under licensing, do you licenses for 1 or 2 nodes? How many are in use?

Alexander.Khlem... Sat, 03/15/2008 - 06:59
User Badges:

There are 2 units authorized and 2 units used - this looks all right. For some reason the SW Version shows 6.0 (not 6.1) but I was told it should not matter because you do not need to have a separate license for 6.0-6.1 upgrade.

mhurley131 Sat, 03/15/2008 - 07:45
User Badges:

It saying 6.0 should be ok.... I have a current setup just like that (came with 6.0, then upgraded 6.1).

Just to make sure, you ran the 6.1 upgrade on both the pub and sub, right?

mhurley131 Sat, 03/15/2008 - 10:06
User Badges:

Just had to ask :)

My next step would be to open a TAC case. They can collect trace files on the service and give you an answer.

Alexander.Khlem... Mon, 03/17/2008 - 04:11
User Badges:

Hi All,

I have managed to fix it. All I did was sending the "utils dbreplication repair " command from the Publisher CLI and than restarting the CallManager service on the Sub from Serviceability web page. The service has been running without errors since than and my devices have successfully re-registered to the Sub.

Thanks a lot to everybody involved.


This Discussion