Unsolved
This post is more than 5 years old
9 Posts
0
4970
February 17th, 2012 23:00
VNX 5300 Block iSCSI Slow??
Hi,
I have a VNX 5300 which has the following:
8 x 2TB SATA disks
16 x 15K 600GB disks
Vault Drives (Not being used for anything other than Vault)
The 8 x 2TB and 16 x 600GB are all grouped together in a RAID 6 Storage Pool.
I have 3 x VMware hosts which share 3 x 2TB Thin LUN's on this pool (All set to autotier) and connected via Fibre Channel.
I now have a requirement for a single 2008 R2 SP1 Hyper-V host. At the moment I have no spare Fibre cards available so decided to try out 1Gb iSCSI instead. I have a Dell R710 with 128GB of RAM, dual quad core CPU's, using 2 x Broadcom 5709C with the Microsoft iSCSI initiator and EMC PowerPath with MPIO and a 1TB Thin LUN on the VNX 5300. This is currently connected by a single HP Procurve 2910al. This was setup following the attachment guide from EMC. From Unisphere I can see four connections from the host, and the host is set to use Failover Mode 4 ALUA. I can remove a NIC and it all seems to work fine. The MPIO type is Vendor Specific (PowerPath).
The problem with this setup is that the performance is really bad...
I did a very basic test of creating an empty VM and installing Microsoft Server 2008 R2 onto it. Now the R710 itself has 4 local 15K disks in a RAID 10, this can do this task in around 8 minutes. If I do the same test using one of my VMware hosts on a LUN, it can also do this in around 7 minutes. If I use the iSCSI LUN with Hyper-V, it takes 25 minutes plus, and the performance degrades significantly if I start a second one etc...
Now as this is my first iSCSI connection I am trying to understand if this is normal or not?! I can not believe that it is? Looking in Task Manager each NIC never seems to go above 25% utilization. However the strange thing is if I perform a large copy from a server on the network to the VNX LUN (Say 3 x 3GB ISO files), the File Progress window shows a copy speed of 60-70-80 MB a second and the Task Manager NIC utilizations ramp up to 80-90%??
It does seem that the SAN can do more (Hence the VMware test, although I appreciate it is not a fair comparison due to the use of Fibre), but for some reason the connection is stopping me especially for lots of small IO? When looking at the PowerPath MMC I can see the IOPS ramp up to multiple hundreds too...
Things I have attempted so far...
Pushed the iSCSI LUN to the highest tier of storage
Enabled Jumbo Frames (9000) on both NIC's, the switch and set the iSCSI NIC's on the VNX to 9000 MTU
Enabled Flow Control on the switch on all ports used for this (4 for the VNX,and 2 for the server)
Disabled various functions on the NIC's such as TCP Offloading, Receive Side Scaling etc.
Creating the VM with a thick disk
Changed the Jumbo Frames to 4000 everywhere to see if there was fragmentation anywhere etc
Setting the TcpDelAckFrequency=1 registry value on both the NIC's and the EMC location as referenced in a primus article...
Setting the DisableNagle registry value
Disabling one of the iSCSI NIC's (This naturally doubles the utilization in task manager, but still never goes above 50%)...
I think the problem may be that I have nearly all the right things here to try, but perhaps keep getting bad combinations of them?!
Can anyone comment on this (Even if its just to say it does not sound right!!), in particular which settings should I be using/not using etc!


Pdi1
1 Message
0
February 22nd, 2012 08:00
Hi,
Is anything else connected to the 2910al switch besides the VNX and that Hyper-V host?
The 2910al switches aren't very good as it gomes to iSCSI because of the buffer size that this type of switch contains. But this is depending on the number of iSCSI targets and initaitors you have connected to it. We've had serveral performance issues with it and after turning to another type of switch the performance was back.
For a good performing iSCSI HP switch i'd recommend the ProCurve 3500 or 3800 series...
I do not think that this has anything to do with the VNX.
kelleg
6 Operator
•
4.5K Posts
0
February 24th, 2012 15:00
On the Windows host you get TcpDelayAckFrequency - should be TcpAckFrequency (emc150702) - this only affects Read performance but it can have a fairly dramatic affect if it's not set.
On a server that runs Windows Server 2003 SP1 or later or Windows 2008 including R2, follow these steps:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces
The interfaces will be listed underneath by automatically generated GUIDs like {064A622F-850B-4C97-96B3-0F0E99162E56}.
a. Check the IPAddress or DhcpIPAddress parameters to determine whether the interface is used for iSCSI traffic. If not, skip to the next interface.
b. On the Edit menu, point to New, and then click DWORD value.
c. Name the new value TcpAckFrequency, and assign it a value of 1.
Glen