Upgrading CM 4.1 to CUCM 8.6

Hi All,
I have a CUCM 8.6 which was upgraded from CM 4.1 to CUCM 8.6 about few months ago by another colleague of mine. The person has left the company, and the CUCM 8.6 has not come up into the production network.
Between that time till now, there has been alot of changes made that no one has kept track with.
Looking at the situation I can see 2 options:
a) Re-do the upgrade from 4.1 to 8.6 based on the thread: https://supportforums.cisco.com/thread/2149422
b) Trace back changes manually and make the changes (i.e Bulk admin, etc?)
Just would like to ask everyone for ideas on the best way forward.. if you have any ideas that I could avoid re-doing Option (a), I would greatly appreciate it.

It depends on how many changes were made. If it was a lot I would go with option A, if you are unsure I would also go with option A, if there was only some basic changes such as phone changes, etc and you can identify them option B would be easiest.
HTH,
Chris

Similar Messages

Ask the Expert: Upgrading Cisco Unified Communications Manager (CUCM) to Version 9.1 (Drive to 9)

Welcome to the Cisco Support Community Ask the Expert conversation. Learn from experts Vijay Rao and Amit Singh about simplified upgrade process and focused support from Cisco to migrate to version 9.1.
This is a continuation of the live Webcast
Drive to 9 is a comprehensive and holistic program designed to help you upgrade the current Cisco® Unified Communications Manager installed base to version 9.1 or higher. This upgrade will enable customers to have next-generation collaboration experiences.
During the live event, Cisco subject matter experts Vijay Rao and Amit Singh focussed on the simplified upgrade process and focused support from Cisco to migrate to version 9.1. They also talked about the changes made to the licensing model of User Connect Licensing and Cisco Unified Workspace Licensing.
Vijay Rao is a Network Consulting Engineer and is currently a unified communications (UC) consultant for Bank of America. He has been providing consulting assistance to the bank for the past 6 years. He helps design complex UC networks for large enterprise customers. He was previously part of Cisco IT in the Asia Pacific, Japan, and China (APJC) region and was instrumental in designing and implementing the Bangalore campus. He has been working with Cisco for 9 years and has 12 years of UC experience. He has a Cisco CCVP® certification.
Amit Singh is a customer support engineer at the Cisco Technical Assistance Center in Bangalore, India. He has 7 years of experience in his areas of expertise: wireless, Cisco Unified Communications Manager, multiservices, Cisco Unity®, and Cisco Unified Contact Center Express. He has been involved in various escalation requests from India, Singapore, and Australia and is currently working as a technical lead for the Voice team in Bangalore, India. He is a computer science graduate.
Remember to use the rating system to let Vijay and Amit know if you have received an adequate response.
Vijay and Amit might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Collaboration, Voice and Video sub-community forum shortly after the event. This event lasts through July 19, 2013. Visit this forum often to view responses to your questions and the questions of other community members.
Webcast related links:
Webcast Video
FAQ from the live webcast
Slides from the live webcast

Hello Robert,
Apologies for a delayed response, some days get very hectic.
In CallManager, we only define the SRST reference, and CUCM version and SRST version are independent of each other.
The only thing, which is related and will change with CUCM upgrade is Phone F/w version.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr1.pdf
You may just want to check your, phone f/w compatibility with the SRST version running on your ISR G1 Gateways:
http://www.cisco.com/en/US/products/sw/voicesw/ps2169/products_device_support_tables_list.html
For Example: SRST version 7.1
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6788/vcallcon/ps2169/data_sheet_c78-520521.html
You may want to do some lab testing with CUCM 9.1 and an SRST supported f/w on your phones.
If you decide to run the old Phone/F/w to support the SRST version, you may not be able to take advantage of new features.
Also, you can try and upgrade your phones(Wih CUCM 9.1) and test them with your SRST version.
It should work fine, but from a troubleshooting perspective, TAC may request you to come into a Cisco Supported combination.
Please, let me know if this clarifies your doubt or we can have a quick phone call.
Regards
Amit Singh

Upgrade our 8.0.3 CUCM to version 9.1.X

                   Hi All,
We are planning to upgrade the our cucm 8.0.3 to 9.1.x
Can anyone tell us the steps for the upgradation. We are using the extension mobility. Prior to upgrade we already upgraded the router IOS to c2900-universalk9-mz.SPA.152-4.M5.bin(cisco 2900 series routers). the upgrade on plan on comming weekend
regards
jomyk

Hi Chris,
Thanks for the update.following is our hw details. we dont have any plan to upgrade the HW
HW Platform       : 7825I4
Processors        : 1
Type              : Intel(R) Core(TM)2 Duo CPU     E8400 @ 3.00GHz
CPU Speed         : 3000
Memory            : 4096 MBytes
Read the document according to that prepared a document. Could you cross check the document whether i missed any thing to consider the upgradation plan
III. Upgrade considerations
Need to apply the refresh upgrade cop file before doing the actual upgrade for the cucm using 9.1 image.
Sequence for the refresh /upgrade should be
a-Do the refresh upgrade (install the COP file) on the publisher and on the other node( subscriber).
b-Do the upgrade (install the ISO image of the 9.1) on the publisher server then directly do the switch version (utils system switch-version) on the publisher server.
c-Once the switch version is done on the publisher successfully, do the upgrade on the subscriber server and then do a switch version on that subscriber.
B. When we install upgrade software, there will be a temporary node outage while the Cisco Unified Communications Manager software is installed.
C. When we upgrade a cluster we will start by upgrading the publisher node. we can begin upgrading subsequent nodes in parallel after the publisher node reaches a specified point in the upgrade. There will be a temporary node outage until all subscriber nodes get upgraded to the new software version.
d. Disable the Cisco Extension Mobility service by navigating to Cisco Unified Serviceability > Tools > Service Activation
III. Upgrade from CD Rom
     Create an upgrade disk by burning the upgrade file that you downloaded onto a DVD as an ISO image.
a.
Insert the new DVD into the disc   drive on the local server that is to be upgraded.
b.
Log in to Cisco Unified Communications   Operating System Administration.
c.
Navigate to Software Upgrades   > Install/Upgrade.
The   Software Installation/Upgrade window displays.
From the Source list, choose DVD.
d.
Enter a slash (/) in the   Directory field.
e.
To use the Email Notification   feature, enter your Email Destination and SMTP Server in the fields provided.
f.
To continue the upgrade process,   click Next.
g.
Choose the upgrade version that   you want to install and click Next.
h.
In the next window, monitor the   progress of the download.
i.
If you want to run the upgraded   software at the completion of the upgrade process and automatically reboot to   the upgraded partition, choose Switch to new version after upgrade. The   system restarts and is running the upgraded software.
j.
If you want to install the   upgrade and then manually switch to the upgraded partition at a later time,   do the following steps:
•a.          Choose Do not switch to new   version after upgrade.
•b.          Click Next
The Upgrade Status window   displays the Upgrade log.
•c.          When the installation completes,   click Finish.
•d.          To restart the system and   activate the upgrade, choose Settings > Version; then, click Switch   Version.
The system restarts running the   upgraded software.
IV. Post-upgrade   tasks
•a.         Enable the Cisco Extension Mobility service by navigating to Cisco Unified Serviceability   > Tools > Service Activation.
•b.         Verify phone functions by making   the following types of calls:
•a.          Voice mail
•b.          Interoffice
•c.          Mobile phone
•d.          Local
•e.          National
•f.           International
•g.          Shared line
c.Test the following   phone features:
Conference
Barge
Transfer
C-Barge
Ring   on shared lines
Do   Not Disturb
Privacy
Presence
CTI   call control
Busy   Lamp Field
Thanks
Jomy

CUCM 8.6.2 upgrade to CUCM 10.5

Hi,
I have to upgrade a virtualized CUCM cluster (PUB, SUB1, SUB2, TFTP) version 8.6.2 SU3 to version 10.5.
As per documentation this should be a direct refresh upgrade and no need of PCD to do it.
Based on the documentation the main steps of the upgrade are:
-changing the OS to RHEL 6 (64-bit) and the Network Adapter from "Flexible" to "VMXNET 3” for the VM (shut down the VM and perform the changes)
-run ciscocm.version3-keys.cop.sgn.
-run ciscocm.free_common_space_v1.1.cop.sgn
-run the 10.5 ugrade file in following order: PUB, TFTP, SUB1, SUB2
The existing 8.6.2 OVA, 7500 users is using 2 vCPU and 80GB for each vdisk (total of 160GB).
The 10.5 OVA, 7500 users requires 1 vCPU and 110GB for the vdisk.
Does anybody know if I have to run the ciscocm.free_common_space_v1.1.cop.sgn to increase the space to 110GB on each vdisk (even if the total size is 160GB on 2 vdisks which is more then 110GB required on 10.5 OVA)?
Cisco engineer said that this is not possible as well that I can not change the OS to RHEL 6 (64-bit) on the existing server/VM (ESXi 4.1 U3.
He recommends to create a new VM using the new OVA and use the DRS and restore process for performing the upgrade.
Any input/advise will be appreciated!
Thanks.

The success to any upgrade is planning. The customer type bank or not doesn't not really matter. What is crucial is your willingness to do due diligence to make this as smooth as possible..
Here are the things you need to do in the order described
1. Read your documentation. Very crucial. CUCM10.5 is a major change on all others.
You need to start by reviewing the upgrade guide, release notes, and new and changed documentation for all the steps and considerations you need to take into account for this upgrade.
NB: The upgrade guide for IM and P is merged with that of CUCM and here is the link for it..
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100.html
Release notes found here:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/10_5_1/CUCM_BK_CE15D2A0_00_cucm-release-notes-1051.html
2. Plan for your license migration. Usually this involves two steps
a. Use cisco LCU (license count utility tool) to generate license report on your existing cluster. This can be downloaded from cco.filename is LCUZIP-Ver9.1.2.zip
Ensure that you install any unsed DLU and license PAKS on your cluster before you run this..
b. Next email this file obtained from lcu (this is a csv file) tool cisco licensing team [email protected]. This will confirm that your service contracts is in order prior to requesting new licenses for 10.5
c. Login in Prime License Manager after successfully migrated from 8.6 to 10.5
Use the following procedure to generate a license request.
Log in to Cisco Prime License Manager.
From the Licenses > Fulfillment page, select Generate License Request from the drop-down list under
Other Fulfillment Options.
The License Request and Next Steps window appears. Copy the selected text to your clipboard or click save it to a file on your PC and send to [email protected] to get permanent licenses
3. Document the steps you will use for the upgrades. You can send a draft here and I will be happy to review this with you.
Ensure that you write down step by step what you will do on the day. The upgrade guide should be used to write down what you will do on the day. This is a very long upgrade, hence you need to document in detail what you will be doing.
4. Contact the relevant team to get your ESW/UCSS contract numbers. You need this to login to PUT to download your media. I was doing an upgrade recently and realised that the customers ESW contract has expired..So this is crucial.
Upgrade tasks
PCD is your best bet. Install PCD on your Esxi host. Just create a new VM for it. It makes things much easier for you..If you don't have spare capacity to create new VM then do it manually
5. Before you begin..Take a back up of your cluster.
6. VM machine sizing.
Please refer to cucm10.5 ova readme file, found on CCO. Depending on the OVA template you used for your cucm8.6, you may need to change the vm setings prior to upgrade. This is because the disk size and cpu requirements is different for cucm10.5 on some ova templates.
6a. You will need to change the vm adapter settings on your VM. This is documented in the cucm10.5 ova. Your best option is to use esxi powercli. You can download this from VMware website provided you have a valid service contract.
6b. You will need to change your guest operating system to RHEL6. This is also documented in the 10. 5 OVA
7. If your 8.6 cluster is running on VM at the moment, then just do a direct upgrade to 10.5.
NB: before you upgrade you will need to install the ff cop file on all the servers in the cluster
ciscocm.version3-keys.cop.sgn
After this upgrade your cluster starting with cucm. The upgrade guide will tell you the order of the upgrade..
7. Once upgrade is completed, perform the post upgrade tasks.
8. Develop a detailed test plan. Ensure all critical component of your customer is covered in the test plan. Test features that are critical to them
9. Finally, ensure your CV is updated. In case you need to look for another job if everything breaks: (lol)
Answer to your questions:
"As per what I see, an easy option would be to create a new virtual machine and use a DRS? but, would it work if I create the DRS on CUCM 8.6 and use it on 10.5?"
---You may create a new VM or adjust VM settings as I already discussed. If you want to create a new VM, then you will create VM with cucm10.5 ova, install cucm 10.5 on it.
You will then upgrade your current 8.6 to 10.5, take a DRS back up and go and do a DRS restore on the new 10.5 you have installed on the new VM. You cant restore 8.6 to 10.5.
"What happens to presence server? I understand I have to upgrade it too but, will the configuration be transferred to CUCM 10.5 (I mean, services associated with the menus that originally were on presence 8.6)?"
---Yes IM and P needs to match the cucm version. Yes the configuration will be transferred. You don't need to do anything. Please read the upgrade guide carefully.
"If all of the apps are on 8.6, do we need to upgrade everything to 10.5 at the same window?"
---For CUCM and IM and P, yes you have to upgrade them at the same time. The versions must match. It is advisable that you have unity connection on same version too, but not critical. I believe 8.6 unity connection will work with cucm10.5 ( I haven't checked this, so confirm it yourself)
The upgrade is a refresh upgrade. So it does take a long time and there are several reboots. The publisher is the one that takes the longest amount of time. The subscriber is about half the time it takes for the Pub to upgrade. You should be fine with a weekend maintenance widow. Friday evening to Sunday.
"If upgrade fails, can I still go back to 8.6?" Yes as long as you do not use the "free common space cop file" This is discussed in the upgrade guide as well.
It looks daunting, but if you do your home work, you will be fine and we are here to help and assist you all the way
Please refer to this thread for similar discussions:
https://supportforums.cisco.com/discussion/12319616/vm-upgrade-cucm-86-105-question

CUCM 8.6.2 to 10 Upgrade

Hi everyone,
Didn't have the following situation so far, so need advice:
I have an upgrade on the way, from CUCM 8.6.2 to CUCM 10, and that's fine,
But client needs to expand the cluster, by adding additional subscriber nodes.
Do I go with upgrade first, and then add more subscribers, afterwards?
or
Do I add subscribers first, and then do an upgrade?
Regards
Vladimir

Hi Aman,
Thank you for your prompt response!
Can you give me the reason, why would you go with adding first, migrate later?
Since it doubles the effort. Is there any particular reason for the choice?
I personally would go with migration first, and add subs afterwards...
Are there any cons with my option?
Thank you again!
V

Moving CUCM Cluster from 7.1.5 to 10.5 and migrating P2V

Community - What I am looking for is advice from those who have actually done it! Reading about sex and having sex are two different subjects. I am finding relevant docs on the CISCO site, some are contradictory. One doc on CISCO Prime Deployment says yes to CUCM 7.1.5 and another says no. We know the standard "refresh" upgrade process, cop files and that entire drill. What we are looking for is comments from those who have done it before! Our Cluster is mixed MCS servers with CUCM PUB and SUB at Version 7.1.5. Unity/UCCX at 8.0.2 with no HA (don't ask). We want to end up with BE6000 and have UCCX in HA mode on Version 10.5 (10.6)! So what do you think, Migrate all in cluster to a common base like 9, then migrate to VM and upgrade? Or try to do it some other way.
All Comments welcome and very appreciated!

@Jamie I think we eliminated PCD as a strategy. We see this as following the usual upgrade process and assume we will be taking multiple steps. Step one would be to get all on a common version and we are thinking 8.5. At that point we could do the P2V and then upgrade to 10.5 on ESXi. We need to create some HA for Unity and UCCX, but will do that after we get to 10.5. Hopefully we can upgrade the CUCM Publisher, during which time the rest of the cluster will be operational? Put Pub back online as 8.5 and then do the subscriber. Again, we think UCCX and Unity will be operational on PUB as we upgrade SUB. Once on CUCM 8.5 we will then schedule maintenace windows to upgrade Unity and UCCX. At that point we have a cluster on 8.5 ready for P2V. We do that migration and when all are on ESXi, we do the upgrade to 10.5 and add in a HA server for UCCX and Unity. How does that sound? As we really dont want phones rebooting and downloading firmware, we will do that ahead of time, but are researching the level we should get them to before the 8.5 upgrade.
@Amn thanks for the link. We have been reading all we can on the CISCO site, and are really seeking out those who have done this and can share experience.
Thanks to all who comment.

Cisco unified Operation Manager 2.3 with CUCM 8.6

Hi Guys,
My Customer today have CUOM 2.3 and CUCM 7.1.3. He is planning to do upgrade CUOM 8.6 and CUCM 8.6. My question is: Is it possible to do upgrade CUOM directly to 8.6? If CUOM to be upgraded to 8.X do we need to purchase the upgrade license?
Thanks,
Wilson

I don't think you can install on top of CUOM 2.3, a CUOM 8.X. Not even a 8.0
As said, you can restore a CUOM 2.3 backup on an 8.X.
http://www.cisco.com/en/US/docs/net_mgmt/cisco_unified_operations_manager/8.5/installation/guide/install.html#wp1054045
As far as I can see after CUOM 8.5 the 2.3 migration path is no longer mentioned.
Cheers,
Michel

CUCM 10.5 - CSR/SAN issue

Just upgraded this past weekend to CUCM 10.5. Today, I'm trying to generate updated certs for the servers per our security policy. What i'm finding, though, is that the old way of adding additional SANs doesn't seem to work anymore. We use Active Directory's CA, and usually I would just populate the SANs in the additional attributes field. Doing that now, though, prevents the cert from being accepted at all. Using the multi-server option, it will only take SANs that have the FQDN, which is great, but we also use just the hostname to access servers as well...
Has anyone come across a good way to address this kind of issue?

Thanks Chris. I've tried that, and it's partially working. Where I'm stuck is having just hostnames as well as FQDNs. The TAC engineer I'm working with mentioned attaching a list of separate hostnames to the CSR request (doing a multi-server CSR). I'm wondering, though, do I just attach the .txt file and generate the CSR or do I need to do anything else to make sure that it populates the hostnames in the text file as well as the automatically discovered ones?

IM & P 10.5.1 install or upgrade

Using the Boot disk I am building an IM&P SUB after putting the CUCM PUB details in during the install process I get the error of mismatched versions. fair enough so I download and put on FTP the SU2 10.5.1.12900-2 and resinstall but the installation says there are no patches to be found. The FTP server is being used for CUCM upgrades and is working.
CUCM = 10.5.1.11900-13
IMP pub = 10.5.1.12900-2
I am trying to add an IM & P to the subcluster.
Error = Remote host contains no valid patches in directory.
the patch is UCSInstall_CUP_10.5.1.12900-2.sgn.iso

Have you tried just installing direct from the 12900-2 image? I downloaded that same image for a lab setup and it is bootable. You should be able to boot from it without having to install it as a patch or anything.

"Error encountered: ERROR: Final installdb run unsuccessful" during firmware cop installation

Hi all,
Just a heads up to anyone else who encounters this error when installing device firmware cop files onto CUCM.
We were upgrading the firmware on our CUCM cluster (small - consists of 1 x Publisher and 1 x Subscriber) - running 8.0.2.40000-1
I was installing:
cmterm-7936-sccp.3-3-21.cop.sgn
cmterm-7937-1-4-4-SCCP.cop.sgn
cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn
cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn
When doing so on the publisher server - it was throwing the following error output (note that the files actually ended up on the TFTP server but devices were not picking up the new firmware):
Installation Status
File           cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn
Start Time           Thu Mar 06 19:34:24 WST 2014
Status
Error encountered: ERROR: Final installdb run unsuccessful
03/06/2014 19:33:42 file_list.sh|Starting file_list.sh|<LVL::Info>
03/06/2014 19:33:42 file_list.sh|Parse argument method=sftp|<LVL::Debug>
03/06/2014 19:33:42 file_list.sh|Parse argument source_dir=/|<LVL::Debug>
03/06/2014 19:33:42 file_list.sh|Parse argument dest_file=/var/log/install/downloaded_versions|<LVL::Debug>
03/06/2014 19:33:42 file_list.sh|Parse argument remote_host=10.133.1.240|<LVL::Debug>
03/06/2014 19:33:42 file_list.sh|Parse argument user_name=ccmadministrator|<LVL::Debug>
03/06/2014 19:33:42 file_list.sh|Calling SFTP command with metering off|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|SFTP command complete (0)|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|List file (pre-filtered):|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) RSA|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) UC|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) WIRELESS|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) asa914-k8.bin|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) cmterm-7936-sccp.3-3-21.cop.sgn|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) cmterm-7937-1-4-4-SCCP.cop.sgn|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|/usr/local/bin/base_scripts/filter.sh file=/var/log/install/downloaded_versions|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Parse argument file=/var/log/install/downloaded_versions|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|No patch type specified. Optional.|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|No upgrade mode specifed. Optional.|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Current version is 8.0.2.40000-1|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Processing token "RSA"|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|INorOUT=OUT RSA: Not a signed patch file|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Processing token "UC"|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|INorOUT=OUT UC: Not a signed patch file|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Processing token "WIRELESS"|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|INorOUT=OUT WIRELESS: Not a signed patch file|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Processing token "asa914-k8.bin"|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|INorOUT=OUT asa914-k8.bin: Not a signed patch file|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Processing token "cmterm-7936-sccp.3-3-21.cop.sgn"|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|INorOUT=IN cmterm-7936-sccp.3-3-21.cop.sgn: filter passed|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|Processing token "cmterm-7937-1-4-4-SCCP.cop.sgn"|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|INorOUT=IN cmterm-7937-1-4-4-SCCP.cop.sgn: filter passed|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|Processing token "cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn"|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|INorOUT=IN cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn: filter passed|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|Processing token "cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn"|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|INorOUT=IN cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn: filter passed|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|List file (post-filtered):|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) RSA:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) UC:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) WIRELESS:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) asa914-k8.bin:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7936-sccp.3-3-21.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7937-1-4-4-SCCP.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|List file (pre-structured):|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) RSA:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) UC:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) WIRELESS:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) asa914-k8.bin:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7936-sccp.3-3-21.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7937-1-4-4-SCCP.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|List file (post-structured):|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE) <InstallList>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <FilteredItem type="" file="RSA" result="1"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <FilteredItem type="" file="UC" result="1"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <FilteredItem type="" file="WIRELESS" result="1"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <FilteredItem type="" file="asa914-k8.bin" result="1"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <InstallItem type="copfile" secure-file="cmterm-7936-sccp.3-3-21.cop.sgn" version="" file="cmterm-7936-sccp.3-3-21.cop" reboot="no"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <InstallItem type="copfile" secure-file="cmterm-7937-1-4-4-SCCP.cop.sgn" version="" file="cmterm-7937-1-4-4-SCCP.cop" reboot="no"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <InstallItem type="copfile" secure-file="cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn" version="" file="cmterm-7941_7961-sccp.9-3-1SR2-1.cop" reboot="no"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <InstallItem type="copfile" secure-file="cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn" version="" file="cmterm-7945_7965-sccp.9-3-1SR2-1.cop" reboot="no"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE) </InstallList>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|success|<LVL::Info>
03/06/2014 19:33:46 file_list.sh|file_list.sh complete (rc=0)|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|Starting upgrade_validate_file.sh|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|Parse argument method=sftp|<LVL::Debug>
03/06/2014 19:34:19 upgrade_validate_file.sh|Parse argument source_dir=/|<LVL::Debug>
03/06/2014 19:34:19 upgrade_validate_file.sh|Parse argument file_name=cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn|<LVL::Debug>
03/06/2014 19:34:19 upgrade_validate_file.sh|Parse argument remote_host=10.133.1.240|<LVL::Debug>
03/06/2014 19:34:19 upgrade_validate_file.sh|Parse argument user_name=ccmadministrator|<LVL::Debug>
03/06/2014 19:34:19 upgrade_validate_file.sh|Getting patch size via sftp for cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|Size of patch file = 6018125|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|Total space needs = 12036250|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh| Free space : 126461788160|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|Space needed : 24072500|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|There is enough space on device to proceed.|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|success|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|upgrade_validate_file.sh complete (rc=0)|<LVL::Info>
03/06/2014 19:34:19 upgrade_get_file.sh|Starting upgrade_get_file.sh|<LVL::Info>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument method=sftp|<LVL::Debug>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument source_dir=/|<LVL::Debug>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument file_name=cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn|<LVL::Debug>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument dest_dir=/common/download/|<LVL::Debug>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument remote_host=10.133.1.240|<LVL::Debug>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument user_name=ccmadministrator|<LVL::Debug>
03/06/2014 19:34:20 upgrade_get_file.sh|Starting SFTP of cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn|<LVL::Info>
03/06/2014 19:34:21 upgrade_get_file.sh|SFTP command complete (0)|<LVL::Info>
03/06/2014 19:34:21 upgrade_get_file.sh|Download of iso file RTMTStart|<LVL::Notice>
03/06/2014 19:34:21 upgrade_get_file.sh|Create md5 "/common/download/cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn.md5"|<LVL::Info>
03/06/2014 19:34:21 upgrade_get_file.sh|MD5(/common/download/cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn)= e3:02:d3:e1:89:ff:a1:eb:0a:71:52:03:ad:d7:e2:85|<LVL::Debug>
03/06/2014 19:34:21 upgrade_get_file.sh|Create md5 complete|<LVL::Info>
03/06/2014 19:34:21 upgrade_get_file.sh|Authenticate file "/common/download/cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn"|<LVL::Info>
03/06/2014 19:34:21 upgrade_get_file.sh|File authentication complete|<LVL::Debug>
03/06/2014 19:34:21 upgrade_get_file.sh|Download of iso file RTMTFinish|<LVL::Notice>
03/06/2014 19:34:22 upgrade_get_file.sh|success|<LVL::Info>
03/06/2014 19:34:22 upgrade_get_file.sh|upgrade_get_file.sh complete (rc=0)|<LVL::Info>
03/06/2014 19:34:24 Terminating active side processes
03/06/2014 19:34:24 Terminating active side processes done
03/06/2014 19:34:24 Terminating inactive side processes
03/06/2014 19:34:24 Calling /usr/local/bin/base_scripts/sd_killPartitionB_PIDs.sh
03/06/2014 19:34:24 Terminating inactive side processes done
(13953) Thu Mar 6 19:34:30 WST 2014
install option
(13953) Thu Mar 6 19:34:30 WST 2014
Successful untarring of option /common/download//cmterm-7945_7965-sccp.9-3-1SR2-1.cop.
(13953) Thu Mar 6 19:34:36 WST 2014
Publisher: Starting installdb... /bin/su -l informix -s /bin/sh -c "source /usr/local/cm/db/dblenv.bash /usr/local/cm ; source /usr/local/cm/db/informix/local/ids.env ; nice /usr/local/cm/bin/installdb -x /usr/local/cm/db/xml/xml"
disablenotify rc[0]
xml DSN=ccm_super /usr/local/cm/db/xml/xml
installXml rc[1]
enablenotify dsn[DSN=ccm_super]
enablenotify rc[0]
installdb Failure [-x] 1
(13953) Thu Mar 6 19:34:47 WST 2014
ERROR: Final installdb run unsuccessful
I'd read in various places to perform a CLI command "run loadxml" - which we did but it produced the following output:
admin:run loadxml
This command is processor intensive, and may take a few minutes to run.
It should only be run on the publisher.
Some services may require a restart afterwards.
This is a CPU intensive command and will take a considerable amount of time to complete. Do you want to continue (y/n)?
Starting loadxml
disablenotify dsn[DSN=ccm_super]
disablenotify rc[0]
xml DSN=ccm_super /usr/local/cm/db/xml/xml
installXml rc[1]
enablenotify dsn[DSN=ccm_super]
enablenotify rc[0]
installdb Failure [-x] 1
loadxml function complete
Failure essentially.
Note that the installation went ahead without issues on the Subscriber servers after we tried on the publisher. I believe this is due to it only copying the files to the TFTP server and not updating the database.
I also noted that the following features vanished from the CUCM Administration GUI (the menus were there but the pages came up blank):
"Enterprise Paramaters"
"Enterprise Phone Configuration"
"Service Parameters" (after selecting "server" & "service" drop down options, nothing was displayed)
Within individual "Phone Configuration" - the entire "Product Specific Configuration Layout" was missing from all devices.
I was also unable to export the 'Cisco Database Installation Service' logs from RTMT - it threw an error to the status bar at the bottom stating "Collection cancelled for node <publisher> due to the error" (and there was no error info output...joy!).
I called in TAC and Roman Kramarski assisted me via WebEx to full resolution of the issue - thanks Roman
After running "run loadxml"
We ran the following command which showed us (after much wizzing by of entries) the list of log files, the 5th or so last file in the list being the log output from the "run loadxml" output -
The command: "file list activelog /cm/trace/dbl/sdi detail date"
Our file in question happened to be called "installdb20140306-230735.log" (like I said, was about 5th from the bottom of the list)
Next we viewed the file:
"file view activelog /cm/trace/dbl/sdi/installdb20140306-230735.log"
In the file, fairly close to the top, it showed the following error message:
"23:07:35.047 |   DOMErrorReporter::fatalError *ERROR* Fatal Error at file /usr/local/cm/db/xml/xml/366X_display_instance-fxo_port_gs.xml, line 56, column 22"
This, along with the output of the run loadxml command, indicated that "/usr/local/cm/db/xml/xml/366X_display_instance-fxo_port_gs.xml" file was corrupted or incomplete.
Roman (TAC) then used the Cisco access to root in order to look at the actual file.
It was incomplete - it ended mid closure of a tag:
"<name>OutputAttenuation</n#"
(Instead of "<name>OutputAttenuation</name>" plus a whole bucketload more output.
Luckily I had a fresh install of the exact same version of CUCM just installed on in a dev environment - so Roman was able to get into that one, TFTP the file out, and then TFTP the new file in.
We moved the old corrupt file into another folder (as we renamed it initially and then ran "run loadxml" which produced the error again) - copied the new complete file into the folder - then "run loadxml" ran successfully.
admin:run loadxml
This command is processor intensive, and may take a few minutes to run.
It should only be run on the publisher.
Some services may require a restart afterwards.
This is a CPU intensive command and will take a considerable amount of time to complete. Do you want to continue (y/n)?
Starting loadxml
disablenotify dsn[DSN=ccm_super]
disablenotify rc[0]
xml DSN=ccm_super /usr/local/cm/db/xml/xml
installXml rc[0]
enablenotify dsn[DSN=ccm_super]
enablenotify rc[0]
installdb Success[-x]
loadxml function complete
NOTE that the running of run loadxml did not take that long and didn't cause any outages to my system.
After we did this - the installations went ahead successfully.
After a restart of the TFTP service on each server - firmware upgrades went ahead successfully.
Basically - you can do the initial troubleshooting of checking logs of run loadxml and then pass that detail to Cisco TAC to get them to use root access to copy a fresh version of the file across.
Hope this helps.

Hi Thanks for the information, this help me a lot, I have the same issue but with some differences, because when I search the error on the log file, I saw
08/25/2014 06:14:49.911 installdb|   DOMErrorReporter::fatalError *ERROR* Fatal Error at file , line 0, column 0
message: An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=/usr/local/cm/db/xml/xml/ICS77XX_MRP2XX_display_instance-bri.xml|
08/25/2014 06:14:49.911 installdb|<--DOMErrorReporter::fatalError |
When I search the file I couldn´t find it, so I think this could be because I made a booteable ISO from an upgrade from the Cisco Page, so I go to the production server version 6.1.2 and copied the file missing into my lab and run the command "run loadxml" sucessfully, after that everything works great!
Thanks in advance for your time to post this.
Regards!

IM & Presence migration: 9.1(2) to 10.5(2)

Hi,
We are migrating our IM&P (along with CUCM) from 9.1(2) to 10.5(2). Using PCD for upgrade.
We go the CUCM upgrade files using the PUT tools. Cannot find the files for IM & P upgrade.
PCD accepts the CUCM file as valid upgrades for Unity and CUCM. It does not recognize it as valid for IM&P.
I downloaded the IM&P file for 10.5(2) from Cisco downloads, but it is only for upgrades from 10.0.
https://software.cisco.com/download/release.html?mdfid=286265496&flowid=70402&softwareid=280840578&release=Security_Patches&relind=AVAILABLE&rellifecycle=&reltype=latest
It says for 9.0+ use PUT. But I cannot find it in PUT.
Any Idea where to get the valid upgrade file for 10.5(2) from 9.1?
Thanks

The downloaded upgrade should work fine, not sure how intelligent PCD is but have you checked the release notes and installed the necessary cop file?
IM and Presence Service
You must also install the ciscocm.version3-keys.cop.sgn cop file before you upgrade to IM and Presence Service Release 10.5(1), or later, from any release earlier than 10.0(1). This COP file is necessary for all upgrades from pre-10.0(1) to 10.5(1) and later.
Upgrade from Cisco Unified Presence 8.5(4)
For upgrades from Cisco Unified Presence 8.5(4), you must install two COP files in the following order before you begin the upgrade:
Install the refresh upgrade COP file, cisco.com.cup.refresh_upgrade_v<latest_version>.cop.You can download this COP file from Cisco.com.
Install the RSA-3 key COP file, ciscocm.version3-keys.cop.sgn.
Thanks,
Richard

MeetingPlace support for Outlook 2010

We have a client running CUCM version 7.1.3.30000-1 and using Cisco MeetingPlace version 2.1.1.2.
When my client migrated their users to Office 2010, they have been unable to use Meeting place, they get the following error:
"unable to download, unspecified error web browser"
As I have read this MeetingPlace version does not have support for Outlook2010 plugins, and we would have to upgrade to MeetingPlace 7.1 in order to solve this problem
With this environment:
a) Does MeetingPlace 7.1 support Outlook2010 plugins??
b) Can we upgrade this meeting place version to a new one supporting Outlook2010 plugins??? Or We also would have to upgrade CUCM version??
Thank you
Enrique Villasana

Enrique,
1. Yes, MP 7.1 supports MS Outlook 2010. Please refer http://www.cisco.com/en/US/partner/docs/voice_ip_comm/meetingplace/7_1/english/release_notes/mp71rn.html#wp127737
2. If MP needs to be upgraded to 7.1 then CUCM needs to be at 7.1.5 ( in 7.x series ). Please refer http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace,_Release_7.1_--_Component_Compatibility_Matrix
Hope it helps ?
GP.
Pls rate helpful posts by clicking on stars below the post !!

CISCO DX 650-UNABLE TO GET PLAY STORE--- !!!

Hi Team,
We have multiple Cisco DX650 at our client location.
I have Checked the Parameter in CUCM device page that says allow application from android market.
Even allow application from unknown source is enabled
Tried resetting,rebooting etc no go
Play store icon is visible on few phones but not on all. Is it any kind of a bug? which is causing it? or shall we need to upgrade.
We are on CUCM 9.1.2
Please help this is really an urgent matter as alL this phones are used by VIP users.
Rgds,
Ajith

Hi Ajith,
An out of the box phone will have PlayStore available to user. But, once a config file is downloaded, then PlayStore is immediately disabled by BundledAppInstaller, then config file is read to determine whether admin wants PlayStore to be enabled or not, and thus determine the availability of PlayStore to user.
I did not find any specific bug for this behavior, you can try upgrading to latest load on a DX650 facing the issue and check if the issue goes away.
HTH
Manish

BE6K supported options for voice conferencing

Hello All,
Does anyone know or understand why CUCM 8.6.2 on BE6K cannot support MeetingPlace 8.5? I could understand if its on the same UCS but I understand from Cisco SE the BE6K is not supported on box or off box when intergrated with MeetingPlace. My only options are to upgrade the BE6K to Full CUCM and CUC at a cost of 11.00(CUCM) + 11.00 (CUC) * number of users (Plus ESW+UCSS).
Thanks
Roger....

The idea behind the BE6000 marketing bundle is that it is designed to support up to 1000 users per system, given the lower cost C220M3 server configuration (SATA drives). In a Unity Cxn HA cluster running A/A, 500/500 would be ideal. If you place both Unity Cxn servers in standalone mode with 500 users each, I can't see that offering any different load on the system. So you should be ok, just realize if you separate the UCM cluster across a WAN, you also have a BW requirement to meet, although this is much less most likey - min 3Mbps but depends on your busy hour calculations. UCM BW requirement is discussed in the main UC SRND.

UCCX 7.0.1SR5 to 8.0 upgrade while also adding LDAP integration for CUCM - what happens to agents and Historical Reporting data?

Current State:
•    I have a customer running CUCM 6.1 and UCCX 7.01SR5. Currently their CUCM is *NOT* LDAP integrated and using local accounts only. UCCX is AXL integrated to CUCM as usual and is pulling users from CUCM and using CUCM for login validation for CAD.
•    The local user accounts in CUCM currently match the naming format in active directory (John Smith in CUCM is jsmith and John Smith is jsmith in AD)
Goal:
•    Upgrade software versions and migrate to new hardware for UCCX
•    LDAP integrate the CUCM users
Desired Future State and Proposed Upgrade Method
Using the UCCX Pre Upgrade Tool (PUT), backup the current UCCX 7.01 server.
Then during a weekend maintenance window……
•    Upgrade the CUCM cluster from 6.1 to 8.0 in 2 step process
•    Integrate the CUCM cluster to corporate active directory (LDAP) - sync the same users that were present before, associate with physical phones, select the same ACD/UCCX line under the users settings as before
•    Then build UCCX 8.0 server on new hardware and stop at the initial setup stage
•    Restore the data from the UCCX PUT tool
•    Continue setup per documentation
At this point does UCCX see these agents as the same as they were before?
Is the historical reporting data the same with regards to agent John Smith (local CUCM user) from last week and agent John Smith (LDAP imported CUCM user) from this week ?
I have the feeling that UCCX will see the agents as different almost as if there is a unique identifier that's used in addition to the simple user name.
We can simplify this question along these lines
Starting at the beginning with CUCM 6.1 (local users) and UCCX 7.01. Let's say the customer decided to LDAP integrate the CUCM users and not upgrade any software.
If I follow the same steps with re-associating the users to devices and selecting the ACD/UCCX extension, what happens?
I would guess that UCCX would see all the users it knew about get deleted (making them inactive agents) and the see a whole group of new agents get created.
What would historical reporting show in this case? A set of old agents and a set of new agents treated differently?
Has anyone run into this before?
Is my goal possible while keeping the agent configuration and HR data as it was before?

I was doing some more research looking at the DB schema for UCCX 8.
Looking at the Resource table in UCCX, it looks like there is primary key that represents each user.
My question, is this key replicated from CUCM or created locally when the user is imported into UCCX?
How does UCCX determine if user account jsmith in CUCM, when it’s a local account, is different than user account jsmith in CUCM that is LDAP imported?
Would it be possible (with TAC's help most likely) to edit this field back to the previous values so that AQM and historical reporting would think the user accounts are the same?
Database table name: Resource
The Unified CCX system creates a new record in the Resource table when the Unified CCX system retrieves agent information from the Unified CM.
A Resource record contains information about the resource (agent). One such record exists for each active and inactive resource. When a resource is deleted, the old record is flagged as inactive; when a resource is updated, a new record is created and the old one is flagged as inactive.

Upgrading CM 4.1 to CUCM 8.6

Similar Messages

Maybe you are looking for