Export list of VMs with Snapshots
get-vm | get-snapshot | select vm, name, description, created, sizegb | export-csv -path “c:\temp\file.csv” -notypeinformation
get-vm | get-snapshot | select vm, name, description, created, sizegb | export-csv -path “c:\temp\file.csv” -notypeinformation
As any techie knows, the best way to keep on top of the ever changing products and services they specialize in is to either run a Lab or make use of lab like environments. Fortunately with VMware we have the awesome VMware Hands On Labs (HOL) which allows you to test many if not all
In a proof of concept environment i am currently working in we have an issue with significant over-commitment of resource. Memory is currently around 3:1. Because of this we are seeing workloads often hitting 100% with demand significantly higher: During these periods, we can see VMs were seeing significant memory contention % sometimes exceeding 80%.
This week i had been tasked with collecting lists of VMs that are tagged within certain vSphere tag categories and then compiling lists of their metrics so that service group owners can identify resource demand during testing. This information would also be useful if rightsizing your environment or planning new infrastructure. I used the following
Occasionally you can run into the situation where you need to leave a host down for an extended period of time and the business is happy to sign off on a loss of storage redundancy while any work is completed. In a vSAN environment without further action this could lead to a significant number of
Useful commands you can run to gather vSAN & Storage related information for troubleshooting uptime vmware -vl esxcli vsan cluster get esxcli vsan health cluster list esxcli vsan health cluster get -t=”Overall disks health” esxcli vsan storage list esxcli storage core device list esxcli storage core device stats get Much of this is useful to
Recently i ran into an issue while trying to hot P2V a linux server. It kept stopping at 1%, after creating the helper VM it seems to fail to log on… After some digging it appears that because the vlan these VMs sit on doesnt have DHCP, you need to manually configure its IP information
Creating a new TCP/IP stack is extremely easy but will need to be completed on each host making use of it. You simply run the following command: #esxcli network ip netstack add -N “Name“
While creating a nested lab recently i noticed occasionally some SSD backed datastores & local disk when in single disk RAID0 weren’t correctly displaying as being SSD. Fortunately its a quick fix to resolve this on the host, simply complete the following: SSH to your Host ESXi1#esxcli storage nmp device list 2.Locate the id of
Recently i had to go through tagging some VMs belonging to the same service group. Initially this is to speed up troubleshooting of performance issues within that service group but ultimately they will be used to assist with charge back to service groups/departments. This can be a very time consuming process when completed manually so