Re: [cisco-voip] CUCM 8.6 promotion of new pub
All subs will need to be rebooted, hence the re-registration of all phones. Neal Haas From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of TG Sent: Saturday, November 01, 2014 7:23 PM To: cisco-voip@puck.nether.net Subject: [cisco-voip] CUCM 8.6 promotion of new pub Hi all, In order to promote a new publisher to existing phones, cert consolidation is required on existing cluster to authenticate the new publisher and be able to register successfully. Since this consolidation step (even without resetting the service) generates a reset on all phones of existing cluster, is there a way to control this behavior in order to prohibit 20 or 30,000 phones from resetting all at the same time? ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] CUCM 8.6 promotion of new pub
That's some strange behavior since the bulk reset is due to a change in the ITL. Importing CallManager-trust certificates like what happens during a Bulk Certificate Import shouldn't change anything in the ITL. But it looks like the behavior is documented- https://tools.cisco.com/bugsearch/bug/CSCun32117 I don't know of any workaround to prevent the phones from resetting when the ITL gets updated through the normal processes of adding a node or regenerating a certificate so I'm assuming it should be the same here. Brian On Sat, Nov 1, 2014 at 10:22 PM, TG techguy...@gmail.com wrote: Hi all, In order to promote a new publisher to existing phones, cert consolidation is required on existing cluster to authenticate the new publisher and be able to register successfully. Since this consolidation step (even without resetting the service) generates a reset on all phones of existing cluster, is there a way to control this behavior in order to prohibit 20 or 30,000 phones from resetting all at the same time? ___ 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] UC Apps on Unsupported ESXi Versions
All, I'm planning an upgrade to UCCX 8.5(1)SU3 to 10.5(1)SU1 by way of 8.5(1)SU4. My ESXi is on 4.1 and I am planning to upgrade it to 5.5. The virtualization guide does not list ESXi 5.5 as supported for UCCX 8x. http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Version_8.5.28x.29 And, the virtualization guide also does not list ESXi 4.1 as supported for UCCX 10x. http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Version_10.5.28x.29 I am wondering if anyone has experience with this and if it really matters what order I do the upgrades in, considering that at the end of the maintenance window, I will be on UCCX 10.5(1)SU1 and ESXi 5.5; which is supported. My biggest concern is with the UCCX upgrade to 8.5(1)SU4 halting because of a hardware/software compatibility check while on ESXi 5.5, or likewise, UCCX 10.5(1)SU1 halting because of ESXi 4.1. This is also why the subject of this email says UC Apps and not UCCX. I would suspect all UC Apps (VOS based ones anyway) upgrade in the same manner, when it comes to hardware/software checks. Actually, do UC Apps even check your version of ESXi? Or do they just see VMware and the hardware resources allocated? Thank you. ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UC Apps on Unsupported ESXi Versions
Thanks Brian. That's exactly the kind of information I'm after. I'm hoping someone can validate it with empirical evidence. It worth mentioning the following, which I replied to another list user who direct messaged me, in regards to OVA settings during the upgrade. According to the CUCM and CUC upgrade guides, you can change the OS before or after the upgrade. Se the CUCM guide here where it states OS changes are a pre-upgrade task: 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/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100_chapter_011.html#CUCM_TK_C9AFC8CC_00 And here in the CUC guide where it's a post upgrade task: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrugx/10xcucrug010.html#pgfId-1145799 Interestingly enough, UCCX documentation has no mention of changing OS or Network Adapter. Not in the Upgrade Guide, Release Notes, nor the OVA Read Me. I have opened a request to have this reviewed, it might be a miss or it might be the way it is. Upgrade Guide http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/crs/express_10_5/install/guide/UCCX_BK_C2650101_00_cisco-unified-contact-center-express.html Release Notes http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/crs/express_10_5/release/docs/UCCX_BK_UBDB029E_00_uccx-release-notes-105.html http://www.cisco.com/web/software/280840578/117186/UCCX_RN_10.5su1.pdf OVA Read Me http://www.cisco.com/web/software/283733053/114894/UCCX_v2.6_vmv8.ova_README.txt On Mon, Nov 3, 2014 at 12:54 PM, Brian Meade bmead...@vt.edu wrote: I just got through updating our internal UCCX to 9.0.2(SU2) to get ESXi 5.5 support prior to migrating to our 5.5 infrastructure. I'm not sure if anything really changed to support 5.5 though outside of the BU just finally testing it. On Mon, Nov 3, 2014 at 12:25 PM, Anthony Holloway avholloway+cisco-v...@gmail.com wrote: All, I'm planning an upgrade to UCCX 8.5(1)SU3 to 10.5(1)SU1 by way of 8.5(1)SU4. My ESXi is on 4.1 and I am planning to upgrade it to 5.5. The virtualization guide does not list ESXi 5.5 as supported for UCCX 8x. http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Version_8.5.28x.29 And, the virtualization guide also does not list ESXi 4.1 as supported for UCCX 10x. http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Version_10.5.28x.29 I am wondering if anyone has experience with this and if it really matters what order I do the upgrades in, considering that at the end of the maintenance window, I will be on UCCX 10.5(1)SU1 and ESXi 5.5; which is supported. My biggest concern is with the UCCX upgrade to 8.5(1)SU4 halting because of a hardware/software compatibility check while on ESXi 5.5, or likewise, UCCX 10.5(1)SU1 halting because of ESXi 4.1. This is also why the subject of this email says UC Apps and not UCCX. I would suspect all UC Apps (VOS based ones anyway) upgrade in the same manner, when it comes to hardware/software checks. Actually, do UC Apps even check your version of ESXi? Or do they just see VMware and the hardware resources allocated? Thank you. ___ 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] Unified E-Mail Interaction Manager 9.0
Anyone online with experience on this particular app? I have a few questions I would like to ask off-line. am...@datasourcepro.commailto:am...@datasourcepro.com Thanks, Angel ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] CUCM 8.6 promotion of new pub
I'm not aware of the specifics of the doc bug Brian referenced but the original question sounds less like bulk cert import and more like a publisher recovery. Can you provide a bit more details on what you mean by promote a new publisher to existing phones? -Ryan On Nov 3, 2014, at 11:33 AM, Brian Meade bmead...@vt.edumailto:bmead...@vt.edu wrote: There shouldn't be a need to restart any subscribers. Should just need to restart TVS on all the nodes at most. On Mon, Nov 3, 2014 at 10:19 AM, Haas, Neal nh...@co.fresno.ca.usmailto:nh...@co.fresno.ca.us wrote: All subs will need to be rebooted, hence the re-registration of all phones. Neal Haas From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.netmailto:cisco-voip-boun...@puck.nether.net] On Behalf Of TG Sent: Saturday, November 01, 2014 7:23 PM To: cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net Subject: [cisco-voip] CUCM 8.6 promotion of new pub Hi all, In order to promote a new publisher to existing phones, cert consolidation is required on existing cluster to authenticate the new publisher and be able to register successfully. Since this consolidation step (even without resetting the service) generates a reset on all phones of existing cluster, is there a way to control this behavior in order to prohibit 20 or 30,000 phones from resetting all at the same time? ___ 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 ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] UC Apps on Unsupported ESXi Versions
UCCX tends to be a few releases behind UCM in the OS that they run on so it's likely the vNIC issue UCM hit just hasn't affected UCCX (yet). On the pre vs post upgrade, it's just how the teams tested it and decided to write it up. IMO as long as the changes are done before going back into production that's all that matters. The benefit to doing them pre is that a reboot will give the VM a chance to upgrade vmtools automatically. -Ryan On Nov 3, 2014, at 2:23 PM, Anthony Holloway avholloway+cisco-v...@gmail.commailto:avholloway+cisco-v...@gmail.com wrote: Thanks Brian. That's exactly the kind of information I'm after. I'm hoping someone can validate it with empirical evidence. It worth mentioning the following, which I replied to another list user who direct messaged me, in regards to OVA settings during the upgrade. According to the CUCM and CUC upgrade guides, you can change the OS before or after the upgrade. Se the CUCM guide here where it states OS changes are a pre-upgrade task: 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/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100_chapter_011.html#CUCM_TK_C9AFC8CC_00 And here in the CUC guide where it's a post upgrade task: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrugx/10xcucrug010.html#pgfId-1145799 Interestingly enough, UCCX documentation has no mention of changing OS or Network Adapter. Not in the Upgrade Guide, Release Notes, nor the OVA Read Me. I have opened a request to have this reviewed, it might be a miss or it might be the way it is. Upgrade Guide http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/crs/express_10_5/install/guide/UCCX_BK_C2650101_00_cisco-unified-contact-center-express.html Release Notes http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/crs/express_10_5/release/docs/UCCX_BK_UBDB029E_00_uccx-release-notes-105.html http://www.cisco.com/web/software/280840578/117186/UCCX_RN_10.5su1.pdf OVA Read Me http://www.cisco.com/web/software/283733053/114894/UCCX_v2.6_vmv8.ova_README.txt On Mon, Nov 3, 2014 at 12:54 PM, Brian Meade bmead...@vt.edumailto:bmead...@vt.edu wrote: I just got through updating our internal UCCX to 9.0.2(SU2) to get ESXi 5.5 support prior to migrating to our 5.5 infrastructure. I'm not sure if anything really changed to support 5.5 though outside of the BU just finally testing it. On Mon, Nov 3, 2014 at 12:25 PM, Anthony Holloway avholloway+cisco-v...@gmail.commailto:avholloway+cisco-v...@gmail.com wrote: All, I'm planning an upgrade to UCCX 8.5(1)SU3 to 10.5(1)SU1 by way of 8.5(1)SU4. My ESXi is on 4.1 and I am planning to upgrade it to 5.5. The virtualization guide does not list ESXi 5.5 as supported for UCCX 8x. http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Version_8.5.28x.29 And, the virtualization guide also does not list ESXi 4.1 as supported for UCCX 10x. http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Version_10.5.28x.29 I am wondering if anyone has experience with this and if it really matters what order I do the upgrades in, considering that at the end of the maintenance window, I will be on UCCX 10.5(1)SU1 and ESXi 5.5; which is supported. My biggest concern is with the UCCX upgrade to 8.5(1)SU4 halting because of a hardware/software compatibility check while on ESXi 5.5, or likewise, UCCX 10.5(1)SU1 halting because of ESXi 4.1. This is also why the subject of this email says UC Apps and not UCCX. I would suspect all UC Apps (VOS based ones anyway) upgrade in the same manner, when it comes to hardware/software checks. Actually, do UC Apps even check your version of ESXi? Or do they just see VMware and the hardware resources allocated? Thank you. ___ 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 ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] CUCM 8.6 promotion of new pub
Brian, Thanks for your input. It's unfortunate we have to live with it. Need to know the significance and purpose of TVS restart on subs, as results are seen without doing it as well. Also does that cause another reset on the phones? Ryan, Maybe you misunderstood it, it is about bulk cert, and not pub recovery. Do you know of a way to stop phones from resetting just by combining the cert? We see this being fixed in 9.5 but not everyone is willing to jump to 9.5 for this gap. Cisco should consider addressing this on 8.6 and 9.1 as well as many customers are using these releases. If your 30k phones have to take a hit because of cert combining, then that's a big drawback to this whole procedure of cluster replacements. Thanks, TG On 2014-11-03 4:39 PM, Ryan Ratliff (rratliff) wrote: I'm not aware of the specifics of the doc bug Brian referenced but the original question sounds less like bulk cert import and more like a publisher recovery. Can you provide a bit more details on what you mean by promote a new publisher to existing phones? -Ryan ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] CUCM 8.6 promotion of new pub
TG, you state that you aren't trying to promote a sub, but your subject line indicates that you are. When talking about combining certs and TVS restarts, thats for a migration, moving phones from one cluster to another. This is not a way to promote a sub to a pub, which you cannot do. If you are upgrading while rebuilding a new cluster, that is one thing, but we don't do this often, and most customers do not ever do this. What I mean by this is if you are building a fresh, new cluster with the latest version and then moving phones to this new setup. Rebuilding to resolve dial plan best practices or splitting a company are the only reasons I've seen the need of a migration, but perhaps moving a group of phones from one cluster to another in a very large deployment could be a practical use of it. Pushing new certs down (by combining them) is going to cause some restarts of phones, plan for that with your outages. It's really no different than planned outages around upgrading firmware in prep for a software upgrade, which causes another round of resets as they re-register with subs. Good luck and ask your questions, but please clarify your plan and intents. On Mon, Nov 3, 2014 at 5:53 PM, TG techguy...@gmail.com wrote: Brian, Thanks for your input. It's unfortunate we have to live with it. Need to know the significance and purpose of TVS restart on subs, as results are seen without doing it as well. Also does that cause another reset on the phones? Ryan, Maybe you misunderstood it, it is about bulk cert, and not pub recovery. Do you know of a way to stop phones from resetting just by combining the cert? We see this being fixed in 9.5 but not everyone is willing to jump to 9.5 for this gap. Cisco should consider addressing this on 8.6 and 9.1 as well as many customers are using these releases. If your 30k phones have to take a hit because of cert combining, then that's a big drawback to this whole procedure of cluster replacements. Thanks, TG On 2014-11-03 4:39 PM, Ryan Ratliff (rratliff) wrote: I'm not aware of the specifics of the doc bug Brian referenced but the original question sounds less like bulk cert import and more like a publisher recovery. Can you provide a bit more details on what you mean by promote a new publisher to existing phones? -Ryan ___ 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] CUCM 8.6 promotion of new pub
TG, Restarting TVS is just to make sure TVS has loaded in all the trust certificates. It may not be necessary and should have minimal impact on phones. It won't reset the phones but they may have a small amount of time where they can't authenticate certificates for things like accessing corp directory (only a few seconds). I believe the bug is just a documentation bug to document the behavior. It showing as fixed means it was added to the release notes rather than the behavior actually changing. Brian On Mon, Nov 3, 2014 at 8:53 PM, TG techguy...@gmail.com wrote: Brian, Thanks for your input. It's unfortunate we have to live with it. Need to know the significance and purpose of TVS restart on subs, as results are seen without doing it as well. Also does that cause another reset on the phones? Ryan, Maybe you misunderstood it, it is about bulk cert, and not pub recovery. Do you know of a way to stop phones from resetting just by combining the cert? We see this being fixed in 9.5 but not everyone is willing to jump to 9.5 for this gap. Cisco should consider addressing this on 8.6 and 9.1 as well as many customers are using these releases. If your 30k phones have to take a hit because of cert combining, then that's a big drawback to this whole procedure of cluster replacements. Thanks, TG On 2014-11-03 4:39 PM, Ryan Ratliff (rratliff) wrote: I'm not aware of the specifics of the doc bug Brian referenced but the original question sounds less like bulk cert import and more like a publisher recovery. Can you provide a bit more details on what you mean by promote a new publisher to existing phones? -Ryan ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
