I`m due to upgrade a CUCM 6.X server to 6.1. and I`m querying a procedure
Current set up
Publisher - Running as Glass House- No CM Services, No TFTP etc
2x TFTP Servers
I know we upgrade to an inactive partition so not to effect production however due to various reasons I would like to do the following
Pull Disks on Pub to ensure we have a physical roll back option- test each disk in turn
Change Pub to allow the test phones to register to it
Upgrade Pub on Inactive Partition
Allow test phones to register to Pub - make test calls, access Admin , EM testing etc
As the phones will reboot and so query the TFTP`s which I have not upgraded to the newer SW, it will then register to the Pub which is now on the newer SW- will this work or will it be a conflict between the Pub being on the newer SW and the TFTP being on the older version ?
or should I manually reconfigure the test phones only to use one of the TFTP Servers and the upgrade the same TFTP after I`ve done the Pub and reboot both- PUB and TFTP on the newer SW
Once I`m happy we will then upgrade the other TFTP followed by the Subs
the thing is that even if it's successful you'll need to switch back before upgrading the SUBs, if you leave PUB on 6.1(2) for testing and the SUBs in 6.1(1) and then try to upgrade you won't be able to do so
that's why the instructions clearly say to install the upgrade in all servers at a time, then switch one at a time
the reason I`m asking if that we had a failure when reverting back to the lower SW in our test lab so the idea is to the test the roll back on the Pub only first in case the lab and production Cluster are any way differetn though they are on the SW level. Would not the switch back to the Pub to the lower SW so the cluster is now all on the same Verison and then upgrade the Subs- once all done then switch one by one as per doc?- would this not work
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...