Currently in the process of planning out my upgrade from 8.5.1 SU3 to 8.5.1 SU6 on both Unity and CuCM.
In the CUCM side
1 publisher, 3 subs
Cisco Unity Side
1 publisher, 1 sub
I'm trying to plan my timeline, but getting mixed returns on how much time I should plan for each upgrade, has anyone who recently went to SU6 have a approx time per node?
In reading the documentation there appears to be a utils iothrottle enable command which will speed the upgrade up (we are upgrading on offhours).
It all comes down to what hardware this is running on, which you omitted. Upgrading Pub can take ~2 hours, subs (you can do them all at the same time if you choose) ~1.5 hour. UCXN 1.5 hours each and can run along CUCM upgrade.
Sorry, we are on MCS 7825-I4's (all 6) with:
|CPU Type||Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz|
I thought best practice for upgrades was to get the Pub first, and do the subs 15 minutes apart?
My estimates should apply, where did you see anything about 15 min apart? Probably would not hurt, but not required.
HTH, please rate all useful posts!
Just thought I would add this reference to the great tips from my buddy Chris (+5)
You can upgrade the Subs in Parallel as Chris noted which will save significant down time
When you upgrade a cluster that is running a supported version of Cisco Unified Communications Manager 6.x to Cisco Unified Communications Manager 8.5(1), begin upgrading the first node first. You can begin upgrading subsequent nodes in parallel after the first node reaches a specified point in the upgrade.
During the upgrade of the first node, view the installation log, install_log_
You can also use the CLI to search for the relevant information in the install log by following this procedure:
Step 1 List the install logs; for example:
file list install install_* date
dir count = 0, file count = 3
Step 2 Search the most recent install log for the string PRODUCT_VERSION; for example:
file search install install_log_2008-10-14.09.31.06.log PRODUCT_VERSION
Searching path: /var/log/install/install_log_2008-10-14.09.31.06.log
Searching file: /var/log/install/install_log_2008-10-14.09.31.06.log
10/14/2008 09:52:14 upgrade_os.sh|PRODUCT_VERSION is 22.214.171.124000-97|<:INFO>
Step 3 When the file search command finds the PRODUCT_VERSION string in the install log, you can start the upgrade of the subsequent nodes.
When you are ready to activate the new version, you must activate the new software on the first node before activating it on all other nodes.
"When it comes to luck you make your own "