Bert Zefat's Tech Blog

Go to Virtual Machine > Install VMware Tools (or VM > Install VMware Tools).

sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom or sudo mount /dev/sr0 /mnt/cdrom
tar xzvf /mnt/cdrom/VMwareTools-x.x.x-xxxx.tar.gz -C /tmp/
cd /tmp/vmware-tools-distrib/
sudo ./vmware-install.pl -d

sudo reboot

Tags: ESX, Linux, VMware, vSphere by Bert Zefat
No Comments »

While opening a console for any virtual machine from one particular workstation, the console display is not sized correctly.

To resolve this, you will have to disable Display Scaling.

1. Right click the vSphere Client icon and select Properties
2. Click Compatibility
3. Check box, “Disable display scaling on high DPI Settings”.
4. Apply the settings
5. Reload the vSphere Client.

The console session should populate the full screen.

Tags: ESX, VMware, vSphere by Bert Zefat
No Comments »

Today I encountered the issue that I could not run a SureBackup from an ESX server. Although the ESX server (vmkernel) could ping the Veeam Backup server and coudl connect tot the NFS service (Port 111 and 6161).

I finally saw that there was also a Service NFS running. Disabling this service did not help.

At last i just removed the “Service fro NFS” from the Windows 2012 R2 Storage server.

A reboot is needed AND…. the Surebackup run.

So. If you have a Windows Storage server and you install Veeam Backup and Replication on it. Remove the Service for NFS from it to make vPower NFS work.

Tags: ESX, Microsoft, VEEAM, VMware, vSphere, Windows by Bert Zefat
No Comments »

Windows:

echo off
if "%1" == "freeze" goto doFreeze
goto doThaw
:doFreeze
call c:\windows\pre-freeze-script.bat
goto EOF
:doThaw
call c:\windows\post-thaw-script.bat
:EOF

Linux:

For Linux VMs, the scripts should be named

     /usr/sbin/pre-freeze-script

     /usr/sbin/post-thaw-script

Both must have 0755 permissions so that they are executable, and should be owned by root.

Veeam:
Make sure that ““Enable VMware Tools quiescence” is enabled, cauusing the scripts to be call to.

Tags: ESX, Linux, Microsoft, VEEAM, VMware, vSphere by Bert Zefat
No Comments »

Tags: Blade Systems, ESX, HP by Bert Zefat
No Comments »

Start by identifying the server whose VMkernel may be locking the file.

# vmkfstools -D /vmfs/volumes/UUID/VMDIR/LOCKEDFILE.xxx

 > Hostname vmkernel: gen 532, mode 1, owner xxxxxxxx-xxxxxxxx-xxxx- zzzzzzzzzzzz mtime xxxxxxxxxx]

zzzzzzzzzzzz gives the MAC adres of the server locking the file.

# lsof | grep -i LOCKEDFILE.xxx

OR

# vmkvsitools lsof | grep LOCKEDFILE.xxx

You see output similar to:

11773 vmx 12 46 /vmfs/volumes/Datastore_Name/VirtualMachineName/ VirtualMachineName-flat.vmdk

kill -9 PID (in the above case 11773)

Tags: ESX, VMware by Bert Zefat
No Comments »

I love CLI (Command Line Interface).

It gives you control…

So therefore if I work with ESX and snapshotting:

# vim-cmd vmsvc/getallvms
To get all VM’s andthier ID’s

# vim-cmd vmsvc/snapshot.create [ID] [Name]
To create a snapshot

# vim-cmd vmsvc/get.snapshotinfo [ID]
To get full information on snapshots on the VM

# vim-cmd vmsvc/snapshot.revert [ID]
To revert to a snapshot

# vim-cmd vmsvc/snapshot.remove [ID]
To remove a snapshot

# vim-cmd vmsvc/snapshot.removeall [ID]
To remove all snapshots from the VM

Tags: ESX, VMware, vSphere by Bert Zefat
No Comments »

You need a HP ESXi image to run the command

> /opt/hp/hpssacli/bin/hpssacli

Then you have following options:

Tags: ESX, HP, Storageworks, VMware by Bert Zefat
No Comments »

While re-starting a ESXi 5.1 cluster. It came back, but one host did not join the cluster.

Adding it to the cluster (or at fisrt during a “connect”) it gave me the following error:

vmodl.fauly.hostcommunication 

Removing and adding it again to the cluster did not work. Disabling and Enabling HA did not do the trick.

Fix:
As it was ESXI 5.1 you connect to it (console or SSH) and type

services.sh restart

Now you can add the node again to the Cluster (remember to Enable HA again)

Tags: ESX, VMware by Bert Zefat
No Comments »

Upload the HPPP_x.xx.xx_Linux_X64.rpm to the vMA (/tmp) (with winSCP of FASTscp)

> sudo -s
> rpm -i hppp-linux-1.02.028-1.x86_64.rpm

Starting Power Protector: HP-HPPP[ OK ]

Check if the service is indeed listening on it’s ports:
> netstat -tanp | grep LISTEN
tcp 0 0 0.0.0.0:4679 0.0.0.0:* LISTEN 7813/HP-HPPP
tcp 0 0 0.0.0.0:4680 0.0.0.0:* LISTEN 7813/HP-HPPP
tcp 0 0 :::22 :::* LISTEN 2082/sshd

Default the vMA does not have ports 4679 (http) en 4680 (https) open

Configure communication between HPPP and the HP Network Module:
> sudo -s
> iptables -I OUTPUT -p tcp –dport 80 -j ACCEPT
> iptables -I INPUT -p tcp –dport 4679 -j ACCEPT
> iptables -I INPUT -p tcp –dport 4680 -j ACCEPT
> iptables -I INPUT -p udp –dport 4679 -j ACCEPT
> iptables -I INPUT -p udp –dport 4680 -j ACCEPT
> iptables -I OUTPUT -p udp –dport 4679 -j ACCEPT
> iptables -I OUTPUT -p udp –dport 4680 -j ACCEPT

> service iptables save
> iptables-save

Now you can connect with a web-browser.
Also the commi=unication between the vMA HPPP and the UPS is restored.

Tags: ESX, VMware, vSphere by Bert Zefat
No Comments »