ESXi

Optimization

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008205

http://www.virtualinsanity.com/index.php/2010/03/16/performance-troubleshooting-vmware-vsphere-storage/

https://vikernel.wordpress.com/2014/06/27/troubleshooting-storage-performance/

Get hardware info

smbiosDump | egrep '(Product|Serial)' 
lspci -p

EVC and CPU Compatibility FAQ (1005764)

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005764#Which%20CPUs%20are%20compatible%20with%20each%20EVC%20mode?

http://www.virten.net/2013/04/intel-cpu-evc-matrix/

Manger host

To power on a virtual machine from the command line

List the inventory ID of the virtual machine with the command:

vim-cmd vmsvc/getallvms |grep <vm name>

Check the power state of the virtual machine with the command:

vim-cmd vmsvc/power.getstate <vmid>

Power-on the virtual machine with the command:

vim-cmd vmsvc/power.on <vmid> 

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1038043

Show FC WWN

[root@localhost:~] esxcli storage san fc list
Adapter: vmhba2
Port ID: 010B00
Node Name: 20:00:00:90:fa:86:71:cc
Port Name: 10:00:00:90:fa:86:71:cc
Speed: 8 Gbps
Port Type: NPort
Port State: ONLINE

Adapter: vmhba3
Port ID: 010B00
Node Name: 20:00:00:90:fa:82:8d:f4
Port Name: 10:00:00:90:fa:82:8d:f4
Speed: 8 Gbps
Port Type: NPort
Port State: ONLINE

VSAN

http://www.settlersoman.com/how-to-configure-vmware-virtual-san-vsan/

http://flcloudlabs.com/vsan-and-mtu/

http://www.vladan.fr/infiniband-in-the-lab-the-missing-piece-for-vsan/

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2078224

https://vsantco.vmware.com/vsan/SI/SIEV === VSAN Performance test == https://blogs.vmware.com/vsphere/2014/03/supercharge-virtual-san-cluster-2-million-iops.html

Virtual Machine Disks consolidation is needed

https://communities.vmware.com/message/2540110 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002310

Deploying a vApp failed with the error “Cannot initialize property “ | VMware Arena

http://www.vmwarearena.com/2014/02/deploying-vapp-failed-with-the-error-cannot-initialize-property.html

SSLLoadSharedLibraries: Failed to load OpenSSL libraries. libdir is /usr/lib/vmware

Creating the symlink with ln -sf /opt/vmware/lib/vmware/ /usr/lib64/vmware fixes the issue.

在主机上找到已弃用的VMFS卷

这是一个在VMware ESXi6.X上的BUG。

To Resolve is: Restarting the Management agents on an ESXi

[root@GRGESXi01:~] services.sh restart
services.sh: stop /etc/opt/init.d/vmware-fdm
Running vmware-fdm stop
Stopping vmware-fdm:Setting the memory limit for fdm resource pool on this host to
    0 MB
    success

    services.sh: stopped /etc/opt/init.d/vmware-fdm
    services.sh: stop /etc/init.d/vmtoolsd
    Running vmtoolsd stop
    vmtoolsd is not running
    Errors: 
    Sysinfo error on operation returned status : Not found. Please see the VMkernel log for detailed error information
    services.sh: stopped /etc/init.d/vmtoolsd
    services.sh: stop /etc/init.d/vmsyslogd
    Running vmsyslogd stop
    Stopping vmsyslogd service using init is not supported
    services.sh: stopped /etc/init.d/vmsyslogd
    services.sh: stop /etc/init.d/xorg
    Running xorg stop
    services.sh: stopped /etc/init.d/xorg
    services.sh: stop /etc/init.d/snmpd
    Running snmpd stop
    root: snmpd is not running.
    services.sh: stopped /etc/init.d/snmpd
    services.sh: stop /etc/init.d/wsman
    Running wsman stop
    Stopping openwsmand
    services.sh: stopped /etc/init.d/wsman
    services.sh: stop /etc/init.d/sfcbd
    Running sfcbd stop
    This operation is not supported.
    Please use /etc/init.d/sfcbd-watchdog stop
    services.sh: stopped /etc/init.d/sfcbd
    services.sh: stop /etc/init.d/sfcbd-watchdog
    Running sfcbd-watchdog stop
    Getting Exclusive access, please wait...
    Exclusive access granted.
    services.sh: stopped /etc/init.d/sfcbd-watchdog
    services.sh: stop /etc/init.d/vpxa
    Running vpxa stop
    watchdog-vpxa: Terminating watchdog process with PID 34992
    vpxa stopped.
    services.sh: stopped /etc/init.d/vpxa
    services.sh: stop /etc/init.d/vobd
    Running vobd stop
    watchdog-vobd: Terminating watchdog process with PID 33247
    vobd stopped
    services.sh: stopped /etc/init.d/vobd
    services.sh: stop /etc/init.d/memscrubd
    Running memscrubd stop
    memscrubd is not running
    services.sh: stopped /etc/init.d/memscrubd
    services.sh: stop /etc/init.d/lacp
    Running lacp stop
    watchdog-net-lacp: Terminating watchdog process with PID 33478
    services.sh: stopped /etc/init.d/lacp
    services.sh: stop /etc/init.d/nscd
    Running nscd stop
    watchdog-nscd: Terminating watchdog process with PID 34535
    services.sh: stopped /etc/init.d/nscd
    services.sh: stop /etc/init.d/dcbd
    Running dcbd stop
    watchdog-dcbd: Terminating watchdog process with PID 34502
    services.sh: stopped /etc/init.d/dcbd
    services.sh: stop /etc/init.d/smartd
    Running smartd stop
    watchdog-smartd: Terminating watchdog process with PID 34496
    smartd stopped
    services.sh: stopped /etc/init.d/smartd
    services.sh: stop /etc/init.d/cdp
    Running cdp stop
    watchdog-cdp: Terminating watchdog process with PID 34530
    services.sh: stopped /etc/init.d/cdp
    services.sh: stop /etc/init.d/slpd
    Running slpd stop
    Stopping slpd
    services.sh: stopped /etc/init.d/slpd
    services.sh: stop /etc/init.d/rabbitmqproxy
    Running rabbitmqproxy stop
    rabbitmqproxy is not running
    services.sh: stopped /etc/init.d/rabbitmqproxy
    services.sh: stop /etc/init.d/hostd
    Running hostd stop
    watchdog-hostd: Terminating watchdog process with PID 34365
    hostd stopped.
    services.sh: stopped /etc/init.d/hostd
    services.sh: stop /etc/init.d/lbtd
    Running lbtd stop
    watchdog-net-lbt: Terminating watchdog process with PID 34103
    net-lbt stopped
    services.sh: stopped /etc/init.d/lbtd
    services.sh: stop /etc/init.d/sdrsInjector
    Running sdrsInjector stop
    watchdog-sdrsInjector: Terminating watchdog process with PID 34045
    sdrsInjector stopped
    services.sh: stopped /etc/init.d/sdrsInjector
    services.sh: stop /etc/init.d/rhttpproxy
    Running rhttpproxy stop
    watchdog-rhttpproxy: Terminating watchdog process with PID 34159
    VMware HTTP reverse proxy stopped.
    services.sh: stopped /etc/init.d/rhttpproxy
    services.sh: stop /etc/init.d/vvold
    Running vvold stop
    /etc/init.d/vvold stop, called by pid 583428
    vvold is not running.
    services.sh: stopped /etc/init.d/vvold
    services.sh: stop /etc/init.d/nfcd
    Running nfcd stop
    nfcd is not running
    services.sh: stopped /etc/init.d/nfcd
    services.sh: stop /etc/init.d/storageRM
    Running storageRM stop
    watchdog-storageRM: Terminating watchdog process with PID 34052
    storageRM stopped
    services.sh: stopped /etc/init.d/storageRM
    services.sh: stop /etc/init.d/vmfstraced
    Running vmfstraced stop
    watchdog-vmfstracegd: PID file /var/run/vmware/watchdog-vmfstracegd.PID does not exist
    watchdog-vmfstracegd: Unable to terminate watchdog: No running watchdog process for vmfstracegd
    vmfstracegd is not running
    Failed to clear vmfstracegd memory reservation
    services.sh: stopped /etc/init.d/vmfstraced
    services.sh: stop /etc/init.d/sensord
    Running sensord stop
    watchdog-sensord: Terminating watchdog process with PID 34111
    sensord stopped
    services.sh: stopped /etc/init.d/sensord
    services.sh: stop /etc/init.d/swapobjd
    Running swapobjd stop
    watchdog-swapobjd: Terminating watchdog process with PID 33900
    Waiting for process to terminate...
    swapobjd stopped
    services.sh: stopped /etc/init.d/swapobjd
    services.sh: stop /etc/init.d/usbarbitrator
    Running usbarbitrator stop
    watchdog-usbarbitrator: Terminating watchdog process with PID 33932
    usbarbitrator stopped
    services.sh: stopped /etc/init.d/usbarbitrator
    services.sh: stop /etc/init.d/DCUI
    Running DCUI stop
    Disabling DCUI logins
    VobUserLib_Init failed with -1
    services.sh: stopped /etc/init.d/DCUI
    services.sh: stop /etc/init.d/SSH
    Running SSH stop
    SSH login disabled
    VobUserLib_Init failed with -1
    Connect to localhost failed: Connection failure.
    Errors: 
    Invalid operation requested: This ruleset is required and connot be disabled
    services.sh: stopped /etc/init.d/SSH
    services.sh: stop /etc/init.d/vsantraced
    Running vsantraced stop
    watchdog-vsantraced: PID file /var/run/vmware/watchdog-vsantraced.PID does not exist
    watchdog-vsantraced: Unable to terminate watchdog: No running watchdog process for vsantraced
    vsantraced is not running
    watchdog-vsantracedUrgen: PID file /var/run/vmware/watchdog-vsantracedUrgen.PID does not exist
    watchdog-vsantracedUrgen: Unable to terminate watchdog: No running watchdog process for vsantracedUrgen
    vsantracedUrgen is not running
    Persisting traces to /scratch/vsantraces
    cp: can't stat '/var/log/vsantraces/*.index': No such file or directory
    ls: /var/log/vsantraces/*.gz: No such file or directory
    Failed to clear vsantraced memory reservation
    services.sh: stopped /etc/init.d/vsantraced
    services.sh: stop /etc/init.d/vsandevicemonitord
    Running vsandevicemonitord stop
    watchdog-VSANDeviceMonitor: PID file /var/run/vmware/watchdog-VSANDeviceMonitor.PID does not exist
    watchdog-VSANDeviceMonitor: Unable to terminate watchdog: No running watchdog process for VSANDeviceMonitor
    /usr/lib/vmware/vsan/bin/VSANDeviceMonitor.py is not running
    Failed to clear  memory reservation
    services.sh: stopped /etc/init.d/vsandevicemonitord
    services.sh: stop /etc/init.d/vsanObserver
    Running vsanObserver stop
    services.sh: stopped /etc/init.d/vsanObserver
    services.sh: start /etc/init.d/vsanObserver
    services.sh: start /etc/init.d/vsandevicemonitord
    services.sh: start /etc/init.d/vsantraced
    Running vsandevicemonitord start
    Running vsanObserver start
    Running vsantraced start
    services.sh: started /etc/init.d/vsanObserver
    VSAN Cluster not configured, not starting VSANDeviceMonitor
    VSAN Cluster not configured, not starting vsantraced
    services.sh: started /etc/init.d/vsandevicemonitord
    services.sh: started /etc/init.d/vsantraced
    services.sh: start /etc/init.d/SSH
    services.sh: start /etc/init.d/DCUI
    Running DCUI start
    Running SSH start
    Enabling DCUI login: runlevel = 
    VobUserLib_Init failed with -1
    services.sh: started /etc/init.d/DCUI
    Connect to localhost failed: Connection failure.
    SSH login enabled
    VobUserLib_Init failed with -1
    services.sh: started /etc/init.d/SSH
    services.sh: start /etc/init.d/usbarbitrator
    services.sh: start /etc/init.d/swapobjd
    Running usbarbitrator start
    Running swapobjd start
    swapobjd started
    services.sh: started /etc/init.d/swapobjd
    usbarbitrator started
    services.sh: started /etc/init.d/usbarbitrator
    services.sh: start /etc/init.d/sensord
    services.sh: start /etc/init.d/vmfstraced
    services.sh: start /etc/init.d/storageRM
    services.sh: start /etc/init.d/nfcd
    services.sh: start /etc/init.d/vvold
    services.sh: start /etc/init.d/rhttpproxy
    services.sh: start /etc/init.d/sdrsInjector
    services.sh: start /etc/init.d/lbtd
    services.sh: start /etc/init.d/hostd
    services.sh: start /etc/init.d/rabbitmqproxy
    Running vmfstraced start
    Running sensord start
    Running rhttpproxy start
    Running vvold start
    Running sdrsInjector start
    Running storageRM start
    Running lbtd start
    Running hostd start
    Running rabbitmqproxy start
    Running nfcd start
    /etc/init.d/vvold start, called by pid 583971
    VMFS Global Tracing is not enabled.
    services.sh: started /etc/init.d/vmfstraced
    nfcd started
    sensord started
    services.sh: started /etc/init.d/sensord
    services.sh: started /etc/init.d/nfcd
    net-lbt started
    sdrsInjector started
    services.sh: started /etc/init.d/sdrsInjector
    services.sh: started /etc/init.d/lbtd
    storageRM started
    services.sh: started /etc/init.d/storageRM
    vvold max reserve memory set to 200
    VMware HTTP reverse proxy started.
    services.sh: started /etc/init.d/rhttpproxy
    Ramdisk 'hostd' with estimated size of 750MB already exists
    rabbitmqproxy not up, probably not unconfigured yet.
    hostd started.
    services.sh: started /etc/init.d/hostd
    services.sh: started /etc/init.d/rabbitmqproxy
    WaitVvoldToComeUp /var/run/vmware/.vmware-vvol.started created
    vvold stopped after start!
    /var/run/vmware/.vmware-vvol.started is not created
    Successfully cleared vvold memory reservation
    services.sh: started /etc/init.d/vvold
    services.sh: start /etc/init.d/slpd
    Running slpd start
    Starting slpd
    services.sh: started /etc/init.d/slpd
    services.sh: start /etc/init.d/cdp
    services.sh: start /etc/init.d/smartd
    services.sh: start /etc/init.d/dcbd
    services.sh: start /etc/init.d/nscd
    services.sh: start /etc/init.d/lacp
    services.sh: start /etc/init.d/memscrubd
    Running smartd start
    Running dcbd start
    Running lacp start
    Running nscd start
    Running memscrubd start
    Running cdp start
    The checkPages boot option is FALSE, hence memscrubd could not be started.
    services.sh: started /etc/init.d/memscrubd
    nscd started
    services.sh: started /etc/init.d/nscd
    smartd started
    services.sh: started /etc/init.d/smartd
    LACP daemon started
    dcbd started
    services.sh: started /etc/init.d/dcbd
    services.sh: started /etc/init.d/lacp
    cdp started
    services.sh: started /etc/init.d/cdp
    services.sh: start /etc/init.d/vobd
    Running vobd start
    vobd started
    services.sh: started /etc/init.d/vobd
    services.sh: start /etc/init.d/vpxa
    Running vpxa start
    services.sh: started /etc/init.d/vpxa
    services.sh: start /etc/init.d/sfcbd-watchdog
    Running sfcbd-watchdog start
    Getting Exclusive access, please wait...
    Exclusive access granted.
    services.sh: started /etc/init.d/sfcbd-watchdog
    services.sh: start /etc/init.d/sfcbd
    services.sh: start /etc/init.d/wsman
    services.sh: start /etc/init.d/snmpd
    Running snmpd start
    Running sfcbd start
    Running wsman start
    Starting openwsmand
    This operation is not supported.
    Please use /etc/init.d/sfcbd-watchdog start
    services.sh: started /etc/init.d/sfcbd
    services.sh: started /etc/init.d/wsman
    root: snmpd has not been enabled.
    services.sh: started /etc/init.d/snmpd
    services.sh: start /etc/init.d/xorg
    services.sh: start /etc/init.d/vmsyslogd
    services.sh: start /etc/init.d/vmtoolsd
    services.sh: start /etc/opt/init.d/vmware-fdm
    Running vmware-fdm start
    Running vmtoolsd start
    Running vmsyslogd start
    Running xorg start
    Starting vmware-fdm:services.sh: started /etc/init.d/vmtoolsd
    vmsyslogd is running.
    services.sh: started /etc/init.d/vmsyslogd
    Setting the memory limit for fdm resource pool on this host to
            250 MB
            services.sh: started /etc/init.d/xorg
            success

            services.sh: started /etc/opt/init.d/vmware-fdm

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2115558

How to Fix Snapshot consolidation needed fails with a lock message?

There are few ways which you can opt for to fix this issue – you need to follow the below steps choose your methods.

Method – 1

Note the path of the disk files before removing or unlinking them from VM

You need to unlink your disk files /vmdk files from virtual machine (Do Not Delete the Disks – Only remove them from Virtual Machine)

Note: You VM must be Power off state when you do the complete activity

Once disks are unlinked from the VM – then you need to run Consolidate

Re-add disks from the datastore and power on your VM – Error message will be solved

–some peoples do also have success by restating the ESX management service from CLI “services.sh restart” but I don’t think this will help long term resolution.

Method – 2 (Best Option to fix the issue)

In this step you can solve the issue online – this means Virtual Machine will be stay powered on during this activity.

You need right click on VM and click Migrate – you need choose migrate disks to another available datastore – this will clear lock on disk files of the virtual machine.

Once storage migration is complete then you can run the consolation and it will fix the issue.

Method – 3 (Good Option to fix – but you need extra space on datastore)

For this option you need to power off you virtual machine and then we will clone the vmdk and that will consolidate the all disks files which are linked to the main disk files of the VM.

Login to ESX / ESXi Server from ssh console to run the below command

From the ESX/ESXi terminal:

vmkfstools -i input output -d format -a adaptertype

From the ESX/ESXi terminal:

vmkfstools -i “/vmfs/volumes/Datastore/examplevm/examplevm.vmdk” “/vmfs/volumes/Datastore 2/newexamplevm/newexamplevm.vmdk” -d thin -a buslogic

Warning: If virtual machine snapshots or delta disks are present, ensure that the source chosen is the current snapshot delta disk. Failing to do so results in an outdated destination copy. However, when using the command, the corresponding descriptor file for the latest delta disk needs to be used when cloning the disk.

For example to clone and/or convert virtual machine disk with snapshot (otherwise known as a delta disk), examplevm-000001.vmdk and like above, from Datastore to Datastore 2 , with a thin-provisioned destination copy, run this command:

From the ESX/ESXi terminal:

vmkfstools -i “/vmfs/volumes/Datastore/examplevm/examplevm-000001.vmdk” “/vmfs/volumes/Datastore 2/newexamplevm/newexamplevm.vmdk” -d thin -a buslogic

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2003638

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=10051

P2V

Network card configuration missing after P2V using VMware Converter

The steps are:

Click Start, click Run, type cmd.exe, and then press ENTER.
Type set devmgr_show_nonpresent_devices=1, and then press ENTER.
Type Start DEVMGMT.MSC, and then press ENTER.
Click View, and then click Show Hidden Devices.
Expand the Network adapters tree.
Right-click the dimmed network adapter, and then click Uninstall.

Finally I configured the static IP on the NIC, and all was well.

http://thebackroomtech.com/2009/10/01/network-card-configuration-missing-after-p2v-using-vmware-converter/

Linux workstation

/etc/init.d/vmware restart
* Starting VMware USB Arbitrator ...    [ !! ]
* Starting VMware services ...          [ ok ]
Failed to initialize                    [ !! ]
* ERROR: vmware failed to start

brightmoon vmware # touch /tmp/x
brightmoon vmware # vmware-networks --migrate-network-settings /tmp/x
Restored network settings
brightmoon vmware # less /tmp/x
brightmoon vmware # rm /var/log/vmware/vmware-usbarb-22* -vf
removed ‘/var/log/vmware/vmware-usbarb-22412.log’
removed ‘/var/log/vmware/vmware-usbarb-22669.log’
removed ‘/var/log/vmware/vmware-usbarb-22877.log’
removed ‘/var/log/vmware/vmware-usbarb-22911.log’
removed ‘/var/log/vmware/vmware-usbarb-22945.log’
brightmoon vmware # vmware-networks --migrate-network-settings /tmp/x
Stopped all configured services on all networks
Restored network settings
brightmoon vmware # /etc/init.d/vmware restart
 * Starting VMware USB Arbitrator ... [ !! ]
 * Starting VMware services ...       [ ok ]
Started Bridge networking on vmnet0
Started all configured services on all networks[ ok ]

kill cancel task

[root@GRGESXi02:~] esxcli vm process list
Redhat_env6.0_landrayOAweixin_89
   World ID: 36079
   Process ID: 0
   VMX Cartel ID: 36077
   UUID: 42 02 ea ad 2a 98 03 07-0e e9 1a 82 36 47 36 6c
   Display Name: Redhat_env6.0_landrayOAweixin_89
   Config File: /vmfs/volumes/5618b866-7b466cdb-3be0-40f2e9638ca0/redhat_ent6.0_lanling_134/redhat_ent6.0_lanling_134.vmx

CentOS_v7%2f64_landrayOAkk_90
   World ID: 36087
   Process ID: 0
   VMX Cartel ID: 36086
   UUID: 42 0b ba 88 cf af 21 4e-60 8f 2f d5 90 32 f4 a9
   Display Name: CentOS_v7%2f64_landrayOAkk_90
   Config File: /vmfs/volumes/5618b866-7b466cdb-3be0-40f2e9638ca0/Redhat_90/Redhat_90.vmx

vSphere Data Protection 6.1
   World ID: 41570
   Process ID: 0
   VMX Cartel ID: 41569
   UUID: 42 0b eb 56 13 69 1c 40-ec fd e1 b6 7e 76 71 e9
   Display Name: vSphere Data Protection 6.1
   Config File: /vmfs/volumes/5625a51a-38b5b428-f929-40f2e9639878/vSphere Data Protection 6.1/vSphere Data Protection 6.1.vmx
[root@GRGESXi02:~] esxcli vm process kill -t soft -w 46015

Troubleshooting

=== Unable to connect to the MKS: Internal error == Worked on this part time for weeks. The shutdown/remove/re-add was all it took. Doesn't explain what happened, but at least I can get back in.

Met same issue on ESXi 6.0 after i added host to VC server. All VMs refused to open console with this error.

I tried to re-add first VM, and it works.

Then i shutdown second VM, open config and increase Video Memory from 4 MB up to 64MB. And it helps too. So it can be some bug with video resolution error.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=749640

Insufficient resources to satisfy vSphere HA failover level

http://www.orionscache.com/2014/08/fixing-insufficient-resources-error-in-vsphere-ha-high-availability/

https://support.software.dell.com/zh-cn/vranger/kb/127660

http://geekswing.com/geek/vmware-cpu-and-ram-reservations-fixing-insufficient-resources-to-satisfy-configured-failover-level-for-ha/

Agent can't send heartbeats

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2091510

IMPI log full

localcli hardware ipmi sel clear

vMotion about

http://frankdenneman.nl/2012/09/07/vsphere-5-1-vmotion-deepdive/

How is disk data migration via vMotion different from a Storage vMotion?

The main difference between vMotion and Storage vMotion is that vMotion does not “touch” the storage subsystem for copy operations of non-shared datastores, but transfers the disk data via an Ethernet network. Due to the possibilities of longer distances and higher latency, disk data is transferred asynchronously. To cope with higher latencies, a lot of changes were made to the buffer structure of the vMotion process. However if vMotion detects that the Guest OS issues I/O faster than the network transfer rate, or that the destination datastore is not keeping up with the incoming changes, vMotion can switch to synchronous mirror mode to ensure the correctness of data.

How-to rename VMNIC in VMware ESXi

http://www.vladan.fr/how-to-rename-vmnic-in-vmware-esxi/

To restart a vCenter Server and/or Platform Services Controller service using the command-line:

To restart a vCenter Server and/or Platform Services Controller service using the command-line:

Backing up and restoring the vCenter Server Appliance vPostgres database

ESXi web client Embedded Host Client – VMware Labs:

https://labs.vmware.com/flings/esxi-embedded-host-client?ClickID=dxroxcxz0cbwwz2ns2hoyocthh0xchokzybk

# Install
scp /path/to/downloaded/vib/esxui.vib root@<esxip>:/tmp
ssh root@<esxip> esxcli software vib install -v /tmp/esxui.vib
# Upgrade 
# ssh root@<esxip> esxcli software vib update -v /tmp/esxui.vib

# Removal
# ssh root@ esxcli software vib remove -n esx-ui

References

http://www.virtuallyghetto.com/2014/12/handy-vcsa-vcenter-server-appliance-operational-kb-resources.html