cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3480
Views
0
Helpful
7
Replies

Cisco Unified Communications Applications VMware Tools support

Michael Gioia
Level 1
Level 1

I have a vsphere esxi implementation at 6.0U2.  Which is therefore hosting VMware Tools 10.0.6.

When upgrading all my UC apps (CUCM, CUC, IMP, UCCX* .. this is special.. as it won't update at all), they initially showed VMware Tools running and updated.  But after a restart of the OS of each.  VMware Tools is no longer running...

Anyone can comment/provide feedback.

doc wiki's such as ,

- http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unified_Communications_Manager_%28CUCM%29

- http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CM_IM_and_Presence

Indicate they support ESXi 6.0 and as such the tools is surely supported...

Any comments from anyone ?

Anyone else running 6.0 U2 from vSphere ESXi and pushed it's tools to their UC apps ?

2 Accepted Solutions

Accepted Solutions

Rob Huffman
Hall of Fame
Hall of Fame

Hi Michael,

I would go ahead and open a TAC case as there are a number of bugs related to upgrading VMware Tools to any 10.0 version. Here is one Severity level 2 bug;

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCux90747

VMware Tools 10.0 update fails on CUCM 10.5/11.0 with selinux denials
CSCux90747
Symptom:
VMware Tools upgrade fails due to various Selinux denials. VI-Client indicates tools status as Not running, Not Installed.

View solution in original post

In the last 24 hours Cisco has finally released a fix for this bug for CUCM 10.5(2) and 11.0(1).

Per the release notes for the COP file:

VMware tools upgrade fails due to various Selinux denials and the VM summary tab shows VMware tools Not Running/Not Installed.  The cop file will update the Selinux Policy files so that VMWare tools upgrade happens properly. This COP file also enables the CLI command “utils vmtools caf-logs delete” which can be used to delete CAF logs which takes up disk space.

The cop file is called ciscocm.VMwareTools2016a.cop.sgn and it does require a reboot.

View solution in original post

7 Replies 7

Rob Huffman
Hall of Fame
Hall of Fame

Hi Michael,

I would go ahead and open a TAC case as there are a number of bugs related to upgrading VMware Tools to any 10.0 version. Here is one Severity level 2 bug;

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCux90747

VMware Tools 10.0 update fails on CUCM 10.5/11.0 with selinux denials
CSCux90747
Symptom:
VMware Tools upgrade fails due to various Selinux denials. VI-Client indicates tools status as Not running, Not Installed.

Bingo.. thanks so much rob.huffman. It is my version of UC apps, and SE linux indeed. Running a 'utils os secure permissive' and a reboot, vmware tools are fine. The bug does indicate that if I upgrade I can keep tools running and also go back to using SE linux... which is ideal. Mind you.. UCCX is the anomaly.. where I can't even install it... :/ (https://supportforums.cisco.com/discussion/12946991/uccx-vm-unable-upgradeinstall-vmware-tools)

In the last 24 hours Cisco has finally released a fix for this bug for CUCM 10.5(2) and 11.0(1).

Per the release notes for the COP file:

VMware tools upgrade fails due to various Selinux denials and the VM summary tab shows VMware tools Not Running/Not Installed.  The cop file will update the Selinux Policy files so that VMWare tools upgrade happens properly. This COP file also enables the CLI command “utils vmtools caf-logs delete” which can be used to delete CAF logs which takes up disk space.

The cop file is called ciscocm.VMwareTools2016a.cop.sgn and it does require a reboot.

Hi David,

Thanks for this kind follow up! Much appreciated my friend!

Cheers!

Rob

Agree. Thanks David.

Any news on UCCX ? I have a similar issue with VMTools 10.# that is behaving uniquely on UCCX (vs CUCM, IMP, CUC.. which are all afflicted by this bug/what this thread is talking about).

https://supportforums.cisco.com/discussion/12946991/uccx-vm-unable-upgradeinstall-vmware-tools

I have not personally heard anything about a fix for this with UCCX but I would imagine a fix is imminent.

I have an active case open with Cisco TAC about the CUCM bug (from January!) so the next time I connect with the engineer I will ask about UCCX.  We are a UCCE shop but we leverage the IVRs (which is just UCCX with different licensing), and we are running into this also on our UCCX lab environment where ESXi is already on version 6.0.

Here's the bug they're using to track the UCCX equivalent of this defect: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuy83828

Based on the release notes for the COP file that was released for CUCM, it appears that the COP file is only for CUCM.  So it's actually not clear whether it will work for CUC or IMP as well, or if it's just for CUCM.  Since this is more of an OS issue and doesn't seem to be application specific, I would think (read: hope) that this COP would work regardless of whether it's CUCM, CUC, IMP or CUCCX... but seeing as the UCCX defect mentioned above is still open, perhaps that's not the case.

I also checked the download pages for UCCX and did not see any links to any utilities or COP files, at least not yet.

It seems this issue now also affects CUPS 11.5.1.12900-25 :(
Sadly there doesn't seem to be a cop file for the 11.5.1 release train.