After I solved this problem, then I’ve enabled all offloading feature, mode interruption, RSS and almost everything, it still worked like a champ, 2 paths gives me something close to 220MB/s which is enough for my Veeam backup purpose.

I’ve no problem using MPIO within VM and IOMeter went up to 450MB/s and NO TCP retransmits. Also vmkping –d –s 8000 works fine, so PowerConnect 5448 isn’t likely to be the problem.

Have you tested Windows 2008 R2 with HIT Kit installed and directly connected to EQL PS6000 array? Do you get only 1 link? (ie, MPIO doesn’t work like my setup?)

I did want to note that your tcp retransmits may be caused by the 5448 switch. I have found that the max packet size I can pass is 8,750. ping -f -l 9000 sets the don’t fragment bit and the ping will not be returned if it can’t pass that packet.

I’ve also tried HBA mode with MPIO as well, unfortunately, the result is the same. (ie, only one NIC being ultilized, the other just sits still).

May I asked how did you get this problem solved? or do you mean you that you were only having poor performance, but MPIO is working correctly?

Thanks and Merry Xmas!

If you open a command prompt and type ‘route print’, you can see what routes are available for windows. If after you configure the IP addresses on the iSCSI HBAs and you’re able to see targets, then you shouldn’t have to configure IP addresses within windows on the adapters.

Configuring Windows network
Start -> Control Panel -> Network and Sharing Center -> Change Adapter settings -> Right click appropriate adapter -> Properties -> Select IPv4 or IPv6 -> Properties and change IP address from there.

BACS – You’re correct, there are four, I only listed two to shorten the post a little.

Open BACS -> Device Management -> Under SCSI Controllers -> Select the appropriate adapter(s) -> Under iSCSI Management to the right -> Change IPv4 DHCP to Disable and change the ip address.

When configuring the 5709C as iSCSI HBA, windows routing is not aware of those ip addresses; at least within my configuration, windows networking was not aware. Only the Microsoft iSCSI Initiator knew about the ip addresses on the iSCSI HBAs. You should also be able to ping the iSCSI HBAs from within windows.

Btw, could you tell me more how to configure/input IP address for

a. Windows Networking (iSCSI Network)
b. BACS SCSI Controllers (how come only 2? I though 4 NICs)

I thought I only need to configure 5709C as iSCSI HBA and assign IP to the HBA, so no need to go to Network and configure the NIC again. No?

Thanks.

a. iSCSI Target Equallogic: PS4000XV 1 array member only, loaded with Latest Firmware 5.0.2 and HIT 3.4.2, configured as RAID50.

b. iSCSI Initiator Server: Poweredge R815, W2K8 R2, two quad-port Broadcom 5709C, I do not use the Microsoft iSCSI initiator, therefore; each iSCSI adapter in BACS has an IP address for the iSCSI network.

c. iSCSI Initiators: Using one quad-port Broadcom 5709C

d. Switch: Enterasys N1 – Flow control enabled, Jumbo, iScsi traffic on separate VLAN.

I seem to have made a breakthrough on my performance issues. Using IOMeter with the following settings, 8192 sectors, 64 Outstanding I/Os, 32K 75% Random Read; I was able to get 312MB/s or 2500Mb/s which is satisfying for me.

What I finally figured out was that I didn’t have my MTU set to 9000 on the iSCSI devices in BACS. I finally configured all iSCSI devices, all NICS (even on internal network), with the highest possible settings for MTU, RSS queues, Flow Control – Rx & Tx Enabled, Receive Buffers – 2000, Transmit Buffers – 2500.

I also figured out that I do not have to alter the Microsoft MCS policies at all; as I configured the MPIO settings within the Dell Equallogic Remote Setup Wizard. All iSCSI connects apply this setting which is LQD.

Since I did not use the Microsoft Initiator, I had to input an IP address to the NICs through the Windows Network Connections.

Windows Networking (iSCSI Network)
LAN 1 192.168.200.xxx
LAN 2 192.168.200.xxx
LAN 3 192.168.200.xxx
LAN 4 192.168.200.xxx

BACS SCSI Controllers
0000 – iScsi adapter 192.168.200.xxx
0001 – iScsi adapter 192.168.200.xxx

Once I configured all parameters, no more microsoft in the mix. My CPU load went down by 70% on some test. IO tests proved to be much faster.

I hope this helps. I’ve been working two weeks straight on this setup.

I’ve updated my blog today, see the last section where it says
More Update (October 25, 2010)

Could you tell me more your setup please? Is it W2K8 R2, PS6000? etc. Thanks.