Skip navigation


to be honest, i don't like NetworkManager


If you want to disable it in CentOS 7, this steps had better be done:


  1. Check/modify the /etc/sysconfig/network-scripts/ifcfg-WhatEver files in the correct way (Maybe the IPADDR, PREFIX and GATEWAY options are the most important!)
  2. Execute this commands: systemctl disable NetworkManager.service;systemctl stop NetworkManager.service;service network restart (In order to disable networkmanager, stop it and restart the "network" service)


Best regards,



This can be the steps in order to execute one small script in the ESXi command line (SSH).


- Connect to the command line by ssh

- Change directory to some datastore

- Generate the script, this can be one example:






while [ $NUM -lt 3 ]



DATE=`date +"%Y%m%d_%H-%M-%S"`

esxtop -b -d 2 -n 3 > esxtopcapture-$DATE.csv

NUM=`expr $NUM + 1`






- Finally, give execution permission to the script:

busybox chmod 755



In this case, the script iterates the "while" loop three time. Every time a esxtop output file is generated.


Hope this can be helpful to someone



Best regards,



if you want to backup the host configuration using the command line, you can execute this two commands:


  1. vim-cmd hostsvc/firmware/sync_config (In order to save/sync the host configuration)
  2. vim-cmd hostsvc/firmware/backup_config (to backup the configuration)

The last command had better output something similar to this:

Bundle can be downloaded at : http://*/downloads/configBundle-localhost..tgz

Then, the backup can be downloaded connecting to this URL: http://IP_of_the_ESXi_Host/downloads/configBundle-localhost..tgz

If you want to restore the backup, this steps must be done:

  1. vim-cmd hostsvc/maintenance_mode_enter (put the host in maintenance mode)
  2. vim-cmd hostsvc/firmware/restore_config /tmp/configBundle.tgz (restore the backup using the backup file. Before, the backup file must be uploaded to a location accessible by the host)

I got this information from this vmware's kb:

VMware KB: Backing up and restoring ESXi configuration using the vSphere Command-Line Interface and vSphere PowerCLI…

And, we can call it a day!

Best regards,