Nov 09
20
VMware DataRecovery version 1.1 have been released today. You can find the release notes here.
One of the new features is the file level restore that is now fully supported. Reading the manual it looks like you can do the file level restore from within the VM. But hey…I mut still go and test it this weekend.
Nov 09
3
I had an interesting issue today with enabling AD authentication on a ESX4 host. On ESX3.5, when you run : esxcfg-auth –enablad, it will open all the needed ports on the ESX console.
In ESX4 it opens port 88 UDP, but this did not work. As soon as we openend 88 TCP we could use our AD account to login via ssh.
Looking at /etc/vmware/firewall/services.xml you will see that port 88 UDP is specified as activeDirectorKerberos. Reading this wiki the following is mentioned :
“UDP TCP: Originally Kerberos used UDP as its transport protocol but modern implementations also support TCP to overcome PDU size limitations in UDP. All modern clients support TCP but older clients might not.”
(Definition of PDU is here)
Thanks for Craigh Stuart for pointing this out.
Nov 09
3
I got my results from the Enterprise Exam I wrote 2 weeks ago….and I passed !!
So the next step to VCDX is to pass my Design Exam.
Also note for those in South Africa you can write the Exams now in South Africa…so good luck !
Oct 09
22
I was looking around for some VM guest OS support and ended up on this blog : http://blogs.vmware.com/guestosguide/
This is a VMware blog with greate doc’s (Look on the Right hand side) on VM Guest installation guides.
Also there is some links to the VMware Guest Compatibility Guide.
I had this error during a demo I did on vShield Zones: vMotion cannot move the VM to a Virtual Intranet.
What I gather from this is that when you use vShields and you vMotion a VM that is protected from one ESX host to another, it checks if the destination vSwitch has a physical Nic attached and if not, it will fail.
If you are using vShield zones you will have vSwitches without physical nics.
To get around this you, need to add the following lines to the vpxd.cfg file, under the config section, of the Virtual Center server :
<migrate>
<test>
<CompatibleNetworks>
<VMOnVirtualIntranet>false</VMOnVirtualIntranet>
</CompatibleNetworks>
</test>
</migrate>
Then restart Virtual Center service and try again.
I was reading in the VMware communities and found this great article and document on “Troubleshooting Performance issues on ESX and vSphere 4″.
To quote the article:
“The attached document is the first installment in a guide covering performance troubleshooting in a vSphere environment. It uses a guided approach to lead the reader through the observable manifestations of complex hardware/software interactions in order to identify specific performance problems. For each problem covered, it includes a discussion of the possible root-causes and solutions. Topics covered include performance problems arising from issues in the CPU, memory, storage, and network subsystems, as well as in the VM and ESX host configuration. Guidance is given on relevant performance metrics to observe using the vSphere Client and esxtop in order to isolate specific performance issues.”
You can find the document here.
If you have read the VUM support Matrix, you might have noticed that some of the Databases and OS is not supported. Well the doc is not correct.
Here is a KB article that states the changes :
Note: The listed are in addition to the databases already listed in the vSphere Compatibility Matrixes.