Hyper-V host(s) to your iSCSI SAN

• To verify Jumbo frames have been successfully configured, run the following command from all your Hyper-V host(s) to your iSCSI SAN:

• Ping 10.50.2.35 –f –l 8000

• This command will ping the SAN (e.g. 10.50.2.35) with an 8K packet from the host. If replies are received, Jumbo frames are properly configured.

NICs used for iSCSI communication should have all Networking protocols (on the Local Area Connection Properties) unchecked, with the exception of:

• Manufacturers protocol (if applicable)
• Internet Protocol Version 4
• Internet Protocol Version 6.
• Unbinding other protocols (not listed above) helps eliminate non-iSCSI traffic/chatter on these NICs.

Management NIC should be at the top (1st) in NIC Binding Order. To set the NIC binding order: Control Panel –> Network and Internet –> Network Connections. Next, select the Advanced menu item, and select Advanced Settings. In the Advanced Settings window, select your management network under Connections and use the arrows on the right to move it to the top of the list.

NIC Teaming should not be used on iSCSI NIC’s. MPIO is the best method. NIC teaming can be used on the Management, Production (VM traffic), CSV Heartbeat and Live Migration networks.

TCP Chimney Offload is not supported with Server 2012 software-based NIC teaming, due to TCP Chimney has the entire networking stack offloaded to the NIC. If software-based NIC teaming is not used, however, you can leave it enabled.

• TO SHOW STATUS:

• From an elevated command-prompt, type the following:

• netsh int tcp show global

• (The output should show Chimney Offload State disabled)

• TO DISABLE TCP Chimney Offload:

• From an elevated command-prompt, type the following:

• netsh int tcp set global chimney=disabled