We are working on upgrading our UC infrastructure to 9.X on UCS. We currenlty have legacy MCS appliances and are running 7.1(3)b for cccm and 7.1(2) for connection. Everything I have read about upgrading connection specifically states version 7.1(3) as the version to get to for upgrading. I was planning on getting both ccm and connection to 7.1(5) and then starting the upgrade.
Since the MCS servers aren't supported for 9.X we are expecting that we will have to install both connection and ccm on the the ucs @ and get it the to exact version that the MCS servers are running..do a DRS restore to the new servers. Once the new servers are running 7.X with the data imported, perform an upgrade to 9.X. I have also read that it would be better to get an DRS from the new 9.X server and then do a fresh install and restore, is this true?
Also when we are building the 7.X server on the UCS can I use the ova for 9.X? I know I can install this with the same hostname and ip (in a blackhole vlan), but what is the best way to deal with dns and ntp requirements?
Should I stick with 7.1(3) or can I go to 7.1(5) for both ccm and connection prior to upgrade? The main reason I am considering the 7.1(5) is that we have 8945 phones that waiting to be deployed, they would be supported under that version and could be deployed now as opposed to after the full upgrade process. We have UCCX which in a different "beast".
Thanks and I appreicate any advise/recomendations...
Thanks for the information...we are a partner and I will be using those resources for assistance . The document doesn't really cover much about Untiy Connection, since this is "live" data, is the process still the same? We have several items to address before the actual upgrade, ie fixed MOH, attendant console features....etc. We were wanting to start with Connection since it has no dependency on CCM version. I have looked through the drive for 9 and it appears that we can upgrade ccm to 7.1(5) (to utilize the 8945's) then do the jump upgrade to 9.X. We currently have 3 servers in our cluster, I assume it would be best acutally build out the entire cluster or do we only need to worry about getting the publisher in the lab enviroment?
Thanks again for your responses, hopefully someone with Unity Connection experience will chime in as well.
One other question for you, if you are integrated with AD via LDAP, do you have to continue to have this connectivity in the "sandbox" during your migration of data? I would expect we could NAT the sandbox from the rest of the network and stil have connectivity to DNS and other servers.
The D29 jump upgrade doc explains which OVA to use, the necessary and mandatory steps (including the last DRS), and requirements for jump upgrade (including a whole recreation of the production environment in the lab for this purpose).
As for CUC, the CUC upgrade guides are what you need to review, basically, two options, either you just use COBRAS to migrate the info from one version to the other, or upgrade to (at least) 8.X release, when virtualization support started, to then DRS from MCS to UCS.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...