Newbie to VMware vSphere – looking for common issues faced daily to solve and learn.

Hello everyone.

Hope everyone is doing well in these dark ages.

I’m hoping to get some assistance to practice more troubleshooting steps and more learn more on Vmware Vsphere 6.7.

I’m in the process trying to get my VCP and I’m looking create some common problems or areas you need to master for working environment. I’m hoping to create some challenges in my lab environment and try to solve them.

At my current work, I’m only creating VM machines at the moment but my manager wants me to be back up of senior admin who is responsibly everything else. We are not using vSAN and or VDS at the moment.

I don’t see many tickets coming in for VMware issues at  my current company. My limit for issues I can think is ESXI failing, storage issues or hardware issues.

I have already done the Challenging labs at HOL.

please let me know if you can think anything.


View Reddit by jbala28View Source

Related Articles


  1. Here is a fun issue to investigate, I run into this kind if issue in the field far too often.

    This is a snapshot exercise, because you need to understand how a snapshot works in Vmware. In your lab, setup a thin provisioned lun. Any way you can bring up a datastore that you can grow. I suggest something small like 100gb. Make a 60gb Windows VM. Build a script that copies a file in a loop making new copies of the file with random names.

    Now, in test one, take a snapshot of the running VM. Then run the loop script until the vm drive files up. Take another snapshot and delete all the loop files to free up the space in the vm (yes, they will still be in the first snapshot). Keep doing this until the datastore files up.

    The VM will go down and you will need to grow the datastore to get rid of the snapshots with out loosing data.

    Why? Why is the only way to recover and NOT loose data when this happens is to grow the datastore?

    Second test: recover from a full lun caused by snapshots with out growing the datastore.

    What do you end up with if you do get the VM back up and running?

  2. So it is difficult to replicate some issues. You will see some unique things the more features you enable and what your environment looks like. I recommend deploying an older VCenter and esxi build so you can complete full upgrades to the next major build. Additionally you can complete this with CLI commands to get a bit more familiar.

    In the past at VMworld they offered challenge labs. I’d see if there is anything like that in their free offerings since I’ve seen them real certain things and you have to fix it. Normally if you cannot fix it, there is a step by step instruction on what is broken. Worth going through as these are some real world scenarios.

  3. Tough question to answer. On autopilot, VMware is pretty solid. Issues I’ve seen randomly happen are surrounding components that cause incompatabilities like a plug-in, server firmware, VM hardware, and/or VMware tools update. Log reviews and isolation tests typically resolve it on my end.

    If you have a ticketing system, it may be worth searching for VMware keywords and seeing that has historically cause issues so you can read around that as a first place to start.

    Highly recommend learning the backup and recovery processes in place for the virtual environment. Murphy’s law…

Leave a Reply