Networking Best Practice for Workload Management

Use nonblocking switches, and set Configure Network Port Speed to a specific value rather than allowing speed negotiation.
Disable the unicast storm control. Most switches have unicast storm control disabled by default. If your switch has unicast storm control enabled, you should disable it on the ports that are connected to Microsoft iSCSI Initiator hosts and targets to avoid packet loss
Use MPIO to manage multiple network connections to the storage in Microsoft iSCSI Initiator. This provides additional redundancy and fault tolerance on Windows Server operating systems
Enable flow control on network switches and adapters. Flow control ensures that a receiver can pace the sender’s speed, and it is important in avoiding data loss
Turn off the spanning tree algorithm for detecting loops. Loop detection introduces a delay in creating a port that can become usable for data transfer, and it can lead to application timeouts
Segregate SAN and LAN traffic. Servers should use dedicated network adapters for SAN traffic. Deploying traffic for Microsoft iSCSI Initiator on a separate network or networks helps minimize network congestion and latency. Additionally, traffic for is more secure when SAN and LAN traffic can be separated by using port-based virtual local area networks (VLANs) or physically separate networks
Use Jumbo Frames if your network infrastructure supports them. Jumbo Frames can be used to allow more data to be transferred with each Ethernet transaction and reduce the number of frames. This larger frame size reduces the overhead on your servers and iSCSI targets. For end-to-end support, each device in the network needs to support Jumbo Frames, including the network adapter and Ethernet switches