I always forget the syntax for checking vMotion connectivity between hosts…
Simply put we need to ping specifically from the vMotion network to confirm any vMotion issues.
Display network interfaces (will give you the name)
esxcli network ip interface list |grep -E 'vmk|Netstack'
Check connectivity from vMotion network
ping -I vmk2 -S vmotion IPADDRESSHERE
I’ve been working on a project to upgrade vCentre from 6.0 to 6.5. This meant that multiple Dell (R530, R630, R730) hosts required an update of ESX (using Update Manager). Unfortunately these upgrades failed (first time around) due to the custom VIBs within previous Dell Customized Images of ESXi conflicting with native drivers within ESX6.5. Below is the cheat-sheet of commands to remove these.
vSphere CLI commands. These can be executed by enabling SSH on ESX host and connecting via Putty
List VIBs (Matching “QLC”)
esxcli software vib list | grep QLC
List VIBs (All)
esxcli software vib list
List VIBs (Network) (Check you don’t disconnect yourself)
esxcli network nic list
Remove VIBs (example scsi-mtip32xx-scsi)
esxcli software vib remove -n scsi-mtip32xx-scsi
Host Maintenance Mode
esxcli system maintenanceMode set --enable true
Host Reboot (Needs to be in maintenance mode)
esxcli system shutdown reboot --reason Upgrades
Notes: The vSphere CLI has been superseded by PowerCLI. PowerCLI is distributed as a Windows PowerShell snapin (PowerCLI 6.0 introduced PowerShell module), and includes over 500 PowerShell cmdlets for managing and automating vSphere and vCloud, along with documentation and samples.
Yes the year is 2016! and Yes we are still converting Server 2003 onto VMware! (I know Server 2003 is dead and 13 years behind the times, but there are still some instances in our organisation that still require it for old bespoke software that can’t be easily moved to Server 2013/2016)
When converting a physical “Server 2003” machine to a virtual machine using VMware Converter this error displays:
“Warning: Unable to locate the required Sysprep files. Upload them under ‘C:\ProgramData\VMware vCentre Converter Standalone\sysprep\svr2003’ on the Converter server machine. See ‘Help’ for more details”
1.) Enable SSH via GUI
2.) Load “Putty” – SSH to ESX IP/Hostname
3) Run “services.sh restart”
“Unable to create “datastore” in vSphere client”
Call “HostStorageSystem.ComputeDiskPartitionInfo” for object “storageSystem” on ESXi “172.16.233.55” failed.
I’ve been using VMWare converter and Veeam Replication for a while now but still ask myself the question of “How long will this take to migrate or P2V”
Here’s some results to help with the expected performance…
1 VM Move – Server to Server on LAN (1GBPS Switch)
1 VM Restore – Reverse Incremental Backup on iSCSI to Server on LAN (1GBPS Switch)
After carrying out a re-install of ESXi 5.5 and attaching the VMs the “edit settings” are unavailable.
“You cannot use the vSphere Client to edit the settings of the virtual machines of version 10 or higher.
User the vSphere Web Client to edit the settings of this virtual machine”
As vCentre wasn’t in place for this scenario the workaround was to directly edit the VMs .vmx file.
- Load vSphere Client
- Select VM: “Remove from Inventory”
- Select Storage: “Browse Datastore”
- Select VM Folder: Locate/Download “.vmx” file (approximately 3/4 KB)
- Edit in Notepad
- Modify the “virtualHW.version = “10” to “8”
- Upload “.vmx” file back to VM Folder
- Select “.vmx” and “Add to Inventory”
- VM should now be editable.
I’ve been doing a lot of more work with Dell hardware and configuration of OpenManage. This ties in with my configuration of Dell OpenManage with VMWare ESXi 5.1 & 5.5 and SNMP monitors. See Vmware ESXi Host for info
Here is some info on the installation:
Dell OpenManage Server Administrator (Windows):
Dell OpenManage Server Administrator vSphere Installation Bundle for ESXi:
This offers a full guide on how to install OpenManage on ESXi. I’ve taken this process and tried to simplified it so a script does the work for you on.
Dell VMWare packages:
Installing Dell OpenManager Server Administrator via CLI (No Prompts):
- Download/Install: VMware vSphere CLI 5.1
- Download VIB file (links above)
- Upload VIB file into your VM datastore root (.zip format). Note filename for script
- Change varibles and run script below.
- Process should will notify of errors / completion, this usually takes a few minutes to complete.
"C:\Program Files (x86)\VMware\VMware vSphere CLI\bin\esxcli.exe" --server %hostname% --username %user% --password %password% software vib install -d /vmfs/volumes/%dsname%/%vibname%
echo Task Run | Please see Status above.
This script will output results similar to this…
We cannot display this gallery
Note: The VIB filename must match the name in the datastore.
Although SNMP traps can be configured within Windows VMs installed on the VMWare host it can also be configured to report directly from ESXi. This configuration helps monitoring software such as Solarwinds or Spiceworks.
Configure ESXi SNMP via CLI (with Prompts):
Download/Install: VMware vSphere CLI 5.1
echo Enter the FQDN of the host:
set /p hostname=
echo Enter the root password:
set /p password=
"C:\Program Files (x86)\VMware\VMware vSphere CLI\bin\vicfg-snmp.pl" --server %hostname% --username %user% --password %password% -c ESX -t 184.108.40.206@161/ESX --enable
"C:\Program Files (x86)\VMware\VMware vSphere CLI\bin\vicfg-snmp.pl" --server %hostname% --username %user% --password %password% -show >> c:\ESXi_SNMP.log