Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1
I think that's how it use to work a few versions back, but I don't think that's accurate anymore. UCCX uses the license mac, which is dynamically created based on a few settings of the server as you can read here: http://docwiki.cisco.com/wiki/Licensing_Model_for_Virtualized_UC_Applications If the MAC Address of the network adapter were to be in play at all, then the Answer File Generator could not predict your license mac. On Fri Nov 07 2014 at 8:47:07 AM Matthew Loraditch mloradi...@heliontechnologies.com wrote: 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-RS, 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 supp...@heliontechnologies.com?subject=Technical%20Support%20Request Support Phone. 410.252.8830 *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf Of *Anthony Holloway *Sent:* Thursday, November 06, 2014 4:56 PM *To:* Heim, Dennis; Jason Aarons (AM); cisco-voip@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.h...@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 [image: twitter] https://twitter.com/CollabSensei [image: chat][image: Phone] +13142121814[image: video] *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf Of *Anthony Holloway *Sent:* Tuesday, November 04, 2014 11:37 PM *To:* Jason Aarons (AM); cisco-voip@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.aar...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1
You are right… I’m mixing products up… Attendant Console does still rely on the VM NIC’s mac and I have dealt with that issue recently… Now I’m also wondering why Dennis is suggesting this.. only thing I can think of is avoid ARP issues. Matthew G. Loraditch – CCNP-Voice, CCNA-RS, CCDA 1965 Greenspring Drive Timonium, MD 21093 direct voice. 443.541.1518 fax. 410.252.9284 Twitterhttp://twitter.com/heliontech | Facebookhttp://www.facebook.com/#!/pages/Helion/252157915296 | Websitehttp://www.heliontechnologies.com/ | Email Supportmailto:supp...@heliontechnologies.com?subject=Technical%20Support%20Request Support Phone. 410.252.8830 From: Anthony Holloway [mailto:avholloway+cisco-v...@gmail.com] Sent: Friday, November 07, 2014 9:59 AM To: Matthew Loraditch; Heim, Dennis; Jason Aarons (AM); cisco-voip@puck.nether.net Subject: Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1 I think that's how it use to work a few versions back, but I don't think that's accurate anymore. UCCX uses the license mac, which is dynamically created based on a few settings of the server as you can read here: http://docwiki.cisco.com/wiki/Licensing_Model_for_Virtualized_UC_Applications If the MAC Address of the network adapter were to be in play at all, then the Answer File Generator could not predict your license mac. On Fri Nov 07 2014 at 8:47:07 AM Matthew Loraditch mloradi...@heliontechnologies.commailto:mloradi...@heliontechnologies.com wrote: 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-RS, CCDA 1965 Greenspring Drive Timonium, MD 21093 direct voice. 443.541.1518 fax. 410.252.9284 Twitterhttp://twitter.com/heliontech | Facebookhttp://www.facebook.com/#!/pages/Helion/252157915296 | Websitehttp://www.heliontechnologies.com/ | Email Supportmailto:supp...@heliontechnologies.com?subject=Technical%20Support%20Request Support Phone. 410.252.8830 From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.netmailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Anthony Holloway Sent: Thursday, November 06, 2014 4:56 PM To: Heim, Dennis; Jason Aarons (AM); cisco-voip@puck.nether.netmailto:cisco-voip@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.h...@wwt.commailto:dennis.h...@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-boun...@puck.nether.netmailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Anthony Holloway Sent: Tuesday, November 04, 2014 11:37 PM To: Jason Aarons (AM); cisco-voip@puck.nether.netmailto:cisco-voip@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
Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1
Thanks Brian, you are probably right. To be clear though: that's a standalone ELM/PLM only, and not Co-Resident. Important: For a standalone installation of Cisco Prime License Manager, only static MAC addresses are supported on the virtual machine. Using the vSphere client, select Edit virtual machine settings Network adapter 1 MAC Address. Select the Manual option and enter a unique MAC address. Source: PLM User Guide http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/plm/10_5_1/userguide/CPLM_BK_UD1156AD_00_user-guide-rel-1051/CPLM_BK_UD1156AD_00_user-guide-rel-1051_chapter_01.html#CPLM_TK_I7706464_00 On Fri Nov 07 2014 at 12:02:51 PM Brian Meade bmead...@vt.edu wrote: The MAC address is used for ELM/PLM. That may be where the confusion is. On Fri, Nov 7, 2014 at 9:58 AM, Anthony Holloway avholloway+cisco-v...@gmail.com wrote: I think that's how it use to work a few versions back, but I don't think that's accurate anymore. UCCX uses the license mac, which is dynamically created based on a few settings of the server as you can read here: http://docwiki.cisco.com/wiki/Licensing_Model_for_Virtualized_UC_Applications If the MAC Address of the network adapter were to be in play at all, then the Answer File Generator could not predict your license mac. On Fri Nov 07 2014 at 8:47:07 AM Matthew Loraditch mloradi...@heliontechnologies.com wrote: 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-RS, 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 supp...@heliontechnologies.com?subject=Technical%20Support%20Request Support Phone. 410.252.8830 *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf Of *Anthony Holloway *Sent:* Thursday, November 06, 2014 4:56 PM *To:* Heim, Dennis; Jason Aarons (AM); cisco-voip@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.h...@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 https://twitter.com/CollabSensei +13142121814 *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf Of *Anthony Holloway *Sent:* Tuesday, November 04, 2014 11:37 PM *To:* Jason Aarons (AM); cisco-voip@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
Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1
Sounds like Jason is doing HA. Anthony I didn't see any sub listed in your tasks, so I think that accounts for some portion of the difference. On Nov 5, 2014 11:12 PM, Jason Aarons (AM) jason.aar...@dimensiondata.com wrote: The funny part is that this is the replicated offline environment. Once we test scripts, databases, etc then production gets migrated J *From:* Anthony Holloway [mailto:avholloway+cisco-v...@gmail.com] *Sent:* Wednesday, November 5, 2014 10:47 PM *To:* Heim, Dennis; Jason Aarons (AM); cisco-voip@puck.nether.net *Subject:* Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1 Dennis, You're on to something here, however, resources such as time and money are not always in abundance. Sometimes, you're asked to do things as quickly and as cheaply as possible. And by sometimes, I mean most of the time. On Wed Nov 05 2014 at 6:55:04 AM Heim, Dennis dennis.h...@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 [image: twitter] https://twitter.com/CollabSensei [image: chat][image: Phone] +13142121814[image: video] *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf Of *Anthony Holloway *Sent:* Tuesday, November 04, 2014 11:37 PM *To:* Jason Aarons (AM); cisco-voip@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.aar...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip itevomcid ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1
The last time I tried this, It was a weekend long deal due to the application replication not coming online in an HA environment. Took TAC over 12 hours to figure out that the passwords weren't synced in all tables and had to root and run sql updates to resolve it. Customer had changed passwords previously and when we did the upgrade, it came out to show it's head. For whatever reason, the application was replicating before the upgrade attempt, but after we booted up on SU4, platform replication was fine, just application was not. Was a fun weekend. We haven't scheduled a time to try again, waiting on the customer for it. On Thu, Nov 6, 2014 at 4:58 AM, Justin Steinberg jsteinb...@gmail.com wrote: Sounds like Jason is doing HA. Anthony I didn't see any sub listed in your tasks, so I think that accounts for some portion of the difference. On Nov 5, 2014 11:12 PM, Jason Aarons (AM) jason.aar...@dimensiondata.com wrote: The funny part is that this is the replicated offline environment. Once we test scripts, databases, etc then production gets migrated J *From:* Anthony Holloway [mailto:avholloway+cisco-v...@gmail.com] *Sent:* Wednesday, November 5, 2014 10:47 PM *To:* Heim, Dennis; Jason Aarons (AM); cisco-voip@puck.nether.net *Subject:* Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1 Dennis, You're on to something here, however, resources such as time and money are not always in abundance. Sometimes, you're asked to do things as quickly and as cheaply as possible. And by sometimes, I mean most of the time. On Wed Nov 05 2014 at 6:55:04 AM Heim, Dennis dennis.h...@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 [image: twitter] https://twitter.com/CollabSensei [image: chat][image: Phone] +13142121814[image: video] *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf Of *Anthony Holloway *Sent:* Tuesday, November 04, 2014 11:37 PM *To:* Jason Aarons (AM); cisco-voip@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.aar...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip itevomcid ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
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.h...@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 [image: twitter] https://twitter.com/CollabSensei [image: chat][image: Phone] +13142121814[image: video] *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf Of *Anthony Holloway *Sent:* Tuesday, November 04, 2014 11:37 PM *To:* Jason Aarons (AM); cisco-voip@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.aar...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
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 jsteinb...@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)SU445 - 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-v...@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.aar...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1
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)SU445 - 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-v...@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.aar...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1
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-v...@gmail.com] Sent: Wednesday, November 5, 2014 9:55 PM To: Justin Steinberg Cc: Jason Aarons (AM); cisco-voip@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 jsteinb...@gmail.commailto:jsteinb...@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)SU445 - 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-v...@gmail.commailto:avholloway+cisco-v...@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.aar...@dimensiondata.commailto:jason.aar...@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@puck.nether.netmailto:cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip itevomcid ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1
At 10hours I haven’t gotten to 10.5.1SU1 either….. From: Anthony Holloway [mailto:avholloway+cisco-v...@gmail.com] Sent: Wednesday, November 5, 2014 9:55 PM To: Justin Steinberg Cc: Jason Aarons (AM); cisco-voip@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 jsteinb...@gmail.commailto:jsteinb...@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)SU445 - 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-v...@gmail.commailto:avholloway+cisco-v...@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.aar...@dimensiondata.commailto:jason.aar...@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@puck.nether.netmailto:cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip itevomcid ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1
That's painful to hear. Is this typical and expected or are you hitting the worst case scenario? On Wed Nov 05 2014 at 9:24:33 PM Jason Aarons (AM) jason.aar...@dimensiondata.com wrote: At 10hours I haven’t gotten to 10.5.1SU1 either….. *From:* Anthony Holloway [mailto:avholloway+cisco-v...@gmail.com] *Sent:* Wednesday, November 5, 2014 9:55 PM *To:* Justin Steinberg *Cc:* Jason Aarons (AM); cisco-voip@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 jsteinb...@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)SU445 - 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-v...@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.aar...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip itevomcid ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1
Dennis, You're on to something here, however, resources such as time and money are not always in abundance. Sometimes, you're asked to do things as quickly and as cheaply as possible. And by sometimes, I mean most of the time. On Wed Nov 05 2014 at 6:55:04 AM Heim, Dennis dennis.h...@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 [image: twitter] https://twitter.com/CollabSensei [image: chat][image: Phone] +13142121814[image: video] *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf Of *Anthony Holloway *Sent:* Tuesday, November 04, 2014 11:37 PM *To:* Jason Aarons (AM); cisco-voip@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.aar...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1
The funny part is that this is the replicated offline environment. Once we test scripts, databases, etc then production gets migrated ☺ From: Anthony Holloway [mailto:avholloway+cisco-v...@gmail.com] Sent: Wednesday, November 5, 2014 10:47 PM To: Heim, Dennis; Jason Aarons (AM); cisco-voip@puck.nether.net Subject: Re: [cisco-voip] UCCX 8.5.1sr3 to sr4 to Refresh Upgrade 10.5.1 Dennis, You're on to something here, however, resources such as time and money are not always in abundance. Sometimes, you're asked to do things as quickly and as cheaply as possible. And by sometimes, I mean most of the time. On Wed Nov 05 2014 at 6:55:04 AM Heim, Dennis dennis.h...@wwt.commailto:dennis.h...@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-boun...@puck.nether.netmailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Anthony Holloway Sent: Tuesday, November 04, 2014 11:37 PM To: Jason Aarons (AM); cisco-voip@puck.nether.netmailto:cisco-voip@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.aar...@dimensiondata.commailto:jason.aar...@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@puck.nether.netmailto:cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip itevomcid ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
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.aar...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
