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
60
7 OpenSM - Subnet Manager
OpenSM v3.3.11 is an InfiniBand Subnet Manager. In order to operate one host machine or more
in the InfiniBand cluster., at least one Subnet Manger is required in the fabric.
OpenSM can run as a Windows service and can be started manually from the following directory:
<installation_directory>\tools. OpenSM as a service will use the first active port, unless it
receives a specific GUID.
OpenSM can be registered as a service from either the Command Line Interface (CLI) or the
PowerShell.
The following are commands used from the CLI:
To register it as a service execute the OpenSM service:
To start OpenSM as a service:
To run OpenSM manually:
For additional run options, enter:
“opensm.exe -h”
The following are commands used from the PowerShell:
To register it as a service execute the OpenSM service:
To start OpenSM as a service run:
Notes
• For long term running, please avoid using the '-v' (verbosity) option to avoid exceeding
disk quota.
• Running OpenSM on multiple servers may lead to incorrect OpenSM behavior.
Please do not run more than two instances of OpenSM in the subnet.
Please use the embedded OpenSM in the WinOF package for testing purpose and small
cluster. Otherwise, we recommend using OpenSM from FabricIT EFM™ or UFM® or
MLNX-OS®.
sc create OpenSM binPath= "c:\Program Files\Mellanox\MLNX_VPI\IB\Tools\opensm.exe
-service" start= auto
sc start OpenSM
opensm.exe
New-Service –Name "OpenSM" –BinaryPathName "`"C:\Program Files\Mella-
nox\MLNX_VPI\IB\Tools\opensm.exe`" --service -L 128" -DisplayName "OpenSM" –
Description "OpenSM for IB subnet" -StartupType Automatic
Start-Service OpenSM1