[cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1

[Jason Aarons (AM)]

More like 8 hour (I’m at 10+ hours and it’s still not done), got to add in TAC for CSCup83263 for root

From: Anthony Holloway [mailto:avholloway+cisco-voip at gmail.com]
Sent: Wednesday, November 5, 2014 9:55 PM
To: Justin Steinberg
Cc: Jason Aarons (AM); cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1



Thanks for taking the time to put some numbers next to these tasks.  It looks like this really is a ~5 hour ordeal.

Jason, care to share a recap of how it went?

On Wed Nov 05 2014 at 8:08:02 PM Justin Steinberg <jsteinberg at gmail.com<mailto:jsteinberg at gmail.com>> wrote:
i'll take a stab at time estimates.  that being said, i have heard of switch-versions taking much longer or sitting at SELINUX loading for longer than the typical 15-20 minutes.

checking for existing snapshots before doing anything is really important.   if there are snapshots that someone left on their from the past, it will most likely completely hose the upgrade times and make the system extremely slow.

1. Upload ISOs to DataStore
2. Disable IO Throttle on Publisher
3. Mount 8.5(1)SU4 ISO
4. Upgrade Publisher to 8.5(1)SU4    45 - 60 minutes
5. Switch Version to 8.5(1)SU4 60 minutes (includes switch version process, reboot, SELINUX loading, services startup)
6. Patch Publisher with RU COP 5 minutes
7. Shutdown Publisher 10 minutes
8. Modify VM Settings: RAM from 4GB to 8GB
9. Power On Publisher 15 minutes
10. Mount 10.5(1)SU1 ISO
11. Upgrade Publisher to 10.5(1)SU1  45-60 minutes
12. Switch Version to 10.5(1)SU1 60 minutes (includes switch version process, reboot, SELINUX loading, services startup)
13. Rerun the CAD Client Configuration Tool (10 minutes)

On Wed, Nov 5, 2014 at 12:36 AM, Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>> wrote:
Wow.  Are you going MCS to UCS too?  If not, I'm doing that exact upgrade very soon and no documentation I have reviewed indicated how long upgrades would take, let alone 5 hours.  Right now my plan has a time budget of 3 hours for the same, which does not include moving ISOs to the datastore (I like doing local upgrades) nor upgrading clients.

Which portion is taking 5 hours?  Could you break it down by task for us?  E.g., L2 to SU4, Switch Version to SU4, RU COP, RU to 10.5, Switch Version to 10.5.

Did you disable IO Throttling first?

Based on my research here are the summary steps to this exact upgrade (sans client upgrades):

1. Upload ISOs to DataStore
2. Disable IO Throttle on Publisher
3. Mount 8.5(1)SU4 ISO
4. Upgrade Publisher to 8.5(1)SU4
5. Switch Version to 8.5(1)SU4
6. Patch Publisher with RU COP
7. Shutdown Publisher
8. Modify VM Settings: RAM from 4GB to 8GB
9. Power On Publisher
10. Mount 10.5(1)SU1 ISO
11. Upgrade Publisher to 10.5(1)SU1
12. Switch Version to 10.5(1)SU1

On Tue Nov 04 2014 at 11:04:24 PM Jason Aarons (AM) <jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>> wrote:
One UCCX node in ha pair 5 hours doing upgrades...it would be more enjoyable watching paint dry...there has got to be a better method in the future for L2 upgrades than this..


Sent from my Verizon Wireless 4G LTE Smartphone
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip



itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141106/445593b3/attachment.html>