Best practice iSCSI server configuration with hyperv (Windows 2012 and 2016)

Hi,

I have always used good common practices, but I have found some options that I do not know and I would like the help to confirm with you.

1 - Disable all NIC options, leaving only IPV4;
2 - Disable the options to register in DNS and Netbios;
4 - Set MTU to 9000 in advanced settings;
5 - Disable VMQ in the advanced settings;

New information I found. Are they really necessary?

Click on the Advanced tab under the NIC properties and set the following attributes' values ​​to Disabled:

- IPv4 Checksum Offload
- IPv4 TSO Offload
- Large Send Offload V2 (IPV4)
- Large Send Offload V2 (IPV6)
- Offload IP Options
- Offload tagged traffic
- Offload TCP Options
- Recv Segment Coalescing (IPV4)
- Recv Segment Coalescing (IPV6)
- TCP Checksum Offload (IPv4)
- TCP Checksum Offload (IPv6)
- UDP Checksum Offload (IPv4)
- UDP Checksum Offload (IPv6)

New Dell recommendation information

https://downloads.dell.com/manuals/all-products/esuprt_software/esuprt_it_ops_datcentr_mgmt/general-...

Note: Recommended registry settings apply to all versions of Windows Server unless directly specified.
HKLM \ SYSTEM \ CurrentControlSet \ Services \ mpio \ Parameters
- PDORemovePeriod
- PathRecoveryInterval
- UseCustomPathRecoveryInterval
etc...

Note: The registry settings in Table 6 only apply to Windows Server 2012 or later
HKLM \ SYSTEM \ CurrentControlSet \ Services \ mpio \ Parameters
- DiskPathCheckDisabled
- DiskPathCheckInterval

I do not understand what you mean by (single-path). Should these settings only be applied for single-path communication? If I have use (multi-path) should not we configure?

This appendix contains recommended changes for iSCSI initiators. These changes apply to single-path and MPIO configurations that use iSCSI to connect to SC Series storage.
HKLM \ SYSTEM \ CurrentControlSet \ Control \ Class \ {4D36E97B-E325-11CE-BFC1-08002BE10318} \ <Instance Number> \ Parameters

HKLM \ SYSTEM \ CurrentControlSet \ Services \ Tcpip \ Parameters \ Interfaces \ <SAN Interface GUID>
- TcpAckFrequency
- TcpNoDelay

Should this setting be used only for 10GbE configuration?

- Enable RFC1323 timestamps (TCP High Performance Extensions)
netsh int tcp set global timestamps = enabled
HKLM \ SYSTEM \ CurrentControlSet \ Services \ TCPIP \ Parameters \ Tcp1323Opts

- Disable Nagle's Algorithm
- Disable NIC Interrupt Modulation

For Windows 2012 and R2 you need to apply KBs. What to say that for 2016 does not need? Just ensure that all the updates have been installed?

Recommended updates and hotfixes for Windows Server 2012
R2 / 2016 Microsoft publishes updates for Windows Server 2012 R2 and Windows Server 2016 cumulatively. Any updates for storage-related files are included in the monthly cumulative updates. Apply the latest monthly cumulative update from Microsoft to ensure that the storage-related files msdsm.sys, mpio.sys, msiscsi.sys,
and storport.sys stay current.
See the Microsoft Update Catalog at
 https://www.catalog.update.microsoft.com/Home.aspx to locate specific KB downloads.

Thank you.

0 Kudos
1 Reply
Highlighted
3 Argentum

Re: Best practice iSCSI server configuration with hyperv (Windows 2012 and 2016)

Hello Sandro Silva Alves,
Where did you find these recommendations?

1 - Disable all NIC options, leaving only IPV4;
2 - Disable the options to register in DNS and Netbios;
4 - Set MTU to 9000 in advanced settings;
5 - Disable VMQ in the advanced settings;

Setting the MTU of an interface to 9000 if the network is set to 1500 would not be recommended. I checked the current MPIO and Hyper-V documentation, and did not find these shown.

If my answer was helpful, please click: Kudos
Forum Member since 2012
#iwork4Dell
0 Kudos