Friday, 20 April 2012

ESXi 5 EqualLogic best practices.

If you are using Raw Device Mapped (RDM) disks in your VM's, make sure the pathing for that is changed to RR and IOPs 3 as well.  (MEM would also set this connections up properly as well)
Other common tweaks are disable DelayedACK  (its in the iSCSI initiator properties) and disable Large Receive Offload (LRO)
Within VMware, the following command will query the current LRO value.

# esxcfg-advcfg -g /Net/TcpipDefLROEnabled
To set the LRO value to zero (disabled):

# esxcfg-advcfg -s 0 /Net/TcpipDefLROEnabled
NOTE: a server reboot is required.

Info on changing LRO in the Guest network.

ESXI v5.0 should also have the Login Timeout changed to 60 seconds.  (default is 5).  However, you have to be at build 514841 or better.  
See VMware KB 2007680 kb.vmware.com/.../2007680

One more common enhancement that gets missed often is creating a virtualized SCSI adapter for each VMDK (or RDM) in each VM.  (Up to 4x controllers)     If you look in the VM settings, each VMDK/RDM shows a "Virtual node"  
It will say 0:0, for first drive, then 0:1, 0:2, etc...   Shutdown the VM, change the other VMDK/RDMs from 0:1 to 1:0, then 0:2 to 2:0 and so on.   This will tell ESX to create new SCSI controllers for each disk.  Really helps with Exchange/SQL/Sharepoint.   Things that have databases and logs or fileservers that have multiple VMDKs/RDMs
*************************************************************************************
*** Script to change EQL volumes to RR and set the IOPs to 3 in ESXi v5.0. ****
*************************************************************************************
This is a script you can run to set all EQL volumes to Round Robin and set the IOPs value to 3.  (Datastores and RDMs)

#esxcli storage nmp satp set --default-psp=VMW_PSP_RR --satp=VMW_SATP_EQL ; for i in `esxcli storage nmp device list | grep EQLOGIC|awk '{print $7}'|sed 's/(//g'|sed 's/)//g'` ; do esxcli storage nmp device set -d $i --psp=VMW_PSP_RR ; esxcli storage nmp psp roundrobin deviceconfig set -d $i -I 3 -t iops ; done
After you run the script you should verify that the changes took effect.

#esxcli storage nmp device list

Thursday, 12 April 2012

Equallogic ASM/ME - Replication partner Not Available

ASM/ME reports Replication Partner Not Available. Even though manual replication works.

Issue was caused by the inability to access the VSS-CONTROL LUN on the replication partner. In my case the vssadmin username and password where correctly specified but the iSCSI initiator refused the login to the VSS LUN. The workaround is to set the VSS access at the group level to unrestricted while Dell investigate.


UPDATE. - Workaround from Dell PS.

Highlight the VSS-Control Volume and click connect you get an Advance button, Click it and you will get a pop up window and you should see your chap credentials there.
Enter you chap Credentials on both the hosts and that should resolve the issue.





Wednesday, 4 April 2012

Optimal iSCSI NIC settings

This can help eliminate TCP retransmits between EQL and the host.Find the 2x iSCSI NICs in the registry, only change this for NICs connecting to iSCSI storage.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces


Create two new DWORDS



TcpAckFrequency = 1
TcpDelAckTicks = 0

Restart the server.

Tuesday, 3 April 2012

Dell Life cycle controller crashes with Hardware Exeception

When you press F10 to access the Dell Life Cycle controller it crashes with this error.


!!!! x64 exception type - 00000000000000000000000D !!!!


This happened to me after using the life cycle controller to update all the firmware within the server.


The solution




Monday, 26 March 2012

vCenter server service won't start event id 1000

I was at a customer the other day. We needed to reboot the VC VM the customer hadn't done this in ages, and typically , after the reboot the vCenter server service wouldn't start, I check the eventvwr and found event id 1000. After some Googling I would appear that something was already running on port 80. I checked the VPXA logs in this location %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs\ and found this error:


[VpxdReverseProxy] Failed to create http proxy: Resource is already in use: Listen socket: :80 


Futher Googling suggested either IIS has been installed, or the SQL reporting service was installed. Some reports suggest that WinRM takes port 80 but this was later found to be incorrect.


I even tried upgrading the customer the vCenter 4.1 U2 this still did not work.


NETSTAT -ANO reported that java.exe was taking the port so I presumed that Tomcat was stuffed.


Fix: In the end I thought I would stop some services to see if that was the cause. Sure enough when I stopped VMware Update Manager, port 80 was then free. I set the VUM service to delayed start and this sorted the issue. A couple of reboots proved this worked! What I can't work out is that know one else had blogged this issue.


Troubleshooting.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015101
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003971

IOP values for harddisks

Device Type IOPS Interface Notes
5,400 rpm SATA drives HDD 50-80 IOPS SATA 3 Gb/s
7,200 rpm SATA drives HDD 75-100 IOPS SATA 3 Gb/s
10,000 rpm SATA drives HDD 125-150 IOPS SATA 3 Gb/s
10,000 rpm SAS drives HDD 140 IOPS SAS SAS is full duplex
15,000 rpm SAS drives HDD 175-210 IOPS SAS SAS is full duplex

In a mirrored configuration:
Disk IOPS = Read IOPS + (2 * Write IOPS)
In a parity (RAID5) configuration:
Disk IOPS = Read IOPS + (4 * Write IOPS)

Example calculations

Now let's look at an example. If you estimate that you need to support 40 Read IOPS (40 reads/sec) and 80 Write IOPS (80 writes/sec).
If you want to use a mirrored configuration of drives:
Disk IOPS = Read IOPS + (2 * Write IOPS) = 40r/s + (2 * 80w/s) = 200 Disk IOPSUsing 7200 rpm drives, you need: 200 / 50 = 4 disk drives
Using 10k rpm drives, you need: 200 / 130 = 2 disk drives (always round up)
If you want to use a parity (RAID5) configuration of drives:
Disk IOPS = Read IOPS + (4 * Write IOPS) = 40r/s + (4 * 80w/s) = 360 Disk IOPSUsing 7200 rpm drives, you need: 360 / 50 = 8 disk drives (always round up)
Using 10k rpm drives, you need: 360 / 130 = 3 disk drives

An excellent article on how how RAID levels effect IOPS 
http://skabelka.com/node/125
http://sudrsn.wordpress.com/2010/12/25/iops-raid-penalty-and-workload-characterization/

Monday, 27 February 2012