cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Walkthrough Wednesdays
912
Views
25
Helpful
10
Replies
JonesR
Beginner

CUC 11.5.1 > CUC 12.5 Vmware Compatibility

Good Afternoon All,

 

I have been reading the release and upgrade documents for this upgrade. I just wanted to check that the Virtual machine needs to be at Compatibility version 13 before upgrading the inactive partition? 

 

Also if the upgrade is applied to the inactive partition, and then left for a week what would the implications be to voicemails received during that time?

 

If that is a yes, will CUC cope if i upgraded VM Compat from 7 (Current) to 13?

 

Many thanks,

RJones

 

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
Roger Kallberg
VIP Advisor

I would recommend you to change the VM configuration for compatibility after you have switched to the new version. However there is also a requirement to change the guest OS on the VM to CentOS-7. This change should per guidelines be done prior to the upgrade. Worth knowing is that the upgrade from 11 to 12 on CUC will not do the upgrade on the inactive partition. It will run directly on the active partition. So you would not actually do a switch version to activate 12. If you do a switch version after the upgrade completes you’d switch back to the 11 version. I experienced this first hand last year when we upgraded our systems to 12.5.

This is documented in the upgrade guide.

Please rate all useful posts

View solution in original post


@JonesR wrote:

Morning Roger,

 

I have been reading this document.

 

Once again read it again, and I think I understand it will be a RU not a SU as the OS is still using Redhat. 

 

Due to this then it will upgrade the active Partition due to the OS upgrade as well as the CUC. Nice.


This part of the referenced document is the applicable pieces.

10.x.x/11.x.x or later to 12.5(1) or later

Note 

For 10.0(1) to 12.5(1), you must follow an intermediate upgrade path. Example: 10.0(1) to 11.x or later and then 11.x or later to 12.5(1)

  • You need the following COP file before performing this upgrade:

    • ciscocm.cuc_upgrade_12_0_v1.2.k3.cop.sgn

  • The new version is installed on the active partition. During RU, switch version is performed automatically.

 

Note

If you are upgrading Unity Connection from any earlier version to release 12.5(1), you must change the Guest Operating System before upgrade.


 

Also check the details in the OVA readme file CUCSRSV_12.5_v1.0.ova.README_Rev1.txt 

Please rate all useful posts

View solution in original post

10 REPLIES 10
arcaidy
Beginner

I don't understand the question about virtual machine compatibility version.


Upgrades to the inactive partition only include voicemail and configurations from that time and before. Anything new will not be there when you swap versions. For example, if you waited a week you would not have any of that weeks voicemail or system changes.
If you have single inbox enabled this might not be an issue since the voicemails will be in their email. Anyone not using that though would lose any voicemails that came in during that week.
You could use COBRAS to back up the messages and then restore them. But I think you'd be better off during a new upgrade and then switching versions as quickly as possible afterwards.

Thanks,
James Coffey
Roger Kallberg
VIP Advisor

I would recommend you to change the VM configuration for compatibility after you have switched to the new version. However there is also a requirement to change the guest OS on the VM to CentOS-7. This change should per guidelines be done prior to the upgrade. Worth knowing is that the upgrade from 11 to 12 on CUC will not do the upgrade on the inactive partition. It will run directly on the active partition. So you would not actually do a switch version to activate 12. If you do a switch version after the upgrade completes you’d switch back to the 11 version. I experienced this first hand last year when we upgraded our systems to 12.5.

This is documented in the upgrade guide.

Please rate all useful posts

View solution in original post

Morning Roger,

 

I have been reading this document.

 

Once again read it again, and I think I understand it will be a RU not a SU as the OS is still using Redhat. 

 

Due to this then it will upgrade the active Partition due to the OS upgrade as well as the CUC. Nice.

 

When did this change to Cent-OS 12?

 

Thank you for your insight saved me a headache 


@JonesR wrote:

 

When did this change to Cent-OS 12?

From 12.5 the OS for CVOS is CentOS 7 64-bit.

Please rate all useful posts


@JonesR wrote:

Morning Roger,

 

I have been reading this document.

 

Once again read it again, and I think I understand it will be a RU not a SU as the OS is still using Redhat. 

 

Due to this then it will upgrade the active Partition due to the OS upgrade as well as the CUC. Nice.


This part of the referenced document is the applicable pieces.

10.x.x/11.x.x or later to 12.5(1) or later

Note 

For 10.0(1) to 12.5(1), you must follow an intermediate upgrade path. Example: 10.0(1) to 11.x or later and then 11.x or later to 12.5(1)

  • You need the following COP file before performing this upgrade:

    • ciscocm.cuc_upgrade_12_0_v1.2.k3.cop.sgn

  • The new version is installed on the active partition. During RU, switch version is performed automatically.

 

Note

If you are upgrading Unity Connection from any earlier version to release 12.5(1), you must change the Guest Operating System before upgrade.


 

Also check the details in the OVA readme file CUCSRSV_12.5_v1.0.ova.README_Rev1.txt 

Please rate all useful posts

View solution in original post

Hi Roger,

 

Apologies hopefully the last one, maybe, so when you upgraded from 11.5 to 12.5. 

 

Did you upgrade CUC first then when the upgrade was a complete shutdown and do the VMware changes?

 

In which order did you do the steps to get this upgrade done? I am guessing once CUC reboots if its the wrong OS on the VM side it just will fail to boot correctly as it will not be set to cent os?

 

Many thanks

We set the OS to CentOS prior to starting the upgrade as that is what the upgrade guide says. This might sound odd as at this time the OS on the VM would still be Redhat, but it won't actually fail to boot even if guest OS is set to something different that what it's really runs. I'm not an expert in VMware, so I don't actually know exactly what the guest OS setting on the VM does.

Please rate all useful posts
Hard_Boiled_Greg
Beginner

I have this same issue. I am upgrading from CUC version 11.5 to version 12.5. The problem is that there seems to be some contradiction in the advice being given. The Unity Connection 12.5 upgrade documentation says "(Applicable for Unity Connection 12.5(1) and later) Ensure that the virtual machine has ESXi 6.5 U2 and VM version 13." Our VM shows that it is still "ESXi 5.0 virtual machine" which when looking at this chart from VMWare (https://kb.vmware.com/s/article/1003746) means that we are running VM version 8. It is also recommended to modify the VM's Guest OS to CentOS 7 (64-bit) prior to upgrading to CUC 12.5. The only problem is that if you aren't running a newer VM version, you don't even get the option for CentOS 7 presented when modifying the Guest OS. All you get is "CentOS 4/5 or later (64-bit)." No granted, it does say "or later" in that, but I have found that the VM throws the warning "The configured guest OS (CentOS 4/5 or later (64-bit)) for this virtual machine does not match the guest that is currently running (CentOS 7 (64-bit))."

So, unless I update the VM version I am not presented with the option of CentOS 7. Some Cisco UC compatibility documentation suggests not to upgrade VM versions unless there is a specific need to do so due to the nature of what it does and the inherent risk. I'm seeking further clarification from TAC, but this sure seems to be an area of confusion that isn't well documented.

Personally I've never seen any issue with changing the VM compatibility levels on any of our many VMs running various UC services. As you say you won't get the option to set it to CentOS 7 if the VM is not set to a high enough VM compatibility level.

Please rate all useful posts

Did you get an answer from TAC regarding this? 

Content for Community-Ad

Spotlight Awards 2021