I don't think you do have to keep those the same. I've done this a number of times and don't recall paying much attention to maintaining the names or addressing.
That said, you can run the pre-upgrade tool any time you like. I would run an export, and then build a VM with the intended UCCX version - then restore to that. That will prove your process is OK (i.e. both import/export work) and you can prove to yourself that you don't need to have the same name/IP.
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
Yes, you can change the hostname and ip address of the UCCX while performing Windows to Linux upgrade, but care must be taken that all the clients (CAD\CSD\CDA\HRC\Editor) needs to be reinstalled frreshly, as they wont go through auto upgrade.
I'm also going through the same process (installing new CUCM and UCCX clusters in parallel to the existing production clusters). Here is my setup:
CUCM - 6.1
UCCX - 5.0(2) [2 nodes]
CUCM - 8.6
UCCX - going to be 8.5 eventually, but for using PUT tool, I'm installing 8.0(2) first with a new hostname/IP address [going to be 2 nodes]
So will the PUT tool let me keep the new hostname/IP address for new UCCX server? Also what will happen to the HA node (which came as part of PUT restore)? Can I just delete it after the PUT succeeds and then add the new HA node with new name/IP address and install 8.x UCCX?
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...