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

[Matthew Loraditch]

Since UCCX still does its license mac based on the hardware properties of the VM you can end up with a new MAC for the NIC and invalid licensing if you  haven’t set this to manual. VMWare generates these macs automatically and they aren’t guaranteed to stay the same as machines are moved, cloned, etc unless you use the manual setting.


Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA
1965 Greenspring Drive
Timonium, MD 21093

direct voice. 443.541.1518
fax.  410.252.9284

Twitter<http://twitter.com/heliontech>  |  Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>  | Website<http://www.heliontechnologies.com/>  |  Email Support<mailto:support at heliontechnologies.com?subject=Technical%20Support%20Request>
Support Phone. 410.252.8830


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Anthony Holloway
Sent: Thursday, November 06, 2014 4:56 PM
To: Heim, Dennis; 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

Dennis,
Could you explain why you mentioned to convert MAC Addresses to manual in this context?

make sure to sure mac addresses to manual prior to copying

On Wed Nov 05 2014 at 6:55:04 AM Heim, Dennis <Dennis.Heim at wwt.com<mailto:Dennis.Heim at wwt.com>> wrote:
If you have the resources available (time and/or money), my preference is to migrate the environment to an offline environment.  If you have the compute resources do it there, or if not some type of Lab a Service (LaaS). Maybe use Veeam to migrate virtual machines, if you are already virtual (make sure to sure mac addresses to manual prior to copying).

Then you need to determine what you time frame is.. can you lose a few days of: cdr’s, historical reports, etc. Migrating VM’s between environment would need to be worked out. However, that allows you to identify any issues, develop a realistic timeframe for each aspect of the upgrade process. Most importantly, it allows a lot of the work to be done not in the middle of the night.

Dennis Heim | Collaboration Solutions Architect
World Wide Technology, Inc. | +1 314-212-1814
[twitter]<https://twitter.com/CollabSensei>
[chat][Phone]<tel:+13142121814>[video]


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Anthony Holloway
Sent: Tuesday, November 04, 2014 11:37 PM
To: Jason Aarons (AM); cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141107/73557196/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3876 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141107/73557196/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1389 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141107/73557196/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1292 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141107/73557196/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1391 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141107/73557196/attachment-0003.png>