Prime License Manager blank login page/unable to login
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)
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.
B) Upgrade to 9.1.2 or 10.0 and run the CLI: license management reset identity. This will fix the corrupted certificate.
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.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...