Entries Tagged as 'VMware'

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

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03571575&lang=en&cc=us&taskId=101&prodSeriesId=3664763&prodTypeId=12169

DESCRIPTION

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.

SCOPE

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

RESOLUTION

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.

WORKAROUND

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
[Download]

Running VMware vSphere 4 on HP LeftHand P4000 SAN Solutions
[Download]

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

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

3PAR Utility Storage with VMware vSphere
[Download]

HP P2000 Software  Plug-in for VMware VAAI
[Download]

HP 3PAR Storage and VMware vSphere 5 best practices
[Download]

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

Recommended BIOS Settings on HP

HP Power Profile Custom Allows to enable custom Power settings specific for vSphere
HP Power Regulator OS Control Mode Hands over the Power Management to vSphere. The other options give this control to the server itself.
Redundant Power Supply Mode High Efficiency Mode (Auto) By default (Balanced Mode), the server uses all installed PSU’s. This might look like the most efficient use, but the more power is drawn from a PSU, the more efficient it operates. The less power you draw from a PSU, the more gets lost to keep the PSU working. Thus, it is best to use the minimum amount of PSU’s so they deliver the highest possible output. The remaining PSU’s are placed in standby. This settings does not affect redundancy as the standby PSU’s jump in as soon as an active one fails. By using the ‘Auto’ mode, the active PSU’s are chosen based on the server’s serial number (odd or even number = odd or even PSU numbers). This makes sure that all power circuits in the racks are evenly used.
Minimum Processor Idle Power State C3 State Needed for vSphere Dynamic Voltage and Frequency Scaling (DVFS). Allows vSphere to halt unneeded cores.
DIMM Idle Power Saving Mode Enabled DIMMs can put themselves into Low Power mode when not used. This will save some power if not all memory is used on the host.
ASR Status Disabled ASR monitors an agent running in the Service Console. When this does not respond within 10 minutes, the host is rebooted. However, if the agent fails or the Service Console becomes sluggish (even though the VM’s are perfectly fine), ASR will detect this as a system hang and will reboot the server. Furthermore, in case of a PSOD, ASR will reboot the server as well. This reboot might cause a loss of some logfiles.
Automatic Power-On Disabled If set to enabled, the server will power-on as soon as AC Power is available. When set to disabled, power is restored to its previous state when AC Power is available.
Virtual Install Disk Disabled This Virtual Install Disk only contains drivers for Microsoft Windows Operating system.

How do I know if VAAI is enabled on ESX/ESXi?

To determine if VAAI is enabled within ESX/ESXi:

  • In the vSphere Client inventory panel, select the host.
  • Click the Configuration tab, and click Advanced Settings under Software.
  • Check that these options are set to 1 (enabled):
DataMover/HardwareAcceleratedMove
DataMover/HardwareAcceleratedInit

VMFS3/HardwareAcceleratedLocking

Note: These options are enabled by default.

To determine if VAAI is enabled service console in ESX or the RCLI in ESXi, run the following commands and ensure that the value is 1:

# esxcfg-advcfg -g /DataMover/HardwareAcceleratedMove
# esxcfg-advcfg -g /DataMover/HardwareAcceleratedInit
# esxcfg-advcfg -g /VMFS3/HardwareAcceleratedLocking

Can I check the VAAI status from the command line?
To check VAAI status, run the command:

# esxcfg-scsidevs -l | egrep “Display Name:|VAAI Status:”

EVA VAAI compliant?

Question that are thrown to me are:

Is the EVA VAAI compliant?
The EVA will be “vStorage APIs for Array Integration” (in short VAAI) compliant. It is NOT compliant at the moment.

Will it be in the next firmware release. Probably NOT.

The next… Probably YES. So we will have to wait, but until then the EVA should be fast enough by it’s own.

More information when available.

A “Poor man’s SAN” for ESX vSphere with VSA

Just thinking on how to make a “Poor man’s SAN” I came across this this idear:

Take 2 servers with enough disk space available and the ability to expand when needed. Install on both systems ESXi vSphere. With this installed, create on your ESX hosts VM’s with the VSA you can buy from HP.
The VSA is the same software that is running on the P4000 from HP, but now running inside your vSphere environment. The licenses go up to 10TB.
Doing so on both ESX hosts you can setup you SAN/iQ management environment and also your (first) cluster.

Make sure you have enough managers running to keep your data available in case one of your ESX hosts dies.

Now you have created your own iSCSI “P4000” like SAN. You can now connect to it from your production ESX vSphere environment.

One thing. Support from HP is NOT included.
(drawing will follow)

VAAI support with SAN/iQ 9.0 on P4000

SAN/iQ vor P4000 has now support fot VMware VAAI vStorage offloads — Full copy, Block Zeroing, and Hardware Assisted Locking for faster VM deployment and less load on ESX server.

Meaning more VM’s can be run on the same environment. Till SAN/iQ 8.1 is was recommended to a total of 16 VM’s, now up t 50 VM’s should be supported. I have not been able to test this theorie, but this is stated by HP at this moment.

To upgrade to SAN/iQ 9.0 your system should run SAN/iQ 8.1.

SQL on vSphere link collection

VMware released some whitepapers about running MS SQL Server on VMware vSphere.

The VMware communities site has a spot called VIOPS where you can see posts from members in the community about recently posted documents. There are some nice documents available about virtualizing SQL server 2008 on vSphere 4.1.

There are a couple on SQL Server, for each product a “best practices document” and an “availability and recovery options” document.

Microsoft SQL Server on VMware – Best Practices Guide

Microsoft SQL Server on VMware – Availability and Recovery Options

Performance and Scalability of Microsoft® SQL Server® on VMware vSphere™ 4

Design, Deploy & Optimize SQL Server on vSphere