Re: [cisco-voip] UCCX Virtual 9.0(2) to 10.6(1) Upgrade
I’ve done the ova modifications post upgrades for Cm/UCCX. From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Andrew Grech Sent: Thursday, February 19, 2015 11:43 PM To: Cisco VoIP Group Subject: [cisco-voip] UCCX Virtual 9.0(2) to 10.6(1) Upgrade Hi, I'm preparing an upgrade of uccx 9.0(2) to 10.6(1) When would be be the best time to adjust the OVA file? I need to change the RAM and Guest OS to RHEL6 (although Guest OS change step is not documented) The guide says It is highly recommended that you gracefully shut down the UCCX VMs, and update the memory allocation to the new values after you upgrade to UCCX Version 10.0. If memory allocation for the VM is left unchanged after the UCCX is upgraded to Version 10.0, this warning message displays: Does this mean before the switch version? Cheers Andrew ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UCCX Virtual 9.0(2) to 10.6(1) Upgrade
Thanks Dan I just checked the OVAs and I do need to change the vNIC I remember doing this for another product but it wasn't documented unlike ccx unless I'm missing it. My other concern is my signed certificates but I have access to the CA so its not a game changer if I need to reissue. I have thought about running sandbox servers up in my lab loading a drs then upgrading. I could then disconnect the NICs of the current vms and move the sandbox servers into production. This would provide an easy rollback. Anyone have experience with this? Note I won't be cloning the sandbox servers from production but rather running them up from scratch. On 20/02/2015 10:28 PM, Daniel Pagan dpa...@fidelus.com wrote: Based on the UCCX tech note I found, I’d say the shutdown and final modifications should be made after a full switch version is performed and you’re running the upgrade release on your active partitions. This differs from the official word from Cisco on CUCM, which is to adjust the virtual machine resources to match the OVA template specifications before the upgrade is performed. However, also according to official documentation, changing the vNIC to VMXNET3 through PowerCLI should be done post-upgrade. Personally I’ve seen all these modifications being performed after the upgrade is completed and version switched with no negative impact whatsoever, but official documentation and TAC’s stance says the virtual machine settings should be modified first, followed by the upgrade, then wrapped up with the vNIC change to VMXNET3. I can provide documentation if needed - it seems that UCCX documentation differs. Also don’t forget to set the OS security settings to “permissive” if you wish to auto-update the VMware Tools on the virtual machines. - Dan From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Andrew Grech Sent: Thursday, February 19, 2015 11:43 PM To: Cisco VoIP Group Subject: [cisco-voip] UCCX Virtual 9.0(2) to 10.6(1) Upgrade Hi, I'm preparing an upgrade of uccx 9.0(2) to 10.6(1) When would be be the best time to adjust the OVA file? I need to change the RAM and Guest OS to RHEL6 (although Guest OS change step is not documented) The guide says It is highly recommended that you gracefully shut down the UCCX VMs, and update the memory allocation to the new values after you upgrade to UCCX Version 10.0. If memory allocation for the VM is left unchanged after the UCCX is upgraded to Version 10.0, this warning message displays: Does this mean before the switch version? Cheers Andrew ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UCCX Virtual 9.0(2) to 10.6(1) Upgrade
I opened a PDI ticket on this, because CUCM and CUC differ on when you should change the VM settings. Here's what I wrote to PDI: I am planning an upgrade from 8.6(2a)SU2 to 10.5(1)SU1. I am looking at the pre-upgrade tasks of this document: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100.html It states that I need to modify the VM guest settings, to include the OS version, before I do the upgrade. However, the CUC upgrade guide (which should largely be the same as CUCM considering the shared ISO image), states to do the same but Post-Upgrade, not before. That guide is here: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrugx/10xcucrug010.html#16383 I'm wondering if it really matters when I change these settings on the VM: pre or post upgrade, just as long as I do it before VMTools is updated. Or might there be a problem with the documentation? And their reply was simply, follow the documentation, because each team tests their upgrades differently, and how they documented it is how it worked for them. That also means that for apps like UCCX, if you don't see anywhere, where it says to change the OS from 32 to 64 bit, then you shouldn't. You'd be making an assumption that the UCCX team moved their OS version, just because the CUCM team did. Lastly, for RAM and CPU increases, I did those pre-upgrade, with the thoughts that: A) It's not unsupported to have more resources available to the VM, and B) It might make the upgrade process faster. Those are my thoughts on the subject. On Fri Feb 20 2015 at 7:10:57 AM Andrew Grech agrec...@gmail.com wrote: Thanks Dan I just checked the OVAs and I do need to change the vNIC I remember doing this for another product but it wasn't documented unlike ccx unless I'm missing it. My other concern is my signed certificates but I have access to the CA so its not a game changer if I need to reissue. I have thought about running sandbox servers up in my lab loading a drs then upgrading. I could then disconnect the NICs of the current vms and move the sandbox servers into production. This would provide an easy rollback. Anyone have experience with this? Note I won't be cloning the sandbox servers from production but rather running them up from scratch. On 20/02/2015 10:28 PM, Daniel Pagan dpa...@fidelus.com wrote: Based on the UCCX tech note I found, I’d say the shutdown and final modifications should be made after a full switch version is performed and you’re running the upgrade release on your active partitions. This differs from the official word from Cisco on CUCM, which is to adjust the virtual machine resources to match the OVA template specifications before the upgrade is performed. However, also according to official documentation, changing the vNIC to VMXNET3 through PowerCLI should be done post-upgrade. Personally I’ve seen all these modifications being performed after the upgrade is completed and version switched with no negative impact whatsoever, but official documentation and TAC’s stance says the virtual machine settings should be modified first, followed by the upgrade, then wrapped up with the vNIC change to VMXNET3. I can provide documentation if needed - it seems that UCCX documentation differs. Also don’t forget to set the OS security settings to “permissive” if you wish to auto-update the VMware Tools on the virtual machines. - Dan From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Andrew Grech Sent: Thursday, February 19, 2015 11:43 PM To: Cisco VoIP Group Subject: [cisco-voip] UCCX Virtual 9.0(2) to 10.6(1) Upgrade Hi, I'm preparing an upgrade of uccx 9.0(2) to 10.6(1) When would be be the best time to adjust the OVA file? I need to change the RAM and Guest OS to RHEL6 (although Guest OS change step is not documented) The guide says It is highly recommended that you gracefully shut down the UCCX VMs, and update the memory allocation to the new values after you upgrade to UCCX Version 10.0. If memory allocation for the VM is left unchanged after the UCCX is upgraded to Version 10.0, this warning message displays: Does this mean before the switch version? Cheers Andrew ___ 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 Virtual 9.0(2) to 10.6(1) Upgrade
Hi All, We really should have this better documented as we don’t follow CUCM 1:1 as Anthony pointed out in the areas of underlying VOS versions and testing. I’ve field CSCut04158 for the doc-wiki to be updated. It should be visible soon. Thank you, Ryan LaFountain Unified Contact Center Cisco Services Direct: +1 919 392 9898 Hours: M - F 9:00am - 5:00pm Eastern Time From: Anthony Holloway Date: Friday, February 20, 2015 at 8:49 AM To: Andrew Grech, Daniel Pagan, Cisco VoIP Group Subject: Re: [cisco-voip] UCCX Virtual 9.0(2) to 10.6(1) Upgrade I opened a PDI ticket on this, because CUCM and CUC differ on when you should change the VM settings. Here's what I wrote to PDI: I am planning an upgrade from 8.6(2a)SU2 to 10.5(1)SU1. I am looking at the pre-upgrade tasks of this document: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100.html It states that I need to modify the VM guest settings, to include the OS version, before I do the upgrade. However, the CUC upgrade guide (which should largely be the same as CUCM considering the shared ISO image), states to do the same but Post-Upgrade, not before. That guide is here: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrugx/10xcucrug010.html#16383 I'm wondering if it really matters when I change these settings on the VM: pre or post upgrade, just as long as I do it before VMTools is updated. Or might there be a problem with the documentation? And their reply was simply, follow the documentation, because each team tests their upgrades differently, and how they documented it is how it worked for them. That also means that for apps like UCCX, if you don't see anywhere, where it says to change the OS from 32 to 64 bit, then you shouldn't. You'd be making an assumption that the UCCX team moved their OS version, just because the CUCM team did. Lastly, for RAM and CPU increases, I did those pre-upgrade, with the thoughts that: A) It's not unsupported to have more resources available to the VM, and B) It might make the upgrade process faster. Those are my thoughts on the subject. On Fri Feb 20 2015 at 7:10:57 AM Andrew Grech agrec...@gmail.commailto:agrec...@gmail.com wrote: Thanks Dan I just checked the OVAs and I do need to change the vNIC I remember doing this for another product but it wasn't documented unlike ccx unless I'm missing it. My other concern is my signed certificates but I have access to the CA so its not a game changer if I need to reissue. I have thought about running sandbox servers up in my lab loading a drs then upgrading. I could then disconnect the NICs of the current vms and move the sandbox servers into production. This would provide an easy rollback. Anyone have experience with this? Note I won't be cloning the sandbox servers from production but rather running them up from scratch. On 20/02/2015 10:28 PM, Daniel Pagan dpa...@fidelus.commailto:dpa...@fidelus.com wrote: Based on the UCCX tech note I found, I’d say the shutdown and final modifications should be made after a full switch version is performed and you’re running the upgrade release on your active partitions. This differs from the official word from Cisco on CUCM, which is to adjust the virtual machine resources to match the OVA template specifications before the upgrade is performed. However, also according to official documentation, changing the vNIC to VMXNET3 through PowerCLI should be done post-upgrade. Personally I’ve seen all these modifications being performed after the upgrade is completed and version switched with no negative impact whatsoever, but official documentation and TAC’s stance says the virtual machine settings should be modified first, followed by the upgrade, then wrapped up with the vNIC change to VMXNET3. I can provide documentation if needed - it seems that UCCX documentation differs. Also don’t forget to set the OS security settings to “permissive” if you wish to auto-update the VMware Tools on the virtual machines. - Dan From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.netmailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Andrew Grech Sent: Thursday, February 19, 2015 11:43 PM To: Cisco VoIP Group Subject: [cisco-voip] UCCX Virtual 9.0(2) to 10.6(1) Upgrade Hi, I'm preparing an upgrade of uccx 9.0(2) to 10.6(1) When would be be the best time to adjust the OVA file? I need to change the RAM and Guest OS to RHEL6 (although Guest OS change step is not documented) The guide says It is highly recommended that you gracefully shut down the UCCX VMs, and update the memory allocation to the new values after you upgrade to UCCX Version 10.0. If memory allocation for the VM is left unchanged after the UCCX is upgraded to Version 10.0, this warning message displays: Does this mean before the switch version? Cheers
Re: [cisco-voip] UCCX Virtual 9.0(2) to 10.6(1) Upgrade
I just went through a CUC 8.5(1)su7 to 10.5(2) upgrade last night. I tried to upgrade before the vRAM increase from 4 GB to 6GB and the upgrade failed about 5 minutes in due to 'unsupported hardware'. Shutdown the VMs, increased the vRAM to 6GB, booted it back up and the upgrade was fine. On Fri, Feb 20, 2015 at 10:29 AM, Ryan LaFountain (rlafount) rlafo...@cisco.com wrote: Hi All, We really should have this better documented as we don’t follow CUCM 1:1 as Anthony pointed out in the areas of underlying VOS versions and testing. I’ve field CSCut04158 for the doc-wiki to be updated. It should be visible soon. Thank you, Ryan LaFountain Unified Contact Center Cisco Services Direct: +1 919 392 9898 Hours: M - F 9:00am - 5:00pm Eastern Time From: Anthony Holloway Date: Friday, February 20, 2015 at 8:49 AM To: Andrew Grech, Daniel Pagan, Cisco VoIP Group Subject: Re: [cisco-voip] UCCX Virtual 9.0(2) to 10.6(1) Upgrade I opened a PDI ticket on this, because CUCM and CUC differ on when you should change the VM settings. Here's what I wrote to PDI: I am planning an upgrade from 8.6(2a)SU2 to 10.5(1)SU1. I am looking at the pre-upgrade tasks of this document: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100.html It states that I need to modify the VM guest settings, to include the OS version, before I do the upgrade. However, the CUC upgrade guide (which should largely be the same as CUCM considering the shared ISO image), states to do the same but Post-Upgrade, not before. That guide is here: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrugx/10xcucrug010.html#16383 I'm wondering if it really matters when I change these settings on the VM: pre or post upgrade, just as long as I do it before VMTools is updated. Or might there be a problem with the documentation? And their reply was simply, follow the documentation, because each team tests their upgrades differently, and how they documented it is how it worked for them. That also means that for apps like UCCX, if you don't see anywhere, where it says to change the OS from 32 to 64 bit, then you shouldn't. You'd be making an assumption that the UCCX team moved their OS version, just because the CUCM team did. Lastly, for RAM and CPU increases, I did those pre-upgrade, with the thoughts that: A) It's not unsupported to have more resources available to the VM, and B) It might make the upgrade process faster. Those are my thoughts on the subject. On Fri Feb 20 2015 at 7:10:57 AM Andrew Grech agrec...@gmail.com wrote: Thanks Dan I just checked the OVAs and I do need to change the vNIC I remember doing this for another product but it wasn't documented unlike ccx unless I'm missing it. My other concern is my signed certificates but I have access to the CA so its not a game changer if I need to reissue. I have thought about running sandbox servers up in my lab loading a drs then upgrading. I could then disconnect the NICs of the current vms and move the sandbox servers into production. This would provide an easy rollback. Anyone have experience with this? Note I won't be cloning the sandbox servers from production but rather running them up from scratch. On 20/02/2015 10:28 PM, Daniel Pagan dpa...@fidelus.com wrote: Based on the UCCX tech note I found, I’d say the shutdown and final modifications should be made after a full switch version is performed and you’re running the upgrade release on your active partitions. This differs from the official word from Cisco on CUCM, which is to adjust the virtual machine resources to match the OVA template specifications before the upgrade is performed. However, also according to official documentation, changing the vNIC to VMXNET3 through PowerCLI should be done post-upgrade. Personally I’ve seen all these modifications being performed after the upgrade is completed and version switched with no negative impact whatsoever, but official documentation and TAC’s stance says the virtual machine settings should be modified first, followed by the upgrade, then wrapped up with the vNIC change to VMXNET3. I can provide documentation if needed - it seems that UCCX documentation differs. Also don’t forget to set the OS security settings to “permissive” if you wish to auto-update the VMware Tools on the virtual machines. - Dan From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Andrew Grech Sent: Thursday, February 19, 2015 11:43 PM To: Cisco VoIP Group Subject: [cisco-voip] UCCX Virtual 9.0(2) to 10.6(1) Upgrade Hi, I'm preparing an upgrade of uccx 9.0(2) to 10.6(1) When would be be the best time to adjust the OVA file? I need to change the RAM and Guest OS to RHEL6 (although Guest OS change step is not documented)
