User Manual
Table Of Contents
- Mellanox WinOF VPI User Manual
- Table of Contents
- List of Tables
- Document Revision History
- About this Manual
- 1 Introduction
- 2 Firmware Upgrade
- 3 Driver Features
- 3.1 Hyper-V with VMQ
- 3.2 Header Data Split
- 3.3 Receive Side Scaling (RSS)
- 3.4 Port Configuration
- 3.5 Load Balancing, Fail-Over (LBFO) and VLAN
- 3.6 Ports TX Arbitration
- 3.7 RDMA over Converged Ethernet (RoCE)
- 3.8 Network Virtualization using Generic Routing Encapsulation
- 3.9 Differentiated Services Code Point (DSCP)
- 4 Deploying Windows Server 2012 and Above with SMB Direct
- 5 Driver Configuration
- 6 Performance Tuning
- 7 OpenSM - Subnet Manager
- 8 InfiniBand Fabric
- 8.1 Network Direct Interface
- 8.2 part_man - Virtual IPoIB Port Creation Utility
- 8.3 InfiniBand Fabric Diagnostic Utilities
- 8.3.1 Utilities Usage
- 8.3.2 ibdiagnet
- 8.3.3 ibportstate
- 8.3.4 ibroute
- 8.3.5 ibdump
- 8.3.6 smpquery
- 8.3.7 perfquery
- 8.3.8 ibping
- 8.3.9 ibnetdiscover
- 8.3.10 ibtracert
- 8.3.11 sminfo
- 8.3.12 ibclearerrors
- 8.3.13 ibstat
- 8.3.14 vstat
- 8.3.15 osmtest
- 8.3.16 ibaddr
- 8.3.17 ibcacheedit
- 8.3.18 iblinkinfo
- 8.3.19 ibqueryerrors
- 8.3.20 ibsysstat
- 8.3.21 saquery
- 8.3.22 smpdump
- 8.4 InfiniBand Fabric Performance Utilities
- 8.4.1 ib_read_bw
- 8.4.2 ib_read_lat
- 8.4.3 ib_send_bw
- 8.4.4 ib_send_lat
- 8.4.5 ib_write_bw
- 8.4.6 ib_write_lat
- 8.4.7 ibv_read_bw
- 8.4.8 ibv_read_lat
- 8.4.9 ibv_send_bw
- 8.4.10 ibv_send_lat
- 8.4.11 ibv_write_bw
- 8.4.12 ibv_write_lat
- 8.4.13 nd_write_bw
- 8.4.14 nd_write_lat
- 8.4.15 nd_read_bw
- 8.4.16 nd_read_lat
- 8.4.17 nd_send_bw
- 8.4.18 nd_send_lat
- 8.4.19 NTttcp
- 9 Software Development Kit
- 10 Troubleshooting
- 11 Documentation
- Appendix A: Windows MPI (MS-MPI)
- Appendix B: NVGRE Configuration Scrips Examples
Rev 4.60
Mellanox Technologies
20
Step 3. In this step, you can perform the following functions:
• If you choose the HW Defaults option, the port protocols will be determined according to the NIC’s
hardware default values.
• Choose the desired port protocol for the available port(s). If you choose IB or ETH, both ends of the
connection must be of the same type (IB or ETH).
• Enable Auto Sensing by checking the AUTO checkbox. If the NIC does not support Auto Sensing,
the AUTO option will be grayed out.
3.5 Load Balancing, Fail-Over (LBFO) and VLAN
Windows Server 2012 and above supports load balancing as part of the operating system. Please
refer to Microsoft guide “NIC Teaming in Windows Server 2012” following the link below:
http://social.technet.microsoft.com/wiki/contents/articles/14951.nic-teaming-in-windows-server-
2012.aspx
For other Operating Systems such as: Windows Server 2008 R2, please refer to the sections
below.
3.5.1 Adapter Teaming
Adapter teaming can group a group of ports inside a network adapters or a number of physical
network adapters into virtual adapters that provide the fault-tolerance and load-balancing func-
tions. Depending on the teaming mode, one or more interfaces can be active. The non-active
interfaces in a team are in a standby mode and will take over the network traffic in the event of a
link failure in the active interfaces. All of the active interfaces in a team participate in load-bal-
ancing operations by sending and receiving a portion of the total network traffic.
3.5.1.1 Teaming (Bundle) Modes
1. Fault Tolerance
Provides automatic redundancy for the server’s network connection. If the primary adapter
fails, the secondary adapter (currently in a standby mode) takes over. Fault Tolerance is the
basis for each of the following teaming types and is inherent in all teaming modes.
2. Switch Fault Tolerance
Provides a failover relationship between two adapters when each adapter is connected to a
separate switch.
3. Send Load Balancing
Provides load balancing of transmit traffic and fault tolerance. The load balancing performs
only on the send port.
4. Load Balancing (Send & Receive)
Provides load balancing of transmit and receive traffic and fault tolerance. The load balancing
splits the transmit and receive traffic statically among the team adapters (without changing
the base of the traffic loading) based on the source/destination MAC and IP addresses.
If you choose AUTO, the current setting will indicate the actual port settings: IB or
ETH.