Entries Tagged as 'vSphere'

Installing VMware Tools in a Linux VM

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

vSphere Client Console Does Not Display Full Screen

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.

Cannot mount vPower NFS VEEAM

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.

VMware Backup Pre- And Post-Commands

Version of ESX Custom quiescing script directory
ESX/ESXi 3.5 Update 1 or earlier
ESX/ESXi 3.5 Update 2 or later
C:\Program Files\VMware\VMware Tools\backupScripts.d\
ESX/ESXi 4.x C:\Windows\backupScripts.d\
ESXi 5.0
C:\Program Files\VMware\VMware Tools\backupScripts.d\
ESXi 5.1 and ESXi 5.5


To create a sample wrapper script,  you can create a text file and name it vcb.bat.
echo off
if "%1" == "freeze" goto doFreeze
goto doThaw
call c:\windows\pre-freeze-script.bat
goto EOF
call c:\windows\post-thaw-script.bat


For Linux VMs, the scripts should be named



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

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

Working with Snapshots on the ESXi CLI

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


Installing HPPP on vMA

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* LISTEN 7813/HP-HPPP
tcp 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.

VMRC Console has disconnected – attempting to reconnect.

If the issue persists, end any vmware-vmrc.exe processes in the Windows Task Manager:

  1. Close all vSphere Client sessions.
  2. Open Windows Task Manager.
  3. Search for any vmware-vmrc.exe processes and end the process.
  4. Start the vSphere Client and connect to the host directly or to vCenter Server.

HP 4400/6400/8400 Enterprise Virtual Array and HP EVA P6000 Storage controller software version XCS 11001000 Inactive

After working at a customer site and running into a problem expanding an EVA6400 (SPOF on a disk, so I/O controllers not code loading). I heard from support of HP there is a new XCS code for the EVA x400 series and P600 range.

Below document ID: c03571575

Release Date: 2012-11-13
Last Updated: 2012-11-13



A critical issue has been discovered to potentially occur on HP Enterprise Virtual Array (EVA) 4400/6400/8400 and HP EVA P63x0/65×0 systems running controller software version XCS 11001000. The potential for this issue is only on systems running software version XCS 11001000 and that are using VAAI functionality enabled on VMware ESX 4.1/ESX 5.x hosts.

NOTE: Version 11001000 is the only active XCS controller software with this issue; however, the potential for this issue also exists in the inactive XCS versions 10100000 and 11000000.

To ensure current and future systems will function as expected with VAAI enabled, XCS controller software version 11001000 is being retired and will be listed as Inactive in the HP controller software support matrix. Contact your HP Services representative for more information on the issue and to schedule an upgrade to the latest controller software that resolves this issue.


This issue affects HP EVA4400/6400/8400 and HP EVA P63x0/P65x0 arrays that are running XCS 11001000.


Contact your HP Services representative for more information on the issue and to schedule an upgrade to XCS version 11001100. The VAAI functionality must be immediately disabled until the controller software is upgraded to 11001100.


Disable VAAI functionality on all VMware hosts that access the HP EVA array until the controller software has been upgraded to XCS 11001100.

UPDATE 16-11-2012:

The XCS code be found -> https://h20392.www2.hp.com/portal/swdepot/displayProductsList.do?category=NAS

Best practices

HP Enterprise Virtual Array (EVA) family with VMware vSphere 4.0, 4.1 and 5.0 Best practices

Running VMware vSphere 4 on HP LeftHand P4000 SAN Solutions

Best Practices for deploying VMware and vSphere 4 with VMware High Availability and
Fault Tolerance on HP P4500 Multi-Site SAN cluster

HP P4000 LeftHand Solutions with VMware vSphere Best Practices (incl. vSphere 5)

3PAR Utility Storage with VMware vSphere

HP P2000 Software  Plug-in for VMware VAAI

HP 3PAR Storage and VMware vSphere 5 best practices

IOP’s aanpassingen Alua Aware storage

Alle LUN’s standaard op Round-Robin zetten:

esxcli storage nmp satp set --default-psp VMW_PSP_RR --satp VMW_SATP_ALUA

Op alle LUN’s welke op Round-Robin staan de IOP’s op 1 zetten:

for i in `esxcli storage nmp device list | grep naa.600` ; 
do esxcli storage nmp psp roundrobin deviceconfig set -t iops -I 1 -d $i; done