Expressway upgrade to 14.0

[jcanelao]

Can you upgrade an Expressway from 12.5. to 14.0 or do you have to upgrade to 12.7 prior to 14.0?

[Malte_P_Scheuss]

We have clustered Epxressways. We upgraded from 12.5 to 12.7.1 and now 14.0.1.

- We installed 12.5 by OVE with large image on our VCenter 6.7

- Upgrade to 12.7.1 takes about 10 min per server - so you are not wasting time - Upgrade was successful

- Upgrade to 14.0.1 was also easy

=> BUT i received an error, that the vm doesn't fit the requirements.

The error messages links to the VM sizing page
https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-cisco-expressway.html 

But 14.0.1 is not included until today.

Release notes of 14.0.1 are just telling, that the have testet it with VCenter 7 and ESX 6.7. but this does solved may problem.

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/release_note/X14-0-1/exwy_b_cisco-expressway-release-note-x14-0-1.html

- Rollback to 12.7.1 was successfull and it is working fine

[Sebastien Denoncin]

Hello,

We upgraded the expressway 12.7 to 14.0.5 and I have the same error message.

"Your current hardware does not meet supported VM configuration requirements. For information on standard configuration for this version of Expressway, view Virtualization for Cisco Expressway page."

I checked and the hardware spec are correct.

How did you resolve your problem?

Thanks

Regards

Sébastien

[Malte_P_Scheuss]

in my case it was the "processor" because we are running all VMs on Sec based ESX, so please also check 
https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/collaboration-virtualization-hardware.html#processor

We had set up Large deployement but just CPU with 2,5 GHz, so system checked that and gave us this error message.
After just setting down VM sizing to medium size (2 CPU etc) this message disappeared. 

[Alexander Gomer]

Hi Malte,

even with version 14.0.6 I still hitting this issue.

I guess same root cause which you describing, as everything else matching the requirements besides "Physical CPU Base Frequency".

>> After just setting down VM sizing to medium size (2 CPU etc) this message disappeared. 

I guess you have deployed a new VM with smaller VM sizing or is it possible to do this without?

Regards, Alexander

[Malte_P_Scheuss]

Hi ALexander,

nope. i downsized because our CPU did't fullfill the 3,2 GHz for large deployment but 2,6 GHz for medium deployment. And then the message disappeared.

it was an upgrade, no new setup.

[Alexander Gomer]

Hi Malte,

can your further discribe "downsized".

I guess you created a new VM with correct size and then restored form backup right?

I would have to do this on more VM's not just a single one. So I am very interessted in an alterantive solution.

(root shell)

Regards, Alexander

[Malte_P_Scheuss]

Hi ALexander

downsized = after updating to 14.X i received the error, so i turned off the VM, then just changed vCPU from 8 to 2, vRAM from 8 to 6 and then it worked and the message was gone.

[Alexander Gomer]

Hi Malte,

now it is clear, unfortunately this do not work for me as everything for sizing (Cores, RAM, HDD) is machting, besides Physical CPU Base Frequency.

e.g. large need 3,2 GHz but VM's running on 2 GHz

see Bug https://bst.cisco.com/bugsearch/bug/CSCvy07347

Currently I am dealing with TAC to get a solution, without deleting the current VM, create a new one and restore from backup.

Regards, Alexander