VMware ESXi command line

-
Following are some useful commands I'm using in daily management of VMware ESXi 5.5 servers.

Showing the ESXi Gateway alternate to "netstat -rn" in Linux: 

# esxcfg-route -l


Alternate to "arp" command in Linux:

# esxcli network ip neighbor list


List of all registered VMs:

 # vim-cmd vmsvc/getallvms


Restart the vpxa and ESXi host management agents:

# /etc/init.d/hostd restart
# /etc/init.d/vpxa restart


Restart all the mgmt services in the ESXi host:

# /sbin/services.sh restart


Restart VMware vCenter services:

Remote desktop to Windows vCenter server, in the services, restart "VMware VirtualCenter Server".
Same goes to restarting vCenter Inventory as well.


Alternate to "top" in Linux:

# esxtop 


Check ESXi version and update level:

#vmware -vl
   VMware ESXi 5.5.0 build-2068190
   VMware ESXi 5.5.0 Update 2


Listing the files that are opened and being used by VM:

# vmkvsitools lsof | grep vm_name 


Current state of a virtual machine:

# vim-cmd vmsvc/getallvms


Shutdown the VM using the VMID in previous step:

# vim-cmd vmsvc/power.getstate VMID
# vim-cmd vmsvc/power.shutdown VMID


Poweroff the VM in case it fails to shutdown:

# vim-cmd vmsvc/power.off VMID





Comments

Post a Comment

Popular posts from this blog

Rebuild your new Yum repository after changing the packages

-
If you have done any  changes  to your local  repository  packages, adding new ones or deleting some, you can just simply update your yum sqlite metadata database for your changes to take effect, rather than creating the whole repository again which takes time if you have  thousands  of packages in your repository.  Here is how we rebuild our yum repository. 1. After you are done with adding/removing packages to your local repo, then: # createrepo --update /path/to/repo_dir 2. On the  client  side, you need to clean up the cached yum meta data in order to see the changes after repo rebuild: # yum clean all 3. Now update the  client  yum cache  # yum update
Read more

Running Docker Wildfly/JBoss Application Server in Debug mode via Eclipse

-
I have recently built the whole Development Environment of Java Enterprise Edition (J2EE) project on multiple Docker containers. It has saved the hassle of setting up a dev env for new developers. All it takes to setup the environment is to clone our github repositories and run the Docker images. I will explain the setup in a future post. Build Wildfly Docker Image with Debugging Enabled So basically in order to run the Wildfly in debug mode, we need to add --debug  flag to the Wildfly standalone.sh  startup script. Also we need to expose port 8787  in our image as it's the default port for Wildfly JVM debug mode. 1. Create or change your Wildfly Dockerfile as follows: $ cat Dockerfile FROM jboss/wildfly: 10.0 . 0 .Final EXPOSE 8787 CMD [ "/opt/jboss/wildfly/bin/standalone.sh" , "-b" , "0.0.0.0" , "-bmanagement" , "0.0.0.0" , "--debug" ] 2. Build and tag the image: $ docker build -t wildfly-debug . 3.
Read more

Linux and AIX user non expiry and force password change at first login

-
In Linux, if you want to set the password for an account to never expire, here is the command: # chage -I -1 -m 0 -M 99999 -E -1 username  And to force a user to change his password upon first login: # chage -d0 username Current status of the account can be checked via chage command : # chage -l username  Last password change                                    : Jun 18, 2013 Password expires                                        : never Password inactive                                       : never Account expires                                         : never Minimum number of days between password change          : 0 Maximum number of days between password change          : 99999 Number of days of warning before password expires       : 7 For AIX, to set the password to non expiry and force the user to change his password upon first login: # chuser expires=0 maxage=0 username  To check the username status in AIX: # lsuser -f username
Read more