Wednesday, June 24, 2015

Cisco PLM Prime License Manager login hangs

I've run into an issue twice now on CUCM 10.5.2 systems.  When attempting to log into Cisco Prime License Manager running co-resident with a CUCM server, after entering the correct credentials the login page never changes.  The small spinning status wheel below the credentials stops but the browser may look like it is still attempting access.  You can't access PLM.

You may likely be hitting  bug CSCur95552.

For some reason, Cisco TAC has not documented any work around or fixes at this time.

If running co-resident with CUCM, you need regenerate the IPSec certificate on the node where Prime License Manager is running. Then if this is your CUCM Publisher, restart the DRF Master and DRF Local services. If it's not the Publisher, just restart the DRF Local services.

You should then be able to login.

Regenerate Certificate:
Navigate to Cisco Unified OS Administration | Securtiy | Certificate Management and choose Find.
Scroll down to and choose the ipsec certificate associated with the server where PLM is running co-resident.

Choose Regenerate and wait a few moments until it indicates success.


Restart Services:
Navigate to Cisco Unified Serviceability | Tools | Control Center - Network Services.
Pick the server where PLM is running co-resident and choose Go.
Scroll to and choose Cisco DRF Master, click Restart, and wait until it has been restarted.
Scroll to and choose Cisco DRF Local, click Restart, and wait until it has been restarted.

You should now be able to log into PLM.

Restart Tomcat:
If you experience the same issue, restart Tomcat on the same server and repeat the above steps.
SSH to or open VMware console on server where PLM is co-resident.
Login as the platform administrator.
run "utils service restart Cisco Tomcat"


6 comments:

  1. Thanks for sharing a valuable blog.
    This is really a nice blog on the base of Reprise license Manager, thanks.


    Reprise License Manager

    ReplyDelete
  2. We spent 2 months with cisco TAC and they couldn't solve it ..

    This topic worked fine with me and the issue got resolved

    ReplyDelete
  3. We spent 2 months with cisco TAC and they couldn't solve it ..

    This topic worked fine with me and the issue got resolved

    ReplyDelete
  4. Anonymous3:00 PM

    Ran into this today. Restarting the DRF services did the trick, thanks

    ReplyDelete
  5. We ran to this problem on CUCM 11.0, and the problem can be solved only by restarting Tomcat service

    ReplyDelete