Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

How to restart CUCM with software or Web mood ?

i have one issue my CUCM is Hangk and i didnot login by web page. can any one tell how can i solve this problem.

2 REPLIES

Re: How to restart CUCM with software or Web mood ?

You could ssh into the CUCM using OS admin creds and issue the command utils service restart Cisco Tomcat to restart the Tomcat service. If that doesn't resolve the issue, try utils system restart to restart the server.

Sent from Cisco Technical Support iPhone App

Please rate useful posts.
New Member

Re: How to restart CUCM with software or Web mood ?

Hi Khalid,

If the above doess't resolve the issue, you can also SSH and have a look to your physical drives status by issue SHOW HARDWARE .

Btw what CUCM version you are using ? There is an issue found on 8.5(1)base  [8.5.1.10000-26]

-------------------------------------------------------------------------------------------------------------

The issue:

Customer will reboot publisher server and it WILL NOT come back up.  The file system is corrupt. 

The Workaround:

Run the recovery CD and repair the file system. 

The Symptoms:

Backups will fail completely. 

Access to CCM admin page and RTMT will stop working

If you see either of these symptoms, first log into the SSH interface.  When you log in you will receive a page full of Javalang Errors.  If you are seeing these errors, have the customer download and burn the recovery CD before rebooting the server, this will minimize downtime of the pub to around 20 minutes.

Once the recovery CD is ready to go, run it, from the menu select the “repair file system” option and let it do its thing.  Once done, remove the recovery cd and boot the server normally.  In all cases this got them back up and running.

The Fix: 

Upgrade to 8.5(1)SU2 or later. 

The Caveat:

IF YOU DO NOT UPGRADE IN 20-30 DAYS, BE PREPARED FOR THE ISSUE TO COME BACK AND YOU WILL HAVE TO REPEAT THIS PROCESS AGAIN

I was told by Cisco that there are RAID driver issues in the 8.5(1) base code that are causing this.

---------------------------------------------------------------------------------------

HTH.

221
Views
0
Helpful
2
Replies