Upgrade Unity Connection Failing

I am upgrading a Unity Connection from
Version '7.1.5.33900-10 Unrestricted' to '8.5.1.13900-5 Unrestricted'
It fails with hardware validation (error below)
My hardware is a VM on a C210M2
Memory: 6144
CPU: 2
HD1: 146gb
HD2: 146gb
Do I need a special version of CUC for VM?
Any Help appreciated.
James
10/18/2011 14:13:48 upgrade_manager.sh|Check if the upgrade is allowed|<LVL::Info>
10/18/2011 14:13:48 upgrade_manager.sh|Validate hardware for the upgrade|<LVL::Info>
10/18/2011 14:13:48 upgrade_manager.sh|Hardware is supported for the upgrade|<LVL::Info>
10/18/2011 14:13:48 upgrade_manager.sh|Validate hardware for "connection" deployment|<LVL::Info>
10/18/2011 14:13:48 upgrade_manager.sh|File:/common/download/8.5.1.13900-5/Cisco/base_scripts/upgrade_manager.sh:892, Function: validate_upgrade_allowed(), This server is not supported for use with the version of "connection" that you are trying to install. For information on supported servers, see the applicable version of the "connection" Supported Platforms List at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html|<LVL::Error>
10/18/2011 14:13:48 upgrade_manager.sh|Cleanup RAM disk|<LVL::Info>

Right - after much testing - found out the solution to this problem.
The Cisco OVA Templates dont work for CUC for certain install disks (well for at least 7 that I tried !)
Tested Disks (with VSXI version 4.1)
CUCM 8.5 - 80-9842-02
CUCM 8.5 - 80-9927-02
CUCM 8.5 - 80-9929-01
CUCM 8.5 - 80-9842-02
CUCM 8.6.1a - 80-9986-02
CUCM 8.6.1a - 80-9988-02
CUCM 8.6.1a - 80-9989-02
You need to load the OVA template and make the following changes -
Memory     :     6gb (can be set to 8gb if required)
CPU          :     2 (can be set to 3 if required)
Video          :     16mb (hard set)
VMCI          :     Unrestricted (enable checked)
SCSI          :     LSI Logic Parallel
HD          :     200gb - independent persistent
Network      :     needs to be 'connect at power on'
FD              :     Client Device 'Connected' but I dont think this setting matters.
Now Cisco Unity Connection appears at as part of the installable product suite.
I think the OVA templates are extremely poor - clearly untested.
eg - its names your VM - ALIGNED_500User-UnityConnection1CPU160GB.ova etc
Anyway - hope this information help other people from wasting a lot of time.

Similar Messages

Upgrading Unity Connection from 7.1.5 to 8.5.1 - not working

I am attempting to upgrade our unity connection boxes from 7.1.5 to 8.5.1.
I have legacy MCS 7845H2 - It has 4 disks - 2 mirrors of 72gb disks. 4mb of RAM and 2 X 2.3ghz processors
I have UCS C210 VMWare Hosts.
I have attempted 2 migration methods.
The first method involves - upgrading the existing system and restoring a backup of this to a VM
This fails with a hardware compatablity check.
The second method involves - backup existing systen - build VM at same level (using recommending OVA) - restore data onto VM - upgrade VM
This fails with a restore problem - I have used 'TITAN' ftp, but please note the backup is < 900mb.
The error is
Physical restore failed - could not fork server connection, SQLCODE -25596
Program over.
Restore failed during Unity Connection DB ontape restore operation.
----> BEGIN Standard Error
/opt/cisco/connection/lib/disaster-recovery/database_do_restore.real.py:32: RuntimeWarning: Python C API version mismatch for module iproduct: This Python has API version 1013, module iproduct has version 1012.
import iproduct
gunzip: stdout: Broken pipe
----> END Standard Error
Has anyone out there attempted to upgrade to 8.5.1 - please let me know how you got on.
Any help or ideas appreciated.

Here is the end of the restore log ...
CCM DB is in On-Line status after 6 second.
Restoring the Unity Connection database from ontape archive...
Archive Tape Information
Tape type: Archive Backup Tape
Online version: IBM Informix Dynamic Server Version 10.00.UC9XF
Archive date: Mon Sep 26 19:45:06 2011
User id: root
Terminal id: ?
Archive level: 0
Tape device: STDIO
Tape blocksize (in k): 32
Tape size (in k): 0
Tape number in series: 1
Spaces to restore:1 [rootdbs ]
2 [cuc_er_dbspace ]
3 [dir16 ]
4 [rpt ]
5 [mbx16 ]
6 [dyn ]
7 [mbx ]
8 [dir ]
9 [log ]
10 [cuc_er_sbspace ]
11 [ciscounity_sbspace ]
12 [ciscounity_sbspacetemp ]
Archive Information
IBM Informix Dynamic Server Copyright IBM Corporation 1986, 2008
Initialization Time 06/01/2011 15:51:53
System Page Size 2048
Version 14
Archive CheckPoint Time 09/26/2011 19:45:07
Dbspaces
number flags fchunk nchunks flags owner name
1 40001 1 1 N B informix rootdbs
2 48001 2 1 N SB informix cuc_er_sbspace
3 40001 3 1 N B informix cuc_er_dbspace
4 40001 4 1 N B informix dir16
5 40001 5 1 N B informix rpt
6 42001 6 1 N TB informix temp
7 40001 7 1 N B informix mbx16
8 42001 8 1 N TB informix temp2
9 40001 9 1 N B informix dyn
10 40001 10 1 N B informix mbx
11 40001 11 1 N B informix dir
12 40001 12 1 N B informix log
13 48001 13 1 N SB informix ciscounity_sbspace
14 48001 14 1 N SB informix ciscounity_sbspacetemp
Chunks
chk/dbs offset size free bpages flags pathname
1 1 0 250000 183419 PO-B /var/opt/cisco/connection/db/root_dbspace
2 2 0 915000 176607 POSB /var/opt/cisco/connection/db/cuc_er_sbspace
3 3 0 85000 83217 PO-B /var/opt/cisco/connection/db/cuc_er_dbspace
4 4 0 128000 13824 PO-B /var/opt/cisco/connection/db/dir16_dbs
5 5 0 1024000 744409 PO-B /var/opt/cisco/connection/db/rpt_dbs
6 6 0 512000 511922 PO-B /var/opt/cisco/connection/db/temp_dbs
7 7 0 512000 495816 PO-B /usr/local/cm/db/informix/data/mbx16_dbs
8 8 0 512000 511897 PO-B /var/opt/cisco/connection/db/temp2_dbs
9 9 0 128000 110000 PO-B /var/opt/cisco/connection/db/dyn_dbs
10 10 0 128000 119774 PO-B /usr/local/cm/db/informix/data/mbx_dbs
11 11 0 1024000 362797 PO-B /var/opt/cisco/connection/db/dir_dbs
12 12 0 150000 24947 PO-B /var/opt/cisco/connection/db/log_dbs
13 13 0 10000 518 POSB /var/opt/cisco/connection/db/ciscounity_sbspace
14 14 0 450000 22554 POSB /var/opt/cisco/connection/db/ciscounity_sbspacetemp
Physical restore failed - could not fork server connection, SQLCODE -25596
Program over.
Restore failed during Unity Connection DB ontape restore operation.
----> BEGIN Standard Output
----> END Standard Output
----> BEGIN Standard Error
/opt/cisco/connection/lib/disaster-recovery/database_do_restore.real.py:32: RuntimeWarning: Python C API version mismatch for module iproduct: This Python has API version 1013, module iproduct has version 1012.
import iproduct
gunzip: stdout: Broken pipe
----> END Standard Error

Upgrading Unity Connection Locales

Hi,
I need to update the en-GB Locale installed on a Unity Connection 9.1(2)SU1 server.
I tried installing the new release from the OS Admin web page (after stopping the Mixer and Conversation Manager services) and it failed as it said that the en-GB was already installed. This was true but the installed locale was an earlier version.
I then thought I would delete the existing locale using the CLI command "delete cuc locale en-GB" but the server told me lots of users, call handlers etc. were using it so I was reluctatnt to do so.
What is the proper procedure for upgrading locales?
Can I just delete the old one and install the new one or will this cause issues with mailboxes, call handlers etc.
Thanks

Carlo,
Thanks for responding.
The locale currently installed is uc-locale-en_GB-9.1.0.1-32.cop.sgn
The version I want to upgrade to is uc-locale-en_GB-9.1.2.1-10.cop.sgn
Thanks

Call forward to Unity Connection Fails

I have CUCM7.1 and UCXN 7.0 and have done sip integration. When phones call their voicemail it works fine. When a call to phone is forwarded to vm the main greeting is announced and not the personal greeting. RTMT port monitoring indicates the correct caller and the called is the vm pilot.
Any suggestions?

You may want to double check the configurations on your SIP trunk and SIP profile assigned to the SIP trunk. Refer to this integration guide. I used it and it works like a champ.
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/integration/cucm_sip/guide/cucintcucmsip050.html#wp1094879
HTH.
Regards,
Bill
Please remember to rate helpful posts.

Unity Connection Upgrade Version Switch - Grab a Coffee

Thought I would post some reassurance for anyone upgrading Unity Connection to 8.5. I can't remember other Unity Connection upgrades taking so long on the version switch (utils system switch-version). In my case I was upgrading a Unity Connection cluster from 7.1(3b) to 8.5(1)SU1. The software installation to the inactive partition took approximately two hours (per server), which is what the documentation describes you should expect during a business hours upgrade. What the documentation didn't say was that during the version switch you could expect ~45 minutes of no network response from the server. Anyway, hopefully someone will read this, grab a coffee, and wait (instead of sending out rollback notifications - - as I did!).
HTH
Dom

Just wanted to make sure you had seen this
If you are upgrading during nonbusiness hours: On the publisher server, run the CLI command utils iothrottle disable to speed up the upgrade.
In an effort to prevent upgrades from adversely affecting system performance during business hours, the upgrade process is throttled and may take several hours to complete. If you are upgrading during a maintenance window, you can speed up the upgrade by disabling the throttling. This decreases the time required for the upgrade to complete but adversely affects Connection performance.
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/upgrade/guide/8xcucrug009.html#wp1056720
Cheers!
Rob
"Your life is worth much more than gold."
- Bob Marley

Unity Connection Upgrade 8.5(1)SU1 to 8.5(1)SU5

I am upgrading Unity Connection at 2am on a Unity cluster pair. I would like to do as much as possible ahead of time and only do the reboot to the upgrade partition at 2am. If I do the upgrade now without the reboot, will any changes to users made this afternoon be lost when I reboot at 2am?

Yes, all change between now and then will be lost.
Chris

Regarding SNMP trap on Backup Unity connection failure

Hi,
if backup of Unity connection failed, would a backup failure produce an SNMP trap?
thanks,
Kamran

RTMT has alerts for DRF backup failures... and can be set to trigger emails, but I am not aware of any SNMP Traps generated by DRS Backup failing.
Kind regards,
Craig

CUCM 10.5(1) and Unity Connection 9.1(2) compatibility

I'm planning to use PCD to migrate my MCS Call Manager 8.0(3) cluster to 10.5(1) early next week. I have a standalone 9.1(2) Unity Connection server and I'm reading conflicting information on Cisco's website about their compatibility. One page says they are compatible (http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/cucsccpmtx.html#46452) and another page says I have to upgrade Unity Connection to at least 10.0 (http://tools.cisco.com/ITDIT/vtgsca/VTGServlet). Can someone clarify this for me please?
If Unity Connection 9.1(2) is incompatible with CUCM 10.5(1) and I need to upgrade it, which procedure should I do first - or if they can safely be done at the same time. If I do Call Manager first, will Unity Connection be "dead in the water" until I get it upgraded?
Thanks in advance!
Lisa

That's very good news. Thank you very much, Jaime, for your speedy reply. You are truly an asset to this community!
If I do upgrade CUC at the same time and both CUCM (pub and sub) and CUC (standalone) are at 10.5(1), where would you host PLM? Right now I have ELM co-located on my CUC server. Our voice environment is reasonably small - less than 400 voice mail accounts and roughly 450 phones.
Also, can I upgrade CUC at the same time PCD is migrating my CUCM cluster or should this be done at a different time?
Thank you again!
Lisa

Unity connection 2.1 to 8.6

I am upgrading Unity connection from 2.1 to 8.6 on new servers. The docs are really confuding. Has anyone done this and can tell me what docs to follow. One imolies tha tI have to upgrade to 7, then to 8. How do I get the users and greetings off the existing Unity
Any help would be appreciated

Thanks for quick reply. I looked at 8.6 guides. this one is a litlle better but issue i have is I have new servers that do not support 2.1 and I cannot upgarde existing server so I think I need another server same vintage as 2.1 that will support 7 then drs 2.,1 on temp server, then upgrade then DRS onto new servers from interm serve then upgrade or just use cobaras and load 8,6.2a on new servers..
Risky , time cosuming and complicated . welcome to UC....,
Hope this makes sense

Failure to upgrade Cisco Unity Connection 8.6.2 to 9.1.2

Hi everybody.
Has someone that can help me with follow problem?
I making a Cisco Unity Connection upgrade from version: 8.6.2.20000-76 to 9.1.2.10000-28. But unfortunately we can't sucessfull to make this process.
On the finish of this process, I can see this outup error:
11/23/2013 12:28:55 upgrade_manager.sh|Cleanup exiting - Cached Data: [Vendor= VMware, Inc.
HWModel=VMware
CPUCount=2
CPUType= Intel(R) Xeon(R) CPU E5-2643 0 @ 3.30GHz
CPUSpeed=3300
MEMSize=6144
BIOSVer=PhoenixTechnologiesLTD 6.00 06/22/2012
ObjectId=1.3.6.1.4.1.9.1.1348
OSVersion=UCOS 5.0.0.0-2
SerialNumber= VMware-56 4d e0 4f 4d 85 87 7b-eb 22 0e 52 a7 73 1a 22
VendorOID=1.3.6.1.4.1.674]|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Cleaning up download...|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Cleanup upgrade source area.|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Ejecting DVD (/dev/sda1)|<LVL::Debug>
11/23/2013 12:28:55 upgrade_install.sh|Removing /common/download/9.1.2.10000-28|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Started auditd...|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Started setroubleshoot...|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Changed selinux mode to enforcing|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Cleaning up rpm_archive...|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Removing /common/rpm-archive/9.1.2.10000-28|<LVL::Info>
11/23/2013 12:29:00 upgrade_install.sh|IOWAIT monitor stopped|<LVL::Info>
11/23/2013 12:29:00 upgrade_install.sh|File:/usr/local/bin/base_scripts/upgrade_install.sh:599, Function: main(), Upgrade Failed -- (1)|<LVL::Error>
11/23/2013 12:29:00 upgrade_install.sh|set_upgrade_result: set to 1|<LVL::Debug>
11/23/2013 12:29:00 upgrade_install.sh|is_upgrade_lock_available: Upgrade lock is not available.|<LVL::Debug>
11/23/2013 12:29:00 upgrade_install.sh|is_upgrade_in_progress: Already locked by this process (pid: 14477).|<LVL::Debug>
11/23/2013 12:29:00 upgrade_install.sh|release_upgrade_lock: Releasing lock (pid: 14477)|<LVL::Debug>
Best Regards,
Claudio Costa
A mensagem foi editada por: Claudio Costa

Tks Manish, I just perform a restart on the both nodes on my CUC cluster and after that I did can install this upgrade patch.
Also is very important install the upgrade patch on all servers of the cluster before perform a switch-version on the publisher and then on the others nodes.
Best Regards,
Claudio Costa

Unity Connection 10.5(1)SU1a Publisher/Subscriber failing over

Recently upgraded to Unity Connection version: 10.5.1ES78.11901-78 from 9.1.2ES46.12900-46.
After upgrading we are experiencing an issue whereby the pub continually fails over to the sub without any obvious reason for the fail over. We've experienced this bug before on 9.1.1 which was the reason for the upgrade to 9.1.2. There is no bug case that is established for this issue on v10.5(1)SU1a. Pub is still taking calls in secondary state but obviously the need for stability between the nodes is necessary.
Anyone else experience or know of any issues on this most recently released version?
Thanks

To start with you can check if the replication is setup correctly and if any core dumps are being generated on the servers.
utils dbreplication runtimestate
utils core active list
HTH
Manish

Unity Connection 8.5.1ES16.11900-16 upgrade for Single Inbox with Exchange 2007 ?

Hello friends,
I'm currentely running Unity Connection 8.5.1ES16.11900-16.
I would like to use the single inbox feature with Exchange 2007.
It is in the documentation that we need at least Unity Connection 8.5(1) Service Update 1 (UCSInstall_UCOS_8.5.1.11900-21.sgn.iso).
I downloaded, checked MD5 but when searching on the FTP directory it won't accept it (No valid upgrade options were found). Is this a supported upgrade?
Same happens with the localization file in Portuguese that i need to install: uc-locale-pt_PT-8.5.1.1-16.cop.sng ...
Please can you give me some hints about what I may be doing wrong?
Thank you very much and warm regards,
met

Hi Met,
Hope all is well
I think you are hitting this caveat. Although the numbers don't match exactly I'm
pretty sure you will need to wait for an 8.5.1.12xxx.x ES
If the Connection server is running an engineering special with a full Cisco Unified Communications
Operating System version number between 8.5.1.11001-x and 8.5.1.11899-x, do not upgrade the server
to Connection 8.5(1) SU 1 because the upgrade will fail. Instead, upgrade the server with an ES released
after 8.5(1) SU 1 that has a full Unified Communications OS version number of 8.5.1.12xxx.x or later
to get the SU 1 functionality.
http://www.cisco.com/web/software/282074295/44508/851su1cucrm.pdf
Cheers!
Rob

Unity Connection upgrade from 7.1.3 to 8.5?

We are considering upgrading our unity connection cluster to version 8.5 from our current version 7.1.3 and we are concerned about a few things.
1. Compatibly between UC 8.5 and CUPS 8.02 and CUPC 8.5
2. How to backup and restore current UC7.15 messages and user's VM name and greetings.
Does anyone here in the support community have experience with this version upgrade? Would we be using cobras to back up and restore the messages? Are there any "gotchas" we need to be aware of here?
Please let me know.
Thank you!
Rgds,
Vicky

Hi Vicky,
No worries my friend
We have not done this upgrade and do not have any current plans to do so. I am
always, always, always slow to move along the upgrade path. This may be a bad thing
but it has saved us some great pain as well over the years. Our current versions are;
CUCM - 7.1(3b)su2
CUC - 7.1(3b)su2
We have found these versions to be very stable. I have spent a fair bit of time looking at people's
migrations to 8.5(x) here @ CSC and have not seen or heard of too many horror stories. This is one bug you'll
want to look out for.
CSCtn61453            Bug Details
Applying 8.5.1 software as patch results in corrupted CUC installation.
Symptom:
After fresh installation of 8.5.1 software, we can notice several problem symptoms.
- Connection services and Connection DB does not start
- System cannot be accessed via web page
- Informix error messages for certain CLI commands
Example :- show cuc cluster status
com.informix.asf.IfxASFException: Attempt to connect to database server (ciscounity) failed.
Command failed
Conditions:
It is observed during fresh installation of Unity Connection product when installation was
started with earlier version of software and 8.5.1 software was applied as a patch during the setup process.
Workaround:
First, perform a fresh installation of earlier version of software using the install media. Then after verifying the installation, proceed with the upgrade to 8.5.1 as a separate process.
Status
Open
Severity
2 - severe
Last Modified
In Last 3 Days
Product
Cisco Unity Connection
Technology
1st Found-In
8.5(1)ES1
Best of luck with your changes.
Cheers!
Rob

Hardware checks performed during an Unity Connection upgrade ?

I have Unity Connection 8.0.3 running on an old HP server. (Identified as a HP 7845H2 2333 during the install)
I tried a clean install of Unity Connection 8.6.1 on an identical server. The install failed with the server hardware failing to be recognised.
This is despite the server hardware meeting the requirements of the Unity Connection hardware compatibility check list.
If I try to upgrade the Unity Connection 8.0.3 system to 8.5, will the install program run a compatibility check before loading / upgrading ?
The last thing I want is to successfully install 8.5 but have the system crash when I try to boot the new version.
Thanks
Andy

Hi Andy -
Your server may have been on the compatible hardware list but could require additional hardware - see these specs -
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html#wp771057
Unity Connection 8.6 requires 6Gig RAM and 4-146 Gig hard drives for the 7845 servers. Yes the install program does a compatibility check - if the install does not see the "correct" configuration, it does not show Unity Connection as one of the applications available for install. I would recommend moving to 8.6 if you can, or if you decide on 8.5, refer to Bug Search (Bug Toolkit) and review the caveats. I recently had to applu ES55 to CUC 8.5 service release 2 to fix ViewMail forwarding voice messages from Outlook. If you are planning to install Cisco UCS or an HP/IBM provided virtualized environment as an option, definitely check out 8.6 - it will save you from having to do a refresh upgrade from 8.5 - 8.6!
Sincerely,
Ginger

Licensing for Unity Connection after Upgrade from 8.5 to 9.1.2

I upgraded my Unity connection from 8.5.1 to 9.1.2. ( my CUCM is still on 8.5.1) . I have 200 CUWL-STD ( 2200 DLUs), and 50 CUWL-PRO (850 DLUs) . Now I am working with Cisco to get a license file for Unity Connection and apply that to my ELM. I attached my licensing page for when I was in 8.5.1 . Just want to make sure if I will be getting enough license with that license file, or possibly I need to buy more. Someone told me that if I want to have users with mailbox I need to order more licenses since every user take one CUWL license.
Honestly i do not know how CUWL licensing work regardig to Unity or even CUCM.
Thanks,

Hi,
The following link provides details of licenses usage by diff endpoints on version 9.x
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/uct/9_1_1/CUCM_BK_U0AE00F5_00_uct-admin-guide/CUCM_BK_U0AE00F5_00_uct-admin-guide_chapter_0100.html
HTH
Manish

Upgrade Unity Connection Failing

Similar Messages

Maybe you are looking for