This doesnt help: Upgrading VMware Tools on Linux virtual machines fails with the error: Error upgrading VMware Tools (1037320) | VMware K…
Other Vms get :
vix error code = 21000
No VMware Tools package is available. The VMware Tools package is not available for this guest operating system.
Guest OS is RHEL 5 and 6
Any suggestions?
the network icon has a cross on it showing its broken. If i add a network its asking me for options , can you please tell me how to fill it ?
Iam using VSsphere to connect to the VMware server 5.5.
few questions :
- should i be using VLAN or WIRED mode?
- should i be filling in the MAC address ?
- should i be filling the ROUTES section ?
the issue is I cant ping to the local gateway .. i get host unreachable.
[admin@dotstollhadoop1 ~]$ ping 10.100.105.1
PING 10.100.105.1 (10.100.105.1) 56(84) bytes of data.
From 10.100.105.11 icmp_seq=2 Destination Host Unreachable
From 10.100.105.11 icmp_seq=3 Destination Host Unreachable
[admin@dotstollhadoop1 ~]$ netstat -ar
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.100.105.0 * 255.255.255.0 U 0 0 0 eth1
default 10.100.105.1 0.0.0.0 UG 0 0 0 eth1
[admin@dotstollhadoop1 ~]$
Could you attache a screenshot of where you are seeing these options?
- should i be using VLAN or WIRED mode?
- should i be filling in the MAC address ?
- should i be filling the ROUTES section ?
sorry for the late reply on this. From my research on this earlier in the year the link mode is also a single point of failure. the vcenter MSCS is the best form of HA.
Hi,
Login to the ESXi SSH and make sure you have the vmtools directory available with tools ISOs.
below is an example of tools directory in ESXi 5.5.
/locker/packages/5.5.0/packages/5.5.0/vmtools
If the windows.iso exists then try the resolution in the below linked KB
VMware Tools Automatic Upgrade fails with the error: vix error code = 21009 (2129927) | VMware KB
[root@xxxxxxx:/vmfs/volumes/55deec00-6ea3414e-222a-e41f13be37f4/packages/6.0.0/vmtools] ls -l
total 206651
-rwx------ 1 root root 3094528 Mar 4 02:45 darwin.iso
-rwx------ 1 root root 256 Mar 4 02:45 darwin.iso.sig
-rwx------ 1 root root 15876096 Mar 4 02:45 freebsd.iso
-rwx------ 1 root root 256 Mar 4 02:45 freebsd.iso.sig
-rwx------ 1 root root 73893888 Jul 22 12:37 linux.iso
-rwx------ 1 root root 256 Jul 22 12:38 linux.iso.sig
-rwx------ 1 root root 1738 Mar 4 02:45 linux_avr_manifest.txt
-rwx------ 1 root root 540672 Mar 4 02:45 netware.iso
-rwx------ 1 root root 256 Mar 4 02:45 netware.iso.sig
-rwx------ 1 root root 13404160 Mar 4 02:45 solaris.iso
-rwx------ 1 root root 256 Mar 4 02:45 solaris.iso.sig
-rwx------ 1 root root 49 Mar 4 02:45 solaris_avr_manifest.txt
-rwx------ 1 root root 451 Mar 4 02:45 tools-key.pub
-rwx------ 1 root root 14090240 Mar 4 02:45 winPre2k.iso
-rwx------ 1 root root 256 Mar 4 02:45 winPre2k.iso.sig
-rwx------ 1 root root 49 Mar 4 02:45 winPre2k_avr_manifest.txt
-rwx------ 1 root root 90701824 Mar 4 02:45 windows.iso
-rwx------ 1 root root 256 Mar 4 02:45 windows.iso.sig
-rwx------ 1 root root 1069 Mar 4 02:45 windows_avr_manifest.txt
[root@xxxxxxx:/vmfs/volumes/55deec00-6ea3414e-222a-e41f13be37f4/packages/6.0.0/vmtools] pwd
/locker/packages/6.0.0/vmtools
[root@xxxxxxx:/vmfs/volumes/55deec00-6ea3414e-222a-e41f13be37f4/packages/6.0.0/vmtools]
So the files are there
doesnt help.
Any other suggestions?
Greg
Could you share the Guest OS details and the latest vmware.log of the VM.
Also share the /var/log/vmware-tools-upgrader.log file
Guest details (do you need more?):
[root@guestos ~]# cat /etc/issue
Red Hat Enterprise Linux Server release 5.11 (Tikanga)
Kernel \r on an \m
[root@guestos ~]# uname -a
Linux guestos 2.6.18-407.el5 #1 SMP Fri Oct 16 12:04:40 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@guestos ~]#
vmware.log:
2016-07-25T07:34:35.259Z| vmx| I120: VigorTransportProcessClientPayload: opID=43B35BFC-00000208-f-67-832a seq=92535: Receiving ToolsInstallManager.Install request.
2016-07-25T07:34:35.280Z| vmx| I120: TOOLS INSTALL entering BEGINNING state.
2016-07-25T07:34:35.282Z| vmx| I120: TOOLS INSTALL could not find tools for this guest OS.
2016-07-25T07:34:35.282Z| vmx| I120: TOOLS INSTALL Initialization failed.
2016-07-25T07:34:35.282Z| vmx| I120: TOOLS INSTALL entering IDLE state.
2016-07-25T07:34:35.282Z| vmx| A115: ConfigDB: Setting toolsInstallManager.updateCounter = "12"
2016-07-25T07:34:35.302Z| vmx| A115: ConfigDB: Setting toolsInstallManager.lastInstallError = "21000"
2016-07-25T07:34:35.302Z| vmx| I120: Vix: [77362 vigorCommands.c:545]: VigorToolsInstallManagerCommandCallback: toolInstallErr = 1
2016-07-25T07:34:35.302Z| vmx| I120: VigorTransport_ServerSendResponse opID=43B35BFC-00000208-f-67-832a seq=92535: Completed ToolsInstallManager request.
2016-07-25T07:34:35.317Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'VMCI' (cmd=queryFields)
2016-07-25T07:34:35.372Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'VMCI' (cmd=queryFields)
there is no /var/log/vmware-tools-upgrader.log
Greg
attaching 4 screen shots . 
when the host profile you are attached to the host has different configuration, then the compliance errors will be seen. You can apply the host profile to accept the changes. Once you apply host profile, changes will be applied.
Could you also send a sceenshot of the edit settings for the VM? I'm interested in the VMs network settings and also post a screenshot of the network config for the host
Hi All,
I recently created a Test Lab on VCenter 5.1, ESXi 5.1 and Vsphere 5.1, to test upgrading to 6.0.
All went fine, upgraded all the above to 6.0... However, one issue is that I can't login to my VCenter using Domain credentials. I can log in using administrator@vsphere.local and the password I created on the install.
Is there a setting I may have incorrectly selected on the install of VC? Or another setting elsewhere?
Look forward to hearing from you.
Regards
Paul
Hi Paul,
Can you go to the identity source configuration and check if the connection between the AD and the vCenter server is still intact?
Let me know what the result is.
Hi Abhilashhb, thanks for replying.
It looks as if it is there, yes...
Click on the edit button and check if "Test connection" completes successfully. Then try to login again with domain user.
Sorry If I am being dim, but I can't see that Test button when editing the policy?
Hi there, we are getting these errors
2016-07-26T07:45:07.296Z cpu5:85313)WARNING: CBT: 2056: Unsupported ioctl 60
2016-07-26T07:45:07.296Z cpu5:85313)WARNING: CBT: 2056: Unsupported ioctl 44
They appear when backups are run
VMWare say to ignore them, however, they state
Our numbers are 44,60,61 so wondered if the “ignore the errors” still applies?
Appreciate any help.
Has anyone found a fix for this? I am getting a mix of IP's and Host Names in my syslog collector directory. I can't seem to find where the difference is between hosts. I am using a Windows based vCenter 6 server with the default syslog collector directory. All host are setup in the same way using host profiles, but some show up as IP and some show up as Host name.