VMware
Summary
-
- Shut down the virtual ESXi5 VM
- Click Edit Settings (of that VM)
- Click the Options tab
- Click Advanced / General / Configuration Parameters…
- Click Add Row
- For the Name/Value enter: monitor_control.restrict_backdoor / TRUE
VMWare Clients
VMWare Replication
https://www.vmware.com/products/vsphere/features/replication
http://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/prime-collaboration/white-paper-c11-735844.html
http://pubs.vmware.com/vsphere-replication-60/topic/com.vmware.ICbase/PDF/vsphere-replication-60-admin.pdf
VMware VMFS 5 - VMFS 6
if you only have a single Datastore - how do you migrate from VMFS 5 to 6
- Copy all VMs off VMFS5 to another Machine (or delete!)
- Disable Swamp
- Change Scratch Config to use “/tmp” folder
ESXi 6.7 Upgrade Issue
How to remove Offending VIB
Error:
<MISSING_DEPENDENCY_VIBS ERROR: Found=['EMU_bootbank_scsi_be2iscsi_12.0.1108.0-10EM.600.0.0.2494585']
[root@MYESXISERVER:~] esxcli software vib list | egrep iscsi ima-be2iscsi 12.0.1108.0-1OEM.600.0.0.2494585 EMU VMwareCertified 2019-08-16 scsi-be2iscsi 12.0.1108.0-1OEM.600.0.0.2494585 EMU VMwareCertified 2019-08-16
NOTE - I only removed one of above - which was the exact same name in the install error
[root@MYESXISERVER:~] esxcli software vib remove -n scsi-be2iscsi Removal Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: VIBs Removed: EMU_bootbank_scsi-be2iscsi_12.0.1108.0-1OEM.600.0.0.2494585 VIBs Skipped:
VMware References
Removing VMFS 5 Datastore to Recreate VMFS 6
- Make sure no VMs reference the datastore as CD/DVD drive
- Unregister all VMs from the Datastore
- Move all these VMs to a different Datastore
- Unmount the Datastore
- Recreate the Datastore as VMFS 6
Download Links
SLP
Patching ESXi
- Download the latest bundle patch from VMware for your specific build, e.g. ESXi 6.7
- Upload this zip file using Web Client to a specific folder on a datastore (note you can also host on the Web Server - if doing many servers - this would be quicker - see reference below on using a URL for an upgrade command line).
- SSH to the host and run the update (not install) command line as per the below example.
esxcli software vib update -d "/vmfs/volumes/datastore1/VMwarePatch/ESXi670-202010001.zip"
Reference
VMware - Unlock root account
The root (or other accounts) can get locked by repeated failed attempts. To unlock the account you need to:
- Log into ESXI console via KVM or local monitor, i.e. Direct Console Interface or “DCUI”
- Enable ESXi Shell
F2 -> Login -> View Options -> Troubleshooting Mode Options -> Enable ESXi Shell
- Use ALT + F1 to switch to Command line - and log in as if you were using SSH
- Use ALT + F2 if you need to switch back to standard Text based GUI mode - Reference
- Enter pam_tally2 - -user root to find out how many failed login attempts
- Enter pam_tally2 - -user root - -reset to reset the account
Copying a VM without vCenter
How to copy a VM from ESXi 'A' to ESXi 'B'
- Enable SSH on ESXi Server A
- Enable SSH on ESXi Server B
- Make sure SSH client FW security profile is enabled on Server A (so you can SSH from Server A to Server B)
- The below command will copy the complete VM folder from Server A to Server B
- Use Datastore GUI interface on vSphere to add VM to the inventory
NOTE: Enable SSH Client on Firewall on Server A, so it is allowed out!!!
scp -r "/vmfs/volumes/datastore1/<VM Folder>" root@<ipaddress of esxiB>:/vmfs/volumes/datastore1/
Make sure SSH is enabled on both ESXi Servers
Make sure SSH client FW security profile is enabled on Source Server