Can't synchronize CUCM 11.5 SU3 and PLM 11.5

[daru ban]

Hi, all.

I have upgraded CUCM from 11.5.1(SU1) to 11.5.1(SU3). 

After upgraded, I can't synchronize CUCM 11.5 SU3 and standalone PLM 11.5.

PLM says 'Application Error' for reason that is not synchronized CUCM.

I could synchronize CUCM 11.5 SU1 and PLM. I don't configure mixed mode on CUCM.

I tried remove CUCM from PLM and reconfigure, but I couldn't synchronize them.

I don't have any idea to synchronize them.

Does someone have any good ideas?

Thank you for reading and your kindness.

[Aman Soi]

Hi,

these bugs could be the issue :

Prime License Manager blank login page/unable to login

CSCur95552

Description

Symptom:
Blank login screen or login failures when attempting to use Prime License Manager for both co-resident and Standalone deployments.

Conditions:
Attempting to login to Prime License Manager GUI

Workaround:
Co-Resident:
Regenerate the IPSec certificate on the node that Prime License Manager resides. Restart the DRF Master and DRF Local services (DRF Master can only be restarted if it is a Publisher that PLM co-resides)
Once regenerated and the services restarted you should be able to access the page to login.

Standalone:
Regenerate the IPSec certificate on the standalone PLM by running "set cert regen ipsec". Once completed reboot PLM node as the services cannot be restarted manually.
Once regenerated and the node rebooted you should be able to access the page to login.

License install should fail if the Cert is bad (Application Error)

CSCud25936

Description

Symptom:
Product Instance Synchronization Status = Application Error

ELM/PLM log will have:

ERROR ELMCertManager - CSR & Certificate public keys do not match
ERROR ELMSecurity - Unable to import pkcs7 bag: com.cisco.elm.common.security.LicensingSecurityException: CSR & Certificate public keys do not match

Conditions:
The license file has a bad certificate.
A bad certificate can be caused by many reasons:
1) The license was not issued for that ELM. That is, the license file was not generated from the license request of that specific ELM. This can happen if one tries to install a license file generated for a different ELM.

2) The certificate in the license file is corrupted or tampered ( a rare case).

3) The clock of the ELM is way behind, so the clock falls below the cert validity period.

Workaround:
A possible workarounds:

A) If you already have the license-request generated from this ELM, then get a new license file using that.

OR

B) Upgrade to 9.1.2 or 10.0 and run the CLI: license management reset identity.
This will fix the corrupted certificate.

OR

C) Otherwise try these steps:

1) run the CLI: license management reset registration
2) generate a new license request
3) Use that license request to get a new license from Cisco Backoffice.
4) Install it on the PLM.

If the step 2 fails, then there is no easy way to recover other than getting a dev engineer involved.
In that case, a dev engineer will have to clean the bad certificate with root access to the system.

More Info:
This issue was fixed in 9.1.2 and 10.0. With the fix, the license install will fail if the certificate is bad, thereby preventing the system from getting corrupted.

[daru ban]

Hi, Aman!

Thank you for replying.

I read the detail of CSCur95552.

I think CUCM 11.5 SU3 does not met the Bug.

Do you know whether CUCM 11.5 SU3 is affected?

Thank you.

[Aman Soi]

Hi Ban,

I am not aware of any other bug related to your issue in 11.x version.

regds,

aman

[Slavik Bialik]

I had the same issue. Upgrade your PLM to the newest version, 11.5.1 (SU2) and it'll work for sure. Worked for me.

[daru ban]

Hi, Slavik

I upgraded my PLM, but it did not work. It says "Application Error"...

My CUCM cluster is in lab, so I reconfigured my CUCM cluster and old cluster was deleted.

Then, they synchronize!

Thank you for your kindness.

[fedor.solovev]

Upgrade worked.
The latest 11.5 CUCM 11.5.1.15900-18 with the latest PLM 11.5.1.15900-3 - no application error.

[Ali Amir]

@Slavik Bialik +5 for your suggested solution.

I have CUCM 11.5 SU4 and Upgrade of PLM to the 11.5.1 (SU2) could solved my issue.