Some strange issues have occurred recently, which a restart of CUCM2 may help resolve.
We will be restarting CUCM2 Tuesday morning at 6 am.
The location on campus which use attendant console will need to have those services restarted on the CUCM2 and 1 servers once 2 is up and running.
Please let Kevin or I know if you notice any problems after the restarts.
Thanks.
Jamie Voyles
HSB 119
217 206-7840
The restart did not help the issues, so we will be making another attempt Wednesday morning to correct the problem. Once again the CUCM2 server will be off line.
No change to the CCM2 server. I will again contact Cisco TAC and work with the engineer.
The operator station is now unable to communicate with CUCM2. We are escalating the ticket we have with Cisco TAC since we now have a service outage.
Cisco TAC has determined that we need to wipe the drives on CUCM2 and restore the files from the Backup we created today. Phones will switch from CUCM2 to CUCM1 in less than a second, according to TAC. To minimize intruptions we will shut CUCM2 down before 6:00am Friday morning and not bring it back up on the network. The phones will function on CUCM1, we will work to rebuild CUCM2 during the day on Friday.
No changes today. We are running ALL Voice servcies on CUCM1. We were unable to reload the software version on CUCM2, the disc we have does not boot the server. I have informed the engineer with our TAC of our situation and will monitor email over the weekend.
Process continues, we have reloaded the current version of the Cisco software to the subscriber server CUCM2. The subscriber server is still not working 100%. It seems better in that it is not sending constant error messages, but there are features which have not yet been restored. The phones are again communicating with CUCM2 so we do have server redundancy once again.
We are in contact with Cisco TAC and waiting for a reply. I will post as we have more information.
Jamie.
Clarification: one of the ‘features’ referred to in Jamie’s Dec. 3rd comment post is the ability to select the “speak to operator” function on the calling tree. This feature currently is not working (it loops back to the beginning of the tree) and is one that does not have a redundant counterpart in the other CM server. Jamie is keeping the departments posted on repair progress, which includes a firmware patch application tomorrow (Thursday) morning.
Update on CUCM Subscriber server-
The firmware upgrade went in just fine however the symptoms (issues) remain, no change. I have contacted our Cisco account rep. Barry Tobias and asked that he escalate our case with Cisco TAC. The operators station is unchanged the message (press one for the operator) is currently not working. I will be working with Patsy after 8:30 to alter the option so that when selected it rings to a phone which can be answered. The Sangamon Auditorium Ticket office Attendant console is not working correctly and I will see what type of temporary work around we can arrange. Just having all their phones ring does work just not as reliable as the Att console.
I will keep you updated
Jamie
Update
After 3 ½ hours on the phone with Cisco TAC the recommendation is for us to reload the software again on the Subscriber server, it appears that some of the tomcat files are corrupt. So I will in early again tomorrow to rebuild the server. The same TAC engineer is going to call me at 8:00am Friday. To see if the second rebuild is a success. We should know before the TAC engineer calls if the rebuild worked. We have in place a work around for the operator and the ticket office. Calls to the main campus number can now be answered.
The Rebuild of the subscriber server this morning Friday Dec 7 seems to have resolved the primary issue. The two servers are still having some minor problems and a new ticket has been issued for those with Cisco TAC.
Thanks for your patience
Jamie
We have two Cisco TAC cases open on for the possible HP Hardware issue and a second for possible software problems.
The engineer for the hardware TAC case wants us to run an HP Smart Start CD which will require 1-2 hours of down time for the Subscriber server. I really don’t want to do this now, the phones are working and both Attendant consoles are working so to rush and try this now doesn’t make sense. I would rather try this on Dec 27-28 Thur Fri after Christmas. The impact on faculty and staff will be significantly lessened. I will put the case on hold.
The Subscriber software case is still open and I’m waiting for more requests, but this is the same situation, I would rather not cause any issues in the last couple of weeks of the semester for the faculty and students. If we are requested to try anything that will cause a down time we would postpone it also.