CUCM version 10.5 publisher and subscriber fails to synchronize

[momosebi]

I have a client who has a CUCM server running version 10.5. The publisher and subscribing have suddenly stopped synchronizing for some reason. According to the customer, this seemed to have happened soon after migrating the CUCM instance from the Cisco business edition servers to virtual machines, hosted on third party servers. It continued to work even after the migration, but then stopped some months after.

I need guidance in how to go about troubleshooting. I haven't exactly done this before, so I have no clue as to where to start or how to even go about it.

What systems/interfaces do I need to access? How to access it? What to look for when troubleshooting? Helpful troubleshooting commands? Possible causes of the problem?

Thanks very much in advance. Hope for a swift response too as this is quite urgent.

[collinks2]

This means that there is no database replication between the Publisher and Subscriber. You need to check the database replication status on the publisher using this command utils dbreplication runtimestate.youcan check this link for more information 

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200396-Steps-to-Troubleshoot-Database-Replicati.html#:~:text=To verify the database replication,2.

[momosebi]

Thank you for this. It was quite helpful and informative.

However, there's been a development. According to an update I just got from the customer, the problem seems to be actually pointing towards synchronization issues between the CUCM and the Prime license manager. There's an error displayed on the server that says "The system has not synchronized successfully with Cisco Prime License Manager for 143 days. If successful synchronization does not occur within the next 37 days, you will no longer be able to provision users and devices".

[momosebi]

I did some troubleshooting and noticed the following. When I logged into the Prime License Manager, a message was displayed that said "This product instance is already being managed by another cisco prime license manager. Product instances can only be managed by a single cisco prime license manager. To manage the product with this cisco prime license manager, delete it from this and the other cisco prime license manager, and then add it to this one"

So I deleted the publisher from the PLM, and then also went to the publisher's CLI and entered this command "license management reset registration" to reset its registration. I also entered this same command on the subscriber.

I then went back to the PLM and re-added the publisher under 'product instance', however this wasn't successful and gives an error as shown in the attached image - which basically says the publisher is already registered with another PLM. However the PLM that it says it's registered with already is still the same PLM I was currently on and trying to register the publisher to.

I also noticed that the subscriber also was registered to its own PLM, just as the publisher is also registered to its own PLM. So both the publisher and subscriber are registered to different PLMs. Could this be the problem? Or could this also be a licensing problem? Perhaps out-of-date licenses? And how do I verify that?

I really need the assistance urgently and would really appreciate it. Thank you.

[Roger Kallberg]

First thing, what happens if you answer Yes on the question to take over the license management? Second thing, what do you see if you go into the webUI of the PLM on the Publisher? Can you from there remove the node from being handled by that PLM? Also do you see that there are any licenses in either of the PLMs? Third thing, the version you are using is long past any support. With that in mind it’s recommended that you get it updated to a supported version. Those would be version 14 and 15, where 15 would be the recommended option to go to.

[momosebi]

If I answer Yes, it brings up another error as shown in the attached image, basically pointing to a registration failure of the node to the PLM. When logged into the GUI of the PLM on the publisher, under the product instance, it displays the publisher node as being managed by the PLM, but the status of node displays as 'registration failure'.

Yes, I did delete the publisher from the PLM and then re-added it, and that was when it gave that error I mentioned earlier. Bottomline is I am able to successfully delete and add the publisher node to the PLM, but it still says registration failure when I attempt to synchronize the publisher with the PLM.

Also, I'm actually not sure how to check for availaible licenses in the PLM. I navigated to the licensing section on the PLM, but it didn't exactly show me if there were available licenses there. Could you guide me on how to check for that and what to look for. Do you think that could be the problem?

And yes I did explain to the client that they had to upgrade to version 15, and they understood the necessity, but insist that they'd atleast like to first resolve this issue, pending when they finally decide to go along with the upgrade.

[Roger Kallberg]

It’s many years ago since I last touched a v10.5 system and PLM, so it’s far from fresh in mind. To start with I would recommend you to make sure that none of the nodes in the cluster is registered to any PLM, not the standalone nor the co-res on the server node. This applies to both Pub and any Sub nodes. Next I’d suggest that you do a complete cluster reboot, starting with the Publisher first, then 15-20 minutes after the Pub is back and fully running all applicable services I’d continue with the restart of the Subscriber(s). If you have multiple Sub’s I’d do the one where TFTP service is running first. Wait around 15-20 minutes between restart of each Subscriber. I would also recommend that you restart the standalone PLM server. Then when the systems are fully operational after the restart of all cluster nodes and PLM I’d suggest that you add the Publisher to the standalone PLM and see if that succeeds. If it doesn’t I’m afraid that you’re out of luck as you cannot get any help from TAC on this as your version went EOL years ago.