I often get asked how to optimize the HP P4000 Storage Array for a Microsoft Hyper-V Environment and over time, through my engagements, I have pulled together a list of the settings that I tweak.
There is a good whitepaper on the subject at http://tiny.cc/xtoiv entitled “Configuring HP P4000 SAN Solutions with Microsoft Windows Server” which is a must read.
I have broken down my tweaks into 6 categories:
Flow Control
- Flow Control should be enabled globally across the Switch and the NIC ports on the storage nodes. This can be done from the TCP/IP settings page within the CMC console for each node.
- Flow Control is required if the DSM is installed.
- Flow Control needs to be enabled on Host NICs.
Duplex and Speed Settings
- Ensure that appropriate speed e.g. 1000mb full duplex is configured for each NIC and switch port. This should be automatically negotiated.
Jumbo Frames
- Leave Jumbo Frames disabled UNLESS you have demonstrated LARGE Sequential Reads and Writes. If enabling:
- Set Jumbo frames across the dedicated VLAN to 9000k
- Ensure that Server NICs support Jumbo Frames – Max MTU 9014k
- Not all Switches support both Jumbo Frames and Flow Control – if you have to pick between the two choose Flow Control.
ALB
- Use ALB on the storage node and where two dedicated Switches are available. Plug each storage node NIC into each Switch. No special Switch configuration (Spanning-tree, etc.) needs to be performed.
- Truck between two dedicated Switches
- Create a LACP trunk between the two Switches using 2 gig-ports.
Failover Manager
- Install the Failover Manager. Find the Failover Manager Node from within CMC and then add it to the appropriate Management Group.
- Ensure that two Managers exist to maintain Quorum.
Windows Server Specific Settings
- Always install the DSM for Microsoft for increased performance (ensure that flow control is enabled).
- Install the latest version of the MS iSCSI initiator software.
- If dual cards are installed in the server enable MPIO on the iSCSI initiator and then install DSM with MPIO support. From the iSCSI initiator Targets screen manually direct each NIC to the virtual IP of the SAN.
- Create Persistent devices and bind volumes and devices.
- Create registry keys for MaxHoldRequest
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
- Find MaxRequestHoldTime
- Set to Decimal and change value to 600
- Restart the Server
- Set dependencies for specific services
- Hyper-V
- From CMD Prompt: sc config <service name> depend= MSiSCSI
Patrick Lownds