topic Re: FMC 6.7 and vmware tools problem in Network Security

FMC 6.7 and vmware tools problem

bodnar.p — Tue, 16 Mar 2021 22:11:53 GMT

hello

After upgradit fmc 6.3 to 6.7, cannot start vmware tools. On system/configuration/VMware tools, after trying enable VMware tools, i got Error - Failed to enable VMware Tools. ESXi is supported version 6.7

so i tried to log-in into cli, and when trying to get tools status i got those errors:

root@vmfmc:/etc/vmware-tools/init# ./vmware-tools-services
./vmware-tools-services: line 17: /usr/lib/vmware-tools/moduleScripts/services/vmware-db.pl: No such file or directory
./vmware-tools-services: line 40: /usr/lib/vmware-tools/moduleScripts/services/vmware-db.pl: No such file or directory
./vmware-tools-services: line 41: /usr/lib/vmware-tools/moduleScripts/services/vmware-db.pl: No such file or directory
Usage: vmware-tools-services {start|stop|status|restart|force-reload}

so i checked /usr/lib (and just to be sure also /usr/lib64) and can't find directory vmware-tools

any ideas?

so i checked

Re: FMC 6.7 and vmware tools problem

cmonterr — Wed, 24 Mar 2021 22:34:16 GMT

Hello,

Please open a TAC case so an engineer can help you with the following workaround:

== Workaround to resolve vmware tools issue:

1. From expert, elevate to root user with sudo su and enter your password

root@firepower:/# updatedb
root@firepower:/# locate vmware | grep -vw sf

2. This will help you determine if VMWare has been previously installed. If it was installed you will see one or more of the following:

/usr/lib/vmware-tools
/etc/vmware-tools
/etc/init/vmware-tools.conf
/etc/ld.so.conf.d/vmware-tools-libraries.conf
/etc/modprobe.d/vmware-tools.conf
/etc/selinux/targeted/modules/active/modules/vmware.pp
/etc/dracut.conf.d/vmware-tools.conf
/usr/bin/vmware-*
/usr/sbin/vmware-*
/usr/share/doc/vmware-*

3. Verify if VMWare tools are currently installed:

root@firepower:/# rpm -qa --last | grep vmware | awk '{print $1}' | xargs rpm -e

4. Next, run the following:

root@firepower:/# rm -rf /usr/lib/vmware-tools
root@firepower:/# rm -rf /etc/vmware-tools

5. And run the previous command again to see if the files are still there:

root@firepower:/# updatedb
root@firepower:/# locate vmware | grep -vw sf

6. Finally, try to re-enable VMWare tools

Re: FMC 6.7 and vmware tools problem

srayancha — Sat, 27 Mar 2021 18:01:32 GMT

These steps worked perfectly for me.

Re: FMC 6.7 and vmware tools problem

bodnar.p — Wed, 31 Mar 2021 10:01:25 GMT

Can confirm, it is working

thanks for help

Re: FMC 6.7 and vmware tools problem

Eric R. Jones — Wed, 05 May 2021 00:02:36 GMT

This worked for me also.

Re: FMC 6.7 and vmware tools problem

TrashPanda — Mon, 17 May 2021 19:25:56 GMT

This just worked for me in 6.7.0.2. Re-enable VMware Tools in the FMC by going to System>Configuration>VMware Tools.

Re: FMC 6.7 and vmware tools problem

loizosko — Wed, 18 Aug 2021 11:35:38 GMT

worked for me also

but the locate seems not working anymore

this command: rpm -qa --last | grep vmware | awk '{print $1}' | xargs rpm -e
was giving me this: rpm: no packages given for erase

so assume was not installed

run these

rm -rf /usr/lib/vmware-tools
rm -rf /etc/vmware-tools

then updatedb

and was able to enable the tools from the configuration page

Re: FMC 6.7 and vmware tools problem

Yordan1 — Fri, 20 Aug 2021 10:25:58 GMT

that works for me

Thx

Yordan

Re: FMC 6.7 and vmware tools problem

razelle — Sat, 11 Dec 2021 20:19:17 GMT

This just worked for me as well under 7.0.1 the /usr/lib/vmware-tools directory did not exist on my system and the locate returned this error locate: Old-format locate database '/var/locatedb' is too short to be valid.

However I was able to enable vmwater-tools now.

Re: FMC 6.7 and vmware tools problem

Priit Kosmopoliit — Wed, 12 Jan 2022 08:27:46 GMT

Everything else besides these:

rm -rf /usr/lib/vmware-tools
rm -rf /etc/vmware-tools

is just for verification and not strictly required.

Can confirm this works as a workaround for 7.0.1

Re: FMC 6.7 and vmware tools problem

esantora — Thu, 27 Jan 2022 13:57:53 GMT

This worked for me with 7.0.1 as well.