--- /dev/null
+' WIX CustomActions used in the WinOF (Windows OpenFabrics) Release\r
+' File is based on the file contributed by Mellanox Technologies.\r
+\r
+Function Architecture()\r
+ Dim Arch,item\r
+ For Each item In GetObject("winmgmts:root/cimv2").ExecQuery("SELECT Architecture FROM Win32_Processor")\r
+ Arch=item.Architecture\r
+ Exit For\r
+ Next\r
+ \r
+ If (Arch=0) Then\r
+ Arch="x86"\r
+ Elseif (Arch=1) Then\r
+ Arch="MIPS"\r
+ Elseif (Arch=2) Then\r
+ Arch="Alpha"\r
+ Elseif (Arch=3) Then\r
+ Arch="PowerPC"\r
+ Elseif (Arch=6) Then\r
+ Arch="ia64"\r
+ Elseif (Arch=9) Then\r
+ 'Arch="x64"\r
+ Arch="amd64"\r
+ Else\r
+ WScript.echo "Arch ID=" & Arch\r
+ Arch="CustomAction.vbs: Unable to determine Architecture"\r
+ End If\r
+ Architecture=Arch\r
+\r
+End Function\r
+\r
+Sub Hello\r
+ MTARCH = Architecture \r
+ msgbox "Hello from " & MTARCH & " OS " & Session.Property("VersionNT") & _\r
+ " Build " & Session.Property("WindowsBuild")\r
+ ' XXX Did Not Work: Session.Message "You say Goodbye - while I say Hello..."\r
+End Sub\r
+\r
+Function Hello2\r
+ msgbox "Hello2"\r
+End Function\r
+\r
+Function Hello22\r
+ msgbox "Hello22 - after Hello2 OS " & VersionNT & " Build " & WindowsBuild\r
+End Function\r
+\r
+Function Goodbye\r
+ msgbox "Goodbye"\r
+End Function\r
+\r
+\r
+' Since a CustomAction (CA) that runs before SetupFinalize as deffered actions\r
+' can see the properties only through 'customactiondata'\r
+\r
+Sub WinOF_setup\r
+ ' Driver Install Properties:\r
+ ' 0-INSTALLDIR; 1-SystemFolder; 2-System64Folder; 3-WindowsFolder\r
+\r
+ Session.Property("DriverInstall") = Session.Property("INSTALLDIR") & _\r
+ ";" & Session.Property("SystemFolder") & ";" & _\r
+ Session.Property("System64Folder") & ";" & _\r
+ Session.Property("WindowsFolder") \r
+\r
+End Sub\r
+\r
+\r
+''''''''''' Remove Driver Files ''''''''''''\r
+\r
+'Waiting to delete a file until it's free\r
+\r
+Function FileDeleteUntilFree(filename)\r
+ Set objFSO=CreateObject("Scripting.FileSystemObject") \r
+ Set WshShell = CreateObject("WScript.Shell")\r
+ dim too_much \r
+ too_much = 0\r
+ Do While objFSO.FileExists(filename)\r
+ On Error Resume Next \r
+ objFSO.DeleteFile(filename)\r
+ WScript.Sleep 100 ' milliseconds\r
+ too_much = too_much + 1 'We do not wait to much to delete the file, then we don't delete it.\r
+ if too_much > 50 then\r
+ msgbox "delete Timeout(5) " & filename\r
+ exit Do\r
+ End If\r
+ err.clear \r
+ Loop \r
+End Function\r
+\r
+Function FileDelete(filename)\r
+ Dim fso\r
+ Set fso = CreateObject("Scripting.FileSystemObject")\r
+ Err.clear\r
+ If fso.FileExists(filename) Then\r
+ fso.DeleteFile(filename), True\r
+ If Err Then\r
+ msgbox "Could not delete: " & filename\r
+ ' Display error number and description if applicable\r
+ ShowError\r
+ Err.clear\r
+ End If \r
+ End If\r
+End Function\r
+\r
+' Move and then Delete a file. File is moved into %TEMP%\basename(filename)\r
+' then deleted; pesky files in 'system32\drivers'.\r
+\r
+Function FileMDelete(filename)\r
+ Dim fso\r
+ Set fso = CreateObject("Scripting.FileSystemObject")\r
+ Err.clear\r
+ If fso.FileExists(filename) Then\r
+ Set WshShell = CreateObject("WScript.Shell")\r
+ Return = WshShell.Run ("cmd.exe /c del /Q /F " & filename, 0, true)\r
+ If Err Then\r
+ msgbox "Could not delete: " & filename\r
+ ' Display error number and description if applicable\r
+ ShowError\r
+ Err.clear\r
+ End If \r
+ End If\r
+End Function\r
+\r
+Function FileMove(filename,destination)\r
+ Dim fso\r
+ Set fso = CreateObject("Scripting.FileSystemObject")\r
+ If fso.FileExists(filename) Then\r
+ On Error Resume Next \r
+ fso.MoveFile filename,destination\r
+ 'if err then msgbox "Could not move: " & filename\r
+ err.clear \r
+ End If\r
+ ' Display error number and description if applicable\r
+ If Err Then ShowError\r
+End Function\r
+\r
+\r
+Function RemoveDriverFiles()\r
+ Dim Win\r
+ Dim sDRIVERS\r
+ Dim sSystem64Folder \r
+ Dim sInstalldir\r
+ Dim sSystemFolder\r
+ \r
+ ' Function can be called from the Driver{Install/Uninstall} rtns.\r
+ ' (properties are different).\r
+ dim CheckMode\r
+ CheckMode = Session.Property("CustomActionData")\r
+ If Not CheckMode = "" Then\r
+ Dim PropArray\r
+ PropArray = Split(Session.Property("CustomActionData"), ";") \r
+ Win = PropArray(3)\r
+ sSystem64Folder = PropArray(2)\r
+ sSystemFolder = PropArray(1)\r
+ sInstalldir = PropArray(0)\r
+ Else\r
+ Win = Session.Property("WindowsFolder")\r
+ sSystem64Folder = Session.Property("System64Folder") \r
+ sInstalldir = Session.Property("INSTALLDIR") \r
+ sSystemFolder = Session.Property("SystemFolder") \r
+ End if\r
+ \r
+ MTARCH = Architecture \r
+ sDRIVERS = sSystem64Folder \r
+ If (MTARCH="x86") Then\r
+ sDRIVERS = sSystemFolder ' holds Session.Property("SystemFolder")\r
+ End If\r
+ sDRIVERS = sDRIVERS & "drivers\"\r
+\r
+' msgbox "RM sDrivers " & sDRIVERS & " sSystemFolder " & sSystemFolder & " sSystem64Folder " & sSystem64Folder \r
+' msgbox " sDrivers " & sDRIVERS\r
+' msgbox " sSystemFolder " & sSystemFolder\r
+' msgbox " sSystem64Folder " & sSystem64Folder\r
+ \r
+ FileDelete(sDRIVERS & "ibbus.sys")\r
+ FileDelete(sDRIVERS & "mthca.sys")\r
+ FileDelete(sDRIVERS & "ipoib.sys")\r
+ FileDelete(sDRIVERS & "ibsrp.sys")\r
+ FileDelete(sDRIVERS & "vnic.sys")\r
+ \r
+ If (MTARCH="amd64") Then\r
+if False Then\r
+ ' System64Folder = System32, SystemFolder = Syswow64\r
+ ' check/remove from .dll cache prior to removal from system32\\r
+ Dim dllCache\r
+ dllCache = sSystem64Folder & "dllcache\"\r
+ FileDelete(dllCache & "ibal.dll")\r
+ FileDelete(dllCache & "ibald.dll")\r
+ FileDelete(dllCache & "complib.dll")\r
+ FileDelete(dllCache & "complibd.dll")\r
+ FileDelete(dllCache & "mthcau.dll")\r
+ FileDelete(dllCache & "mthcaud.dll")\r
+ FileDelete(dllCache & "IbInstaller.dll")\r
+ FileDelete(dllCache & "ibwsd.dll")\r
+ FileDelete(dllCache & "ibsrp.dll")\r
+ FileDelete(dllCache & "ibsrpd.dll")\r
+ \r
+ FileDelete(sSystem64Folder & "ibal.dll")\r
+ FileDelete(sSystem64Folder & "ibald.dll")\r
+ FileDelete(sSystem64Folder & "complib.dll")\r
+ FileDelete(sSystem64Folder & "complibd.dll")\r
+ FileDelete(sSystem64Folder & "mthcau.dll")\r
+ FileDelete(sSystem64Folder & "mthcaud.dll")\r
+ FileDelete(sSystem64Folder & "IbInstaller.dll")\r
+ FileDelete(sSystem64Folder & "ibwsd.dll")\r
+ FileDelete(sSystem64Folder & "ibsrp.dll")\r
+ FileDelete(sSystem64Folder & "ibsrpd.dll")\r
+End if\r
+ End If \r
+ \r
+ ' MTARCH=x86 SystemFolder = System32\r
+ ' MTARCH=amd64 SystemFolder = Syswow64\r
+ FileDelete(sSystemFolder & "ibal.dll")\r
+ FileDelete(sSystemFolder & "ibald.dll")\r
+ FileDelete(sSystemFolder & "complib.dll")\r
+ FileDelete(sSystemFolder & "complibd.dll")\r
+ FileDelete(sSystemFolder & "mthcau.dll")\r
+ FileDelete(sSystemFolder & "mthcaud.dll")\r
+ FileDelete(sSystemFolder & "ibsrp.dll")\r
+ FileDelete(sSystemFolder & "ibsrpd.dll")\r
+ FileDelete(sSystemFolder & "IbInstaller.dll")\r
+ FileDelete(sSystemFolder & "ibwsd.dll")\r
+ \r
+ FileDelete(Win & "lastgood\system32\ibwsd.dll")\r
+ FileDelete(Win & "lastgood\sys64wow\ibwsd.dll")\r
+ \r
+ ' delete opensm files\r
+ Dim fso\r
+ Dim sTemp\r
+ Set fso = CreateObject("Scripting.FileSystemObject")\r
+ sTemp = fso.GetSpecialFolder(2)\r
+ FileDelete(sTemp & "guid2lid")\r
+ FileDelete(sTemp & "opensm-sa.dump")\r
+ FileDelete(sTemp & "osm.log")\r
+ FileDelete(sTemp & "osm-subnet.lst")\r
+ \r
+ ' Delete oem*.inf and oem*.pnf files\r
+ dim InfFiles, PnfFiles, IFILES, PFILES\r
+ Set WshShell = CreateObject("WScript.Shell")\r
+ Set infFilesExec = WshShell.Exec ("cmd.exe /c for /f %i in ('findstr /m Mellanox %WINDIR%\inf\oem*.*') do @echo %i")\r
+ ' Display error number and description if applicable\r
+ If Err Then ShowError\r
+ \r
+ InfFiles = infFilesExec.StdOut.ReadAll\r
+ PnfFiles = Replace(InfFiles,".inf",".pnf")\r
+ \r
+ IFILES = Split(InfFiles,vbCrLf)\r
+ PFILES = Split(PnfFiles,vbCrLf)\r
+ \r
+ For Each file in IFILES\r
+ If (file <> "") Then\r
+ FileDelete(file)\r
+ End IF\r
+ Next\r
+ \r
+ For Each file in PFILES\r
+ If (file <> "") Then\r
+ FileDelete(file)\r
+ End IF\r
+ Next\r
+ \r
+End Function\r
+\r
+''''''''''' Delete registry key ''''''''''''\r
+\r
+Function DeleteRegKey(KeyPath)\r
+ Const HKEY_LOCAL_MACHINE = &H80000002\r
+ dim strComputer\r
+ strComputer = "."\r
+ Set objReg=GetObject("winmgmts:" & _\r
+ "{impersonationLevel=impersonate}!\\" & _\r
+ strComputer & "\root\default:StdRegProv")\r
+\r
+ ' Display error number and description if applicable\r
+ ' If Err Then ShowError\r
+ Return = objReg.DeleteKey(HKEY_LOCAL_MACHINE, KeyPath)\r
+ \r
+End Function\r
+\r
+\r
+''''''''''' Delete registry value ''''''''''''\r
+\r
+Function DeleteRegValue(strKeyPath, strValueName)\r
+ Const HKEY_LOCAL_MACHINE = &H80000002\r
+ \r
+ dim strComputer\r
+ strComputer = "."\r
+ \r
+ Set objReg=GetObject("winmgmts:" & _\r
+ "{impersonationLevel=impersonate}!\\" & _ \r
+ strComputer & "\root\default:StdRegProv")\r
+\r
+ \r
+ Return = objReg.DeleteValue(HKEY_LOCAL_MACHINE, strKeyPath, strValueName)\r
+ ' Display error number and description if applicable\r
+ If Err Then ShowError\r
+' If (Return = 0) And (Err.Number = 0) Then\r
+' WScript.Echo value & "Registry value HKEY_LOCAL_MACHINE," & _\r
+' strKeyPath & "," & strValueName & "," & dwValue & " deleted"\r
+' Else\r
+' WScript.Echo "Registry value not deleted" & VBNewLine & _\r
+' "Error = " & Err.Number\r
+' End If\r
+\r
+End Function\r
+\r
+\r
+\r
+Function ReadSysPath\r
+\r
+ Const HKEY_LOCAL_MACHINE = &H80000002\r
+ Dim strComputer, strKeyPath, strValueName, strValue\r
+\r
+ ReadSysPath = Null ' assume the worst.\r
+ strComputer = "."\r
+ Set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _ \r
+ strComputer & "\root\default:StdRegProv")\r
+ \r
+ strKeyPath="SYSTEM\CurrentControlSet\Control\Session Manager\Environment"\r
+ strValueName = "Path"\r
+ oReg.GetExpandedStringValue HKEY_LOCAL_MACHINE,_\r
+ strKeyPath, strValueName, strValue\r
+\r
+ If (Err.Number = 0) And (Not IsNull(strValue)) Then\r
+ ReadSysPath = strValue\r
+ End if\r
+End Function\r
+\r
+\r
+Function WriteSysPath(NewPath)\r
+\r
+ Const HKEY_LOCAL_MACHINE = &H80000002\r
+ Dim strComputer, strKeyPath, strValueName\r
+\r
+ strComputer = "."\r
+ Set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _ \r
+ strComputer & "\root\default:StdRegProv")\r
+ \r
+ strKeyPath="SYSTEM\CurrentControlSet\Control\Session Manager\Environment"\r
+ strValueName = "Path"\r
+ oReg.SetExpandedStringValue _\r
+ HKEY_LOCAL_MACHINE, strKeyPath, strValueName, NewPath\r
+\r
+ WriteSysPath = Err.Number\r
+End Function\r
+\r
+\r
+'Chops the last character off a string if it matches strchar\r
+Function ChopChar(strString, strChar)\r
+ Dim x\r
+ x = Len(strString)\r
+ if mid(strString, x) = strChar then\r
+ ChopChar = mid(strString, 1, x -1)\r
+ else\r
+ ChopChar = strString\r
+ end if\r
+End Function\r
+\r
+\r
+' Add [INSTALLDIR] to the system search path registry entry @\r
+' HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\Path\r
+' Called from a defered exection context.\r
+\r
+Function SysPathAdd(InstallDir)\r
+\r
+ Dim rc, result, sInstallDir, newPath\r
+\r
+ ' On Error Resume Next\r
+ ' InstallDir = Session.Property("INSTALLDIR") for reference\r
+ ' sInstallDir = Left(InstallDir,Len(InstallDir) - 1) ' remove trailing \\r
+ sInstallDir = ChopChar(InstallDir,"\")\r
+\r
+ result = ReadSysPath\r
+ If IsNull(result) Then\r
+ SysPathAdd = ShowErr2("SysPathAdd - RegRead()")\r
+ Exit Function\r
+ End if\r
+\r
+ ' Is [INSTALLDIR] already set?\r
+ start = instr(result,sInstallDir)\r
+ If start <> 0 Then\r
+ SysPathAdd = 0\r
+ Exit Function\r
+ End if\r
+\r
+ newPath = result & ";" & sInstallDir\r
+\r
+ rc = WriteSysPath(newPath)\r
+ If rc <> 0 Then\r
+ SysPathAdd = ShowErr2("SysPathAdd - WriteSysPath()")\r
+ Else\r
+ SysPathAdd = 0\r
+ End if\r
+\r
+End Function\r
+\r
+\r
+\r
+Function SysPathRemove(InstallDir)\r
+\r
+ Dim rc, curPath, rKey, sInstallDir, newPath\r
+\r
+ ' On Error Resume Next\r
+ ' sInstallDir = Session.Property("INSTALLDIR")\r
+\r
+ sInstallDir = ";" & ChopChar(InstallDir,"\")\r
+\r
+ curPath = ReadSysPath\r
+ If IsNull(curPath) Then\r
+ SysPathRemove = ShowErr2("SysPathRemove - ReadSysPath() = NULL?")\r
+ Exit Function\r
+ End if\r
+\r
+ SysPathRemove = 0 ' assume SUCCESS\r
+\r
+ start = instr(curPath,sInstallDir)\r
+ If start <> 0 Then\r
+ ' INSTALLDIR IS in the system search path\r
+ ' remove INSTALLDIR from system search path\r
+ s0 = Left(curPath,start-1)\r
+msgbox "target " & Len(sInstallDir) & vbCRLF & sInstallDir\r
+msgbox "cur " & Len(curPath) & vbCRLF & curPath\r
+msgbox "s0 " & Len(s0) & vbCRLF & s0\r
+ s1 = Right(curPath,Len(curPath) - (start+Len(sInstallDir) - 1))\r
+msgbox "s1 " & Len(s1) & vbCRLF & s1\r
+ NewPath = s0 & s1\r
+msgbox "SPR: Reset-Path " & NewPath\r
+ rc = WriteSysPath(NewPath)\r
+ If rc <> 0 Then\r
+ SysPathRemove = ShowErr2("SysPathRemove - WriteSysPath()")\r
+ End if\r
+ End if\r
+\r
+ curPath = ReadSysPath\r
+msgbox "SPR: Cur " & curPath\r
+\r
+End Function\r
+\r
+\r
+\r
+' not used\r
+''''''''''' Check installation status ''''''''''''\r
+\r
+Function install_verify()\r
+ Dim Status\r
+ Dim sInstalldir\r
+ sInstalldir = Session.Property("INSTALLDIR")\r
+ Set WshShell = CreateObject("WScript.Shell")\r
+ Set vstat = WshShell.Exec(sInstalldir & "\bin\vstat.exe")\r
+ install_verify = vstat.ExitCode\r
+\r
+End Function\r
+\r
+'-------------------------------------------------------------\r
+\r
+' add registry key\r
+Function CreateRegKey(KeyPath)\r
+ Const HKEY_LOCAL_MACHINE = &H80000002\r
+ dim strComputer\r
+ strComputer = "."\r
+ Set objReg=GetObject("winmgmts:" & _\r
+ "{impersonationLevel=impersonate}!\\" & _\r
+ strComputer & "\root\default:StdRegProv")\r
+\r
+ ' Display error number and description if applicable\r
+ If Err Then ShowError\r
+ Return = objReg.CreateKey(HKEY_LOCAL_MACHINE, KeyPath)\r
+ \r
+End Function\r
+\r
+\r
+\r
+'--------------------------------------------------------\r
+\r
+\r
+' Function to add registry DWORD val.\r
+Function AddRegDWORDValue(strKeyPath, strValueName, dwValue)\r
+const HKEY_LOCAL_MACHINE = &H80000002\r
+strComputer = "."\r
+ \r
+Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_ \r
+strComputer & "\root\default:StdRegProv")\r
+ \r
+If Err Then ShowError\r
+oReg.SetDWORDValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,dwValue\r
+If Err Then ShowError\r
+\r
+End Function\r
+\r
+'-------------------------------------------------\r
+\r
+' Function to add registry Expanded string val.\r
+Function AddRegExpandValue(strKeyPath, strValueName, dwValue)\r
+const HKEY_LOCAL_MACHINE = &H80000002\r
+strComputer = "."\r
+ \r
+Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_ \r
+strComputer & "\root\default:StdRegProv")\r
+ \r
+If Err Then ShowError\r
+oReg.SetExpandedStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,dwValue\r
+If Err Then ShowError\r
+\r
+End Function\r
+\r
+'------------------------------------------------------------------------\r
+\r
+\r
+' Function to add registry string val.\r
+\r
+Function AddRegStringValue(strKeyPath, strValueName, dwValue)\r
+const HKEY_LOCAL_MACHINE = &H80000002\r
+strComputer = "."\r
+ \r
+Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_ \r
+strComputer & "\root\default:StdRegProv")\r
+ \r
+If Err Then ShowError\r
+oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,dwValue\r
+If Err Then ShowError\r
+\r
+End Function\r
+\r
+'------------------------------------------------------------------------\r
+\r
+\r
+\r
+\r
+''''''''''' Driver Install ''''''''''''\r
+\r
+Function DriverInstall()\r
+\r
+ MTARCH = Architecture\r
+ \r
+ Dim PropArray\r
+ Dim CheckMode, sInstalldir, fso\r
+\r
+ ' Get the value of INSTALLDIR\r
+ CheckMode = Session.Property("CustomActionData")\r
+\r
+ If Not CheckMode = "" Then\r
+ 'in defered action this is the way to pass arguments.\r
+ PropArray = Split(Session.Property("CustomActionData"), ";")\r
+ Else\r
+ Redim PropArray(4)\r
+ PropArray(0) = Session.Property("INSTALLDIR") \r
+ PropArray(1) = Session.Property("SystemFolder") \r
+ PropArray(2) = Session.Property("System64Folder") \r
+ PropArray(3) = Session.Property("WindowsFolder")\r
+ End if\r
+\r
+ sInstalldir = PropArray(0)\r
+ \r
+ ' xxx temp - Add INSTALLDIR to system search path.\r
+ 'If SysPathAdd(sInstalldir) Then\r
+ ' DriverInstall=1\r
+ ' Exit Function\r
+ 'End If\r
+\r
+ RemoveDriverFiles\r
+ \r
+ Set WshShell = CreateObject("WScript.Shell")\r
+ Set fso = CreateObject("Scripting.FileSystemObject")\r
+ \r
+ If Not fso.FileExists(sInstalldir & "IBcore\devman.exe") Then\r
+ msgbox "Driver Install - missing file " & sInstalldir & _\r
+ "IBcore\devman.exe" \r
+ DriverInstall=1\r
+ Exit Function\r
+ End if\r
+\r
+ ' rescan system buses\r
+ Return = WshShell.Run ("cmd.exe /c cd " & sInstalldir & "IBcore & devman.exe rescan", 0, true)\r
+ ' Display error number and description if applicable\r
+ If Err Then ShowError\r
+ If Return <> 0 Then\r
+ msgbox "Driver Install - HCA Ret " & Return & " Err " & Err\r
+ DriverInstall=Return\r
+ Exit Function\r
+ End if\r
+ \r
+ \r
+ ' Install HCA Driver\r
+ Return = WshShell.Run ("cmd.exe /c cd " & sInstalldir & "IBcore & devman.exe update mthca.inf PCI\VEN_15b3", 0, true)\r
+ ' Display error number and description if applicable\r
+ If Err Then ShowError\r
+\r
+ If Return <> 0 Then\r
+ msgbox "Driver Install - HCA Ret " & Return & " Err " & Err\r
+ DriverInstall=Return\r
+ Exit Function\r
+ End if\r
+ \r
+ ' Check/install IPoIB driver\r
+ ' Only if InstallShield component 'net' is NOT tagged as containing a Device Driver \r
+ If fso.FileExists(sInstalldir & "net\netipoib.inf") Then\r
+ Return = WshShell.Run ("cmd.exe /c cd " & sInstalldir & "net & ..\IBcore\devman.exe update netipoib.inf IBA\IPoIB", 0, true)\r
+ If Err Then ShowError\r
+ End If\r
+ \r
+ ' Copy 32 bit dlls on 64-bit architectures\r
+ ' PropArray() 0-INSTALLDIR; 1-SystemFolder; 2-System64Folder 3-WindowsFolder\r
+\r
+ If (MTARCH="amd64") Then\r
+ Dim SYSWOW\r
+ SYSWOW = PropArray(1) \r
+' following file copies relocated to .wxs file so they can be uninstalled \r
+' correctly, as this way the files reamin when uninstalled.\r
+if False then\r
+ msgbox "DriverInstall PA(1) " & SYSWOW & " PA(2) " & PropArray(2)\r
+ if fso.FileExists(sInstalldir & "IBcore\cl32.dll") then\r
+ fso.CopyFile sInstalldir & "IBcore\cl32.dll", SYSWOW & "complib.dll"\r
+ end if\r
+ if fso.FileExists(sInstalldir & "IBcore\cl32d.dll") then\r
+ fso.CopyFile sInstalldir & "IBcore\cl32d.dll", SYSWOW & "complibd.dll"\r
+ end if\r
+ if fso.FileExists(sInstalldir & "IBcore\ibal32.dll") then\r
+ fso.CopyFile sInstalldir & "IBcore\ibal32.dll", SYSWOW & "ibal.dll"\r
+ end if\r
+ if fso.FileExists(sInstalldir & "IBcore\ibal32d.dll") then\r
+ fso.CopyFile sInstalldir & "IBcore\ibal32d.dll", SYSWOW & "ibald.dll"\r
+ end if\r
+ if fso.FileExists(sInstalldir & "IBcore\mtuvpd32.dll") then\r
+ fso.CopyFile sInstalldir & "IBcore\mtuvpd32.dll", SYSWOW & "mthcau.dll"\r
+ end if\r
+ if fso.FileExists(sInstalldir & "IBcore\mtuvpd32d.dll") then\r
+ fso.CopyFile sInstalldir & "IBcore\mtuvpd32d.dll", SYSWOW & "mthcaud.dll"\r
+ end if\r
+ if fso.FileExists(sInstalldir & "net\ibwsd32.dll") then\r
+ fso.CopyFile sInstalldir & "net\ibwsd32.dll", SYSWOW & "ibwsd.dll"\r
+ end if\r
+ end if ' XXX\r
+ End If \r
+\r
+ ' append [INSTALLDIR] to system search path\r
+ SysPathAdd(sInstalldir)\r
+\r
+ err.clear \r
+ DriverInstall=0\r
+End Function\r
+\r
+\r
+'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''\r
+\r
+' Find IBA devices using Devcon\r
+\r
+Function FindDevices() \r
+ Dim sInstalldir\r
+ MTARCH = Architecture\r
+ sInstalldir = Session.Property("INSTALLDIR")\r
+ Set WshShell = CreateObject("WScript.Shell")\r
+\r
+ Set ibaDevicesExec = WshShell.Exec ("cmd.exe /c cd " & sInstalldir & "IBcore & devman.exe FindAll * | FIND ""IBA""")\r
+ ibaDevices = split(ibaDevicesExec.StdOut.ReadAll, vbCrLF)\r
+\r
+ ' Getting the array Size\r
+ dim arrSize\r
+ arrSize = 0\r
+ for each deviceCan in ibaDevices\r
+ if (Instr(deviceCan,"IBA\") = 1) Then\r
+ arrSize = arrSize + 1\r
+ End if\r
+ next\r
+ 'Creating array of IBA\ devices\r
+ dim ibaDev()\r
+ Redim ibaDev(arrSize - 1)\r
+ index = 0\r
+ for each deviceCan in ibaDevices\r
+ if (Instr(deviceCan,"IBA\") = 1) Then\r
+ ibaDev(index) = deviceCan\r
+ index = index + 1\r
+ End if\r
+ next\r
+\r
+ ' Return array of devices\r
+ FindDevices=ibaDev \r
+End Function\r
+\r
+\r
+' returns an array of all Local Area Connections which\r
+' were created for IPoIB.\r
+\r
+Function Find_IPOIB_LAC()\r
+ Set WshShell = CreateObject("WScript.Shell")\r
+\r
+ Set ibaDevicesExec = WshShell.Exec ("cmd.exe /c reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network /f ""IBA\IPOIB"" /s /d | FIND ""Connection""")\r
+ ibaDevices = split(ibaDevicesExec.StdOut.ReadAll, vbCrLF)\r
+\r
+ ' Getting the array Size\r
+ dim arrSize\r
+ arrSize = 0\r
+ for each deviceCan in ibaDevices\r
+ arrSize = arrSize + 1\r
+ next\r
+ 'Creating array of Local Area Connections based on IPoIB\r
+ dim ibaDev()\r
+ Redim ibaDev(arrSize - 1)\r
+ index = 0\r
+ for each deviceCan in ibaDevices\r
+ ibaDev(index) = deviceCan\r
+ index = index + 1\r
+ next\r
+ Find_IPOIB_LAC=ibaDev\r
+End Function\r
+\r
+\r
+' Not used - run the specified command during next startup.\r
+\r
+Function RunAtReboot(run_once_cmd)\r
+ dim key_name\r
+ key_name = "Software\Microsoft\Windows\CurrentVersion\RunOnce"\r
+ AddRegStringValue key_name,"WinOF",run_once_cmd\r
+ msgbox "RunAtReboot() " & run_once_cmd\r
+ RunAtReboot = 0\r
+End Function\r
+\r
+\r
+\r
+''''''''''' Driver Uninstall ''''''''''''\r
+\r
+Sub DriverUninstall() \r
+ Dim sInstalldir, WshShell, fso, devices\r
+\r
+ sInstalldir = Session.Property("INSTALLDIR")\r
+\r
+ Set WshShell = CreateObject("WScript.Shell")\r
+ Set fso = CreateObject("Scripting.FileSystemObject")\r
+\r
+ MTARCH = Architecture\r
+ \r
+ ' WSD doesn't work on XP and should NOT be installed; just in case.\r
+ ' if WSD installed, then it's enabled, shut down the service\r
+\r
+ If (Session.Property("VersionNT") <> 501) AND fso.FileExists(sInstalldir & "installsp.exe") Then\r
+ Return = WshShell.Run ("cmd.exe /c cd " & sInstalldir & " & installsp.exe -r", 0, true)\r
+ End If\r
+ \r
+ ' stop the openSM service in case it was started.\r
+ Return = WshShell.Run ("cmd.exe /c sc.exe stop opensm", 0, true)\r
+\r
+ ' delete opensm service from regisry\r
+ Return = WshShell.Run ("cmd.exe /c sc.exe delete opensm", 0, true)\r
+ If Err Then ShowError\r
+\r
+ ' create a list of IBA\ devices via 'devcon findall'\r
+ devices = FindDevices\r
+ \r
+ ' Remove IPoIB Adapter instances\r
+ for each deviceCan in devices\r
+ if (Instr(deviceCan,"IBA\IPOIB")) Then\r
+ device = split(deviceCan, " ")\r
+ ' Removing\r
+ Return = WshShell.Run ("cmd.exe /c cd " & sInstalldir & "IBcore & devman.exe remove @" & device(0), 0, true)\r
+ End if\r
+ Next\r
+\r
+ ' Removing SRP - Searching for I/O UNIT and then removing it.\r
+ for each deviceCan in devices\r
+ if (Instr(deviceCan,"InfiniBand I/O Unit")) Then\r
+ device = split(deviceCan, " ")\r
+ ' Removing I/O Unit of the SRP\r
+ Return = WshShell.Run ("cmd.exe /c cd " & sInstalldir & "IBcore & devman.exe remove @" & device(0), 0, true)\r
+ End if\r
+ Next\r
+ \r
+ ' Removing SRP - Searching for SRP devices.\r
+ for each deviceCan in devices\r
+ if (Instr(deviceCan,"SRP")) Then\r
+ device = split(deviceCan, " ")\r
+ ' Removing SRP\r
+ Return = WshShell.Run ("cmd.exe /c cd " & sInstalldir & "IBcore & devman.exe remove @" & device(0), 0, true)\r
+ End if\r
+ Next\r
+\r
+ Set objWshScriptExec = wshShell.Exec("cmd.exe /c " & sInstalldir & "IBcore & devman.exe FindAll * | FIND ""IPOIB""")\r
+ If Err Then ShowError\r
+ Set objStdOut = objWshScriptExec.StdOut\r
+\r
+ While Not objStdOut.AtEndOfStream\r
+ strLine = objStdOut.ReadLine\r
+ device = split(strLine, " ")\r
+ Return = wshShell.run("cmd.exe /c cd " & sInstallDir & "IBcore & devman.exe remove @" & device(0),0,true)\r
+ Wend\r
+\r
+ ' Remove InfiniBand Bus/Fabric class driver\r
+\r
+ Set objWshScriptExec = wshShell.Exec("cmd.exe /c cd " & sInstalldir & "IBcore & devman.exe FindAll * | FIND ""InfiniBand Fabric""")\r
+ If Err Then ShowError\r
+ Set objStdOut = objWshScriptExec.StdOut\r
+\r
+ While Not objStdOut.AtEndOfStream\r
+ strLine = objStdOut.ReadLine\r
+ device = split(strLine, " ")\r
+ Return = wshShell.Run("cmd.exe /c cd " & sInstalldir & "IBcore & devman.exe remove @" & device(0),0,true)\r
+ If Err Then ShowError\r
+ Wend\r
+\r
+ ' Remove HCAs\r
+ Return = WshShell.Run ("cmd.exe /c cd " & sInstalldir & "IBcore & devman.exe remove PCI\VEN_15b3", 0, true)\r
+ If Err Then ShowError\r
+\r
+ ' Remove Service entries from the registry\r
+ \r
+ DeleteRegKey "System\CurrentControlSet\Services\ibbus"\r
+ DeleteRegKey "System\CurrentControlSet\Services\mthca"\r
+ DeleteRegKey "System\CurrentControlSet\Services\ipoib"\r
+ \r
+ DeleteRegValue "SYSTEM\CurrentControlSet\Control\CoDeviceInstallers" , "{58517E00-D3CF-40c9-A679-CEE5752F4491}"\r
+ DeleteRegKey "SYSTEM\CurrentControlSet\Control\Class\{58517E00-D3CF-40C9-A679-CEE5752F4491}" \r
+ \r
+ ' in livefish mode the delete didn't suceed, delete it in another way\r
+ Return = WshShell.Run ("reg.exe delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{58517E00-D3CF-40C9-A679-CEE5752F4491} /f", 0, true)\r
+ If Err Then ShowError\r
+ \r
+ Return = WshShell.Run ("reg.exe delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibbus /f", 0, true)\r
+ Return = WshShell.Run ("reg.exe delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mthca /f", 0, true)\r
+ Return = WshShell.Run ("reg.exe delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ipoib /f", 0, true)\r
+\r
+ ' remove all Local Area Connection which were constructed for IPoIB\r
+ ' create a list of IBA\IPOIB Local Area Connections via 'reg query'\r
+ Dim IPOIB_LAC\r
+ IPOIB_LAC = Find_IPOIB_LAC\r
+\r
+ For each LAC in IPOIB_LAC\r
+ If LAC <> "" Then\r
+ Return = WshShell.Run ("reg.exe delete " & LAC & " /f", 0, true)\r
+ If Err Then ShowErr\r
+ End if\r
+ Next\r
+ \r
+ ' remove driver installed files\r
+ RemoveDriverFiles\r
+ \r
+ Session.Property("REBOOT") = "FORCE" \r
+ err.clear \r
+End Sub\r
+\r
+\r
+' Enable WSD if installsp.exe was installed (feature Winsock direct selected).\r
+' For Windows XP, this CA should not be called as WSD is not supported on XP.\r
+\r
+Sub WSDEnable()\r
+ Dim sInstalldir, WshShell, fso\r
+\r
+ sInstalldir = Session.Property("INSTALLDIR")\r
+\r
+ Set WshShell = CreateObject("WScript.Shell")\r
+ Set fso = CreateObject("Scripting.FileSystemObject")\r
+\r
+ If fso.FileExists(sInstalldir & "installsp.exe") Then\r
+ ' install the WinSockdirect service\r
+ Return = WshShell.Run ("cmd.exe /c cd " & sInstalldir & " & installsp.exe -i", 0, true)\r
+ End If\r
+\r
+ ' Display error number and description if applicable\r
+ If Err Then ShowError\r
+End Sub\r
+\r
+\r
+Sub ShowError()\r
+ If Err.Number = 0 Then\r
+ Exit Sub\r
+ End if\r
+ strMsg = vbCrLf & "Error # " & Err.Number & vbCrLf & _\r
+ Err.Description & vbCrLf & vbCrLf\r
+ 'Syntax\r
+ msgbox "ShowError - " & strMsg\r
+End Sub\r
+\r
+\r
+Function ShowErr2(msg)\r
+msgbox "Err # " & Err.Number\r
+ If Err.Number <> 0 Then\r
+ strMsg = vbCrLf & "Err # " & Err.Number & vbCrLf & _\r
+ Err.Description & vbCrLf & vbCrLf\r
+ 'Syntax\r
+ msgbox msg & strMsg\r
+ End if\r
+ ShowErr2=Err.Number\r
+End Function\r
+\r
+\r
+' Create OpenSM (Subnet Management) windows service disabled.\r
+\r
+Sub OpensmServiceEvent()\r
+ Dim sInstalldir,opensmPath,opensmService,WshShell,fso\r
+ Dim sc, StartMeUp\r
+\r
+ sInstalldir = Session.Property("INSTALLDIR")\r
+ opensmService = sInstalldir & "opensm.service.txt"\r
+ opensmPath = sInstalldir & "opensm.exe"\r
+\r
+ Set fso = CreateObject("Scripting.FileSystemObject")\r
+ Set WshShell = CreateObject("WScript.Shell")\r
+ \r
+ ' opensm.exe is required\r
+ If Not fso.FileExists(opensmPath) Then\r
+ Exit Sub\r
+ End if\r
+\r
+ sc = "sc.exe create opensm binPath= """ &opensmPath _\r
+ & " -e --service"" DisplayName= ""InfiniBand Subnet Manager"" "\r
+\r
+ ' start opesm as a Service?\r
+ If fso.FileExists(opensmService) Then\r
+ StartMeUp = True\r
+ sc = sc & "start= auto"\r
+ Else\r
+ StartMeUp = False\r
+ sc = sc & "start= disabled"\r
+ End if\r
+ Return = WshShell.Run ("cmd.exe /c " & sc, 0, true)\r
+ sc = "sc.exe description opensm ""Configures and manage the InfiniBand Subnet"" "\r
+ Return = WshShell.Run ("cmd.exe /c " & sc, 0, true)\r
+\r
+ ' Is opensm to be run as a service?\r
+ If StartMeUp Then\r
+ Return = WshShell.Run ("cmd.exe /c sc.exe start opensm", 0, true)\r
+ End if\r
+ err.clear\r
+End Sub\r
+\r
+\r
+' Determine if an existing WinOF or openib-window installation exists.\r
+' If existing, determined by registry entry for service/ibbus,\r
+' then uninstall and reboot.\r
+' Called in immediate mode, condition: INSTALL=1\r
+\r
+Function ChkInstallAndReboot()\r
+ Const wshYes = 6\r
+ Const wshNo = 7\r
+ Const wshYesNoDialog = 4\r
+ Const wshQuestionMark = 32\r
+\r
+ Dim status ' check if ibbus.sys exists, if not the reboot won't happen\r
+ Dim fso\r
+ Set fso = CreateObject("Scripting.FileSystemObject") \r
+ status = 0\r
+ \r
+ Set WshShell = CreateObject("WScript.Shell")\r
+ Return = WshShell.Run ("reg.exe query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibbus /v ImagePath", 0, true)\r
+ If (Return = 0) And (Err.Number = 0) Then\r
+ Status = Status + 1\r
+ End if\r
+ \r
+ ' if we can't find registry entry, then no need to uninstall/restart.\r
+ ' Proceed with installation\r
+ If status = 0 then\r
+ ' msgbox "No existing InfiniBand installation detected"\r
+ Exit Function\r
+ End if\r
+ \r
+ ' Notify the user an existing non WinOF IB installation was detected and\r
+ ' the system will be rebooted.\r
+ dim res\r
+ \r
+ res = WshShell.Popup("Existing InfiniBand installation has been removed.",12,"WinOF - Existing InfiniBand installation Detected") \r
+\r
+ ' proceed with Uninstall and reboot.\r
+ ' Upon system restart, WinOF installation needs to be restarted \r
+ ' consider a run-once invocation.\r
+\r
+ DriverUninstall\r
+\r
+ ChkInstallAndReboot = 0\r
+\r
+ ' the _Driver Uninstall call sets reboot=force. The ForceReboot action\r
+ ' following this CustomAction will fire when reboot is set =force.\r
+ \r
+End Function\r
+\r
+\r
+\r
+' This routine should never be...InstallShield-12 for some reason has\r
+' decided not to completely remove [INSTALLDIR]? Until such a time\r
+' that 'why' is understood, this routine removes [INSTALLDIR]! Sigh...\r
+' nuke some driver files which remain due to devcon device install.\r
+' Immediate execution; called after MsiCleanupOnSuccess (REMOVE="ALL")\r
+\r
+Sub HammerTime\r
+ Dim fso, sInstallDir, RC, cmd\r
+\r
+ Set fso=CreateObject("Scripting.FileSystemObject") \r
+ Set WshShell=CreateObject("WScript.Shell")\r
+\r
+ sInstallDir = Session.Property("INSTALLDIR")\r
+ If fso.FolderExists(sInstallDir) Then\r
+ cmd = "cmd.exe /c rmdir /S /Q """ & sInstallDir & """"\r
+ RC = wshShell.Run(cmd,0,true)\r
+ End if\r
+\r
+ SysPathRemove(sInstallDir)\r
+\r
+End Sub\r
+\r
+\r
+' NOT USED - deferred action to increment ticks while action is taking place\r
+'\r
+Function AddProgressInfo( )\r
+ Const INSTALLMESSAGE_ACTIONSTART = &H08000000\r
+ Const INSTALLMESSAGE_ACTIONDATA = &H09000000 \r
+ Const INSTALLMESSAGE_PROGRESS = &H0A000000 \r
+\r
+ Set rec = Installer.CreateRecord(3)\r
+ \r
+ rec.StringData(1) = "callAddProgressInfo"\r
+ rec.StringData(2) = "Incrementing the progress bar..."\r
+ rec.StringData(3) = "Incrementing tick [1] of [2]"\r
+ \r
+ 'Message INSTALLMESSAGE_ACTIONSTART, rec\r
+ \r
+ rec.IntegerData(1) = 1\r
+ rec.IntegerData(2) = 1\r
+ rec.IntegerData(3) = 0\r
+ \r
+ Message INSTALLMESSAGE_PROGRESS, rec\r
+ \r
+ Set progrec = Installer.CreateRecord(3)\r
+ \r
+ progrec.IntegerData(1) = 2\r
+ progrec.IntegerData(2) = 5000\r
+ progrec.IntegerData(3) = 0\r
+ \r
+ rec.IntegerData(2) = 1500000\r
+ \r
+ For i = 0 To 5000000 Step 5000\r
+ rec.IntegerData(1) = i\r
+ ' action data appears only if a text control subscribes to it\r
+ ' Message INSTALLMESSAGE_ACTIONDATA, rec\r
+ Message INSTALLMESSAGE_PROGRESS, progrec\r
+ Next ' i\r
+ \r
+ ' return success to MSI\r
+ AddProgressInfo = 0\r
+End Function\r
+\r
--- /dev/null
+\r
+<head>\r
+<style>\r
+<!--\r
+div.Section1\r
+ {page:Section1;}\r
+-->\r
+</style>\r
+</head>\r
+\r
+<h1 align="left">\r
+<img border="0" src="openfabrics.gif" width="107" height="93"> \r
+<a name="TOP" href="#TOP"></a> </h1>\r
+<h1 align="center">Windows OpenFabrics </h1>\r
+<h1 align="center">User's Manual</h1>\r
+<h2 align="center">Release 1.0</h2>\r
+<h3 align="center">\r
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->06/04/2007<!--webbot bot="Timestamp" endspan i-checksum="12566" --></h3>\r
+<h2 align="left"><u>Overview</u></h2>\r
+<p align="left"><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'">\r
+The Windows OpenFabrics (WinOF) package is composed of software modules intended \r
+for use on Microsoft Windows based computer systems connected via an InfiniBand \r
+fabric.</span></p>\r
+<p align="left">The Windows OpenFabrics software package contains the \r
+following:<br>\r
+<br>\r
+OpenFabrics Infiniband core drivers and Upper Level Protocols (ULPs):</p>\r
+<ul>\r
+ <li>\r
+ <p align="left">HCA (Host Channel Adapter) driver </li>\r
+ <li>\r
+ <p style="text-indent: -.25in; margin-left: .5in"><span dir="LTR">MTHCA -<span style='background-position: 0% 0%; mso-highlight:yellow; background-image:none; background-repeat:repeat; background-attachment:scroll'> \r
+ Mellanox </span></span><st1:stockticker>\r
+ <span\r
+ style='background-position: 0% 0%; mso-highlight:yellow; background-image:none; background-repeat:repeat; background-attachment:scroll'>HCA</span></st1:stockticker><span\r
+style='background-position: 0% 0%; mso-highlight:yellow; background-image:none; background-repeat:repeat; background-attachment:scroll'> low level driver. See \r
+ Release_notes.htm for a list of supported devices. <o:p></o:p></span>\r
+ </li>\r
+<li>\r
+<p align="left">Infiniband Core modules: IB verbs and IB access layer</li>\r
+<li>\r
+<p align="left">Upper Layer Protocols: IPoIB, WSD, VNIC, SRP Initiator and uDAPL</li>\r
+</ul>\r
+<p align="left">OpenFabrics utilities:</p>\r
+<ul>\r
+ <li>\r
+ <p align="left">OpenSM: InfiniBand Subnet Manager</li>\r
+<li>\r
+<p align="left">Performance tests</li>\r
+<li>\r
+<p align="left">Diagnostic tools</li>\r
+</ul>\r
+<p align="left">Documentation</p>\r
+<ul>\r
+ <li>\r
+ <p align="left">User's manual</li>\r
+<li>\r
+<p align="left">Release Notes</li>\r
+</ul>\r
+<h2 align="left"><u>Features</u></h2>\r
+<ul>\r
+ <li>\r
+ <h3 align="left">Tools</h3></li>\r
+</ul>\r
+<blockquote>\r
+ <blockquote>\r
+ <p align="left">The OpenFabrics Alliance Windows release contains a set of \r
+ user mode tools which are designed to faciliate the smooth operation of an \r
+ Windows OpenFabrics installation. These tools are available from a command \r
+ window (cmd.exe) as the installation path '%SystemDrive%\Program \r
+ Files\WinOF' is appended to the system wide search path registry entry. \r
+ A start menu short-cut 'WinOF Cmd Window' is provided to faciliate \r
+ correction tool operation.</p>\r
+ <h4 align="left">Infiniband Subnet Management</h4>\r
+ <ul>\r
+ <li>\r
+ <p align="left"><a href="#opensm">opensm</a> Open Subnet \r
+ Management - configure and manage an InfiniBand subnet</li>\r
+ <li>\r
+ <p align="left"><a href="#osmtest">osmtest</a> \r
+ Subnet management tests</li>\r
+ <li>\r
+ <p align="left"><a href="#ibtrapgen">ib_trapgen</a> Generate Infiniband Subnet \r
+ Management Traps for testing purposes</li>\r
+ </ul>\r
+ <h4 align="left"><a href="#verbs_benchmarks">Performance</a></h4>\r
+ <ul>\r
+ <li>\r
+ <p align="left"><a href="#ibsend_lat">ib_send_lat</a> Infiniband send \r
+latency measurement</li>\r
+ <li>\r
+ <p align="left"><a href="#ibsend_bw">ib_send_bw</a> Infiniband send bandwidth \r
+ measurement</li>\r
+ <li>\r
+ <p align="left"><a href="#ibwrite_lat">ib_write_lat</a> Infiniband RDMA write \r
+latency measurement</li>\r
+ <li>\r
+ <p align="left">i<a href="#ibwrite_bw">b_write_bw</a> Infiniband RDMA write bandwidth \r
+measurement</li>\r
+ <li>\r
+ <p align="left"><a href="#ttcp">ttcp</a> \r
+TCP performance measurements</li>\r
+ </ul>\r
+ <h4 align="left"><a href="#diags">Diagnostics</a></h4>\r
+ <ul>\r
+ <li>\r
+ <p align="left"><a href="#iblimits">ib_limits</a> \r
+ Infiniband verb tests</li>\r
+ <li>\r
+ <p align="left"><a href="#cmtest">cmtest </a> Connection Manager tests</li>\r
+ <li>\r
+ <p align="left"><a href="#printip">PrintIP</a> Display \r
+an Internet Protocol address associated with an IB GUID.</li>\r
+ <li>\r
+ <p align="left"><a href="#vstat">vstat</a> \r
+Display HCA attributes, statistics and error counters.<br> </li>\r
+ </ul>\r
+ </blockquote>\r
+</blockquote>\r
+<ul>\r
+ <li>\r
+ <h3 align="left"><a href="#IPoIB">IPoIB - Internet Protocols over InfiniBand</a></h3>\r
+ </li>\r
+ <li>\r
+ <h3 align="left"><a href="#winsockdirect">Winsock Direct Service Provider</a></h3>\r
+ </li>\r
+ <li>\r
+ <h3 align="left"><a href="#DAT">DAT and uDAPL</a></h3></li>\r
+ <li>\r
+ <h3 align="left"><a href="#SRP">SRP - SCSI RDMA Protocol</a></h3></li>\r
+</ul>\r
+<h3 align="left"> </h3>\r
+<p align="left"> </p>\r
+<hr>\r
+<p align="left"> </p>\r
+<h2 align="left"><a name="verbs_benchmarks"></a>User mode verbs micro-benchmarks<br>\r
+ </h2>\r
+<p align="left">These micro-benchmarks tests are intended as useful benchmarks for HW or SW \r
+tuning and/or functional testing.</p>\r
+<blockquote>\r
+ <p align="left">Tests use CPU cycle counters to get time stamps without \r
+ context switch.<br>\r
+ <br>Tests measure round-trip time but report half of that as one-way latency<br>\r
+ (i.e.. May not be sufficiently accurate for \r
+ asymmetrical configurations).<br>\r
+ <br>Min/Median/Max result is reported.<br>The median (vs. average) is less sensitive to extreme scores.<br>Typically the "Max" value is the first value measured.<br>\r
+ <br>larger samples only marginally help. The default (1000) is pretty good.<br>Note that an array of cycles_t (typically unsigned long) is allocated<br>once to collect samples and again to store the difference between them.<br>Really big sample sizes (e.g. 1 million) might expose other problems<br>with the program.<br>\r
+ <br>"-H" option will dump the histogram for additional statistical analysis.<br>See xgraph, ygraph, r-base (http://www.r-project.org/), pspp, or other\r
+ <br>statistical math programs.<br><br>Architectures tested: x86, x86_64, ia64</p>\r
+</blockquote>\r
+<h4 align="left"><a name="ibsend_lat"></a>ib_send_lat.exe - latency test with \r
+send transactions</h4>\r
+<blockquote>\r
+ <p align="left">Usage:</p>\r
+ <blockquote>\r
+ <p align="left">ib_send_lat start a server and wait for connection<br>\r
+ ib_send_lat <host> connect to server at <host></p>\r
+ </blockquote>\r
+ <p align="left">Options:</p>\r
+ <blockquote>\r
+ <p align="left">-p, --port=<port> listen on/connect to port <port> \r
+ (default 18515)<br>\r
+ -c, --connection=<RC/UC> connection type RC/UC (default RC)<br>\r
+ -m, --mtu=<mtu> mtu size (default 2048)<br>\r
+ -d, --ib-dev=<dev> use IB device <dev> (default first device found)<br>\r
+ -i, --ib-port=<port> use port <port> of IB device (default 1)<br>\r
+ -s, --size=<size> size of message to exchange (default 1)<br>\r
+ -t, --tx-depth=<dep> size of tx queue (default 50)<br>\r
+ -l, --signal signal completion on each msg<br>\r
+ -a, --all Run sizes from 2 till 2^23<br>\r
+ -n, --iters=<iters> number of exchanges (at least 2, default 1000)<br>\r
+ -C, --report-cycles report times in cpu cycle units (default \r
+ microseconds)<br>\r
+ -H, --report-histogram print out all results (default print summary \r
+ only)<br>\r
+ -U, --report-unsorted (implies -H) print out unsorted results (default \r
+ sorted)<br>\r
+ -V, --version display version number<br>\r
+ -e, --events sleep on CQ events (default poll)</p>\r
+ </blockquote>\r
+</blockquote>\r
+<h4 align="left"><a name="ibsend_bw"></a>ib_send_bw.exe - BW (BandWidth) test with send transactions</h4>\r
+<blockquote>\r
+ <p align="left">Usage:</p>\r
+ <blockquote>\r
+ <p align="left">ib_send_bw start a server and wait for connection<br>\r
+ ib_send_bw <host> connect to server at <host></p>\r
+ </blockquote>\r
+ <p align="left">Options:</p>\r
+ <blockquote>\r
+ <p align="left">-p, --port=<port> listen on/connect to port <port> \r
+ (default 18515)<br>\r
+ -d, --ib-dev=<dev> use IB device <dev> (default first device found)<br>\r
+ -i, --ib-port=<port> use port <port> of IB device (default 1)<br>\r
+ -c, --connection=<RC/UC> connection type RC/UC/UD (default RC)<br>\r
+ -m, --mtu=<mtu> mtu size (default 1024)<br>\r
+ -s, --size=<size> size of message to exchange (default 65536)<br>\r
+ -a, --all Run sizes from 2 till 2^23<br>\r
+ -t, --tx-depth=<dep> size of tx queue (default 300)<br>\r
+ -n, --iters=<iters> number of exchanges (at least 2, default 1000)<br>\r
+ -b, --bidirectional measure bidirectional bandwidth (default \r
+ unidirectional)<br>\r
+ -V, --version display version number<br>\r
+ -e, --events sleep on CQ events (default poll)</p>\r
+ </blockquote>\r
+</blockquote>\r
+<h4 align="left"><a name="ibwrite_lat"></a>ib_write_lat.exe - latency test with RDMA write \r
+transactions</h4>\r
+<blockquote>\r
+ <p align="left">Usage:</p>\r
+ <blockquote>\r
+ <p align="left">ib_write_lat start a server and wait for connection<br>\r
+ ib_write_lat <host> connect to server at <host></p>\r
+ </blockquote>\r
+ <p align="left">Options:</p>\r
+ <blockquote>\r
+ <p align="left">-p, --port=<port> listen on/connect to port <port> \r
+ (default 18515)<br>\r
+ -c, --connection=<RC/UC> connection type RC/UC (default RC)<br>\r
+ -m, --mtu=<mtu> mtu size (default 1024)<br>\r
+ -d, --ib-dev=<dev> use IB device <dev> (default first device found)<br>\r
+ -i, --ib-port=<port> use port <port> of IB device (default 1)<br>\r
+ -s, --size=<size> size of message to exchange (default 1)<br>\r
+ -a, --all Run sizes from 2 till 2^23<br>\r
+ -t, --tx-depth=<dep> size of tx queue (default 50)<br>\r
+ -n, --iters=<iters> number of exchanges (at least 2, default 1000)<br>\r
+ -C, --report-cycles report times in cpu cycle units (default \r
+ microseconds)<br>\r
+ -H, --report-histogram print out all results (default print summary \r
+ only)<br>\r
+ -U, --report-unsorted (implies -H) print out unsorted results (default \r
+ sorted)<br>\r
+ -V, --version display version number</p>\r
+ </blockquote>\r
+</blockquote>\r
+<h4 align="left"><a name="ibwrite_bw"></a>ib_write_bw.exe - BW test with RDMA write transactions</h4>\r
+<blockquote>\r
+ <p align="left">Usage:</p>\r
+ <blockquote>\r
+ <p align="left">ib_write_bw \r
+ # start a server and wait for connection<br>\r
+ ib_write_bw <host> # connect to server at <host></p>\r
+ </blockquote>\r
+ <p align="left">Options:</p>\r
+ <blockquote>\r
+ <p align="left">-p, --port=<port> listen on/connect to port <port> \r
+ (default 18515)<br>\r
+ -d, --ib-dev=<dev> use IB device <dev> (default first device found)<br>\r
+ -i, --ib-port=<port> use port <port> of IB device (default 1)<br>\r
+ -c, --connection=<RC/UC> connection type RC/UC (default RC)<br>\r
+ -m, --mtu=<mtu> mtu size (default 1024)<br>\r
+ -g, --post=<num of posts> number of posts for each qp in the chain \r
+ (default tx_depth)<br>\r
+ -q, --qp=<num of qp's> Num of qp's(default 1)<br>\r
+ -s, --size=<size> size of message to exchange (default 65536)<br>\r
+ -a, --all Run sizes from 2 till 2^23<br>\r
+ -t, --tx-depth=<dep> size of tx queue (default 100)<br>\r
+ -n, --iters=<iters> number of exchanges (at least 2, default 5000)<br>\r
+ -b, --bidirectional measure bidirectional bandwidth (default \r
+ unidirectional)<br>\r
+ -V, --version display version number</p>\r
+ </blockquote>\r
+</blockquote>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
+<p align="left"><br>\r
+ </p>\r
+<h4 align="left"><a name="ttcp"></a>ttcp - Test TCP performance</h4>\r
+<blockquote>\r
+ <pre>Usage: ttcp -t [-options] host \r
+ ttcp -r [-options]\r
+Common options:\r
+ -l ## length of bufs read from or written to network (default 8192)\r
+ -u use UDP instead of TCP\r
+ -p ## port number to send to or listen at (default 5001)\r
+ -A align the start of buffers to this modulus (default 16384)\r
+ -O start buffers at this offset from the modulus (default 0)\r
+ -d set SO_DEBUG socket option\r
+ -b ## set socket buffer size (if supported)\r
+ -f X format for rate: k,K = kilo{bit,byte}; m,M = mega; g,G = giga\r
+Options specific to -t:\r
+ -n## number of source bufs written to network (default 2048)\r
+ -D don't buffer TCP writes (sets TCP_NODELAY socket option)\r
+Options specific to -r:\r
+ -B for -s, only output full blocks as specified by -l (for TAR)\r
+ -T "touch": access each byte as it's read</pre>\r
+ <p align="left">Requires a receiver (server) side and a transmitter (client) \r
+ side, host1 and host2 are IPoIB connected hosts.</p>\r
+ <p align="left">at host1 (receiver) \r
+ ttcp -r -f M -l 4096</p>\r
+ <p align="left">at host2 (transmitter) ttcp -t -f M -l \r
+ 4096 -n1000 host1</p>\r
+</blockquote>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
+<p align="left"> </p>\r
+<p align="left"> </p>\r
+<h2 align="left"><a name="diags"></a>Diagnostics</h2>\r
+<p align="left"> </p>\r
+<h3 align="left"><a name="iblimits"></a>ib_limits - Infiniband verbs tests</h3>\r
+<p align="left">Usage: ib_limits [options]</p>\r
+<blockquote>\r
+ <p align="left">Options:<br>-m or --memory<br> Direct ib_limits to test memory registration<br>-c or --cq<br> Direct ib_limits to test CQ creation<br>-r or --resize_cq<br> direct ib_limits to test CQ resize<br>-q or --qp<br> Directs ib_limits to test QP creation<br>-v or --verbose<br> Enable verbosity level to debug console.<br>-h or --help<br> Display this usage info then exit.</p>\r
+</blockquote>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
+<p align="left"> </p>\r
+<h3 align="left"><a name="cmtest"></a>cmtest - Connection Manager Tests</h3>\r
+<p>Usage: cmtest [options]</p>\r
+<p> Options:</p>\r
+<blockquote>\r
+ <p> -s --server This option directs cmtest to act as a Server<br>\r
+ -l\r
+ <lid>--local\r
+ <lid>This option specifies the local endpoint.<br>\r
+ -r\r
+ <lid>--remote\r
+ <lid>This option specifies the remote endpoint.<br>\r
+ -c\r
+ <number>--connect\r
+ <number>This option specifies the number of connections to open. Default of \r
+ 1.<br>\r
+ -m\r
+ <bytes>--msize\r
+ <bytes>This option specifies the byte size of each message. Default is 100 \r
+ bytes.<br>\r
+ -n\r
+ <number>--nmsgs\r
+ <number>This option specifies the number of messages to send at a time.<br>\r
+ -p --permsg This option indicates if a separate buffer should be used per \r
+ message. Default is one buffer for all messages.<br>\r
+ -i\r
+ <number>--iterate\r
+ <number>This option specifies the number of times to loop through 'nmsgs'. \r
+ Default of 1.<br>\r
+ -v --verbose This option enables verbosity level to debug console.<br>\r
+ -h --help Display this usage info then exit.</p>\r
+</blockquote>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
+<p align="left"> </p>\r
+<p align="left"> </p>\r
+<h3 align="left"><a name="printip"></a>PrintIP - print ip adapters and their addresses</h3>\r
+<blockquote>\r
+ <p align="left">PrintIP is used to print IP adapters and their addresses, or \r
+ ARP (Address Resolution Protocol) and IP address.<br>\r
+ <br>\r
+ Usage:<br>\r
+ printip <print_ips><br>\r
+ printip <remoteip> <ip> \r
+ (example printip remoteip 10.10.2.20)</p>\r
+</blockquote>\r
+<h3 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h3>\r
+<p align="left"> </p>\r
+<h3 align="left">\r
+<br>\r
+<a name="vstat"></a>vstat - HCA Stats and Counters</h3>\r
+<blockquote>\r
+ <p align="left">Display HCA (Host channel Adapter) attributes.</p>\r
+ <p align="left">Usage: vstat [-v] [-c]<br>\r
+ -v - verbose mode<br>\r
+ -c - HCA error/statistic \r
+ counters</p>\r
+</blockquote>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
+<p align="left"> </p>\r
+<h2 align="left"><a name="opensm"></a>Subnet Management with OpenSM Rev: openib-1.2.0</h2>\r
+<p align="left">A single running process (opensm.exe) is required to configure \r
+and thus make an Infiniband subnet useable. For most cases, InfiniBand \r
+Subnet Management as a Windows service is sufficient to correctly configure most \r
+InfiniBand fabrics.</p>\r
+<p align="left">The Infiniband subnet management process (opensm) may exist on a \r
+Windows (WinOF) node or a Linux (OFED) node.<br>\r
+<br>\r
+Limit the number of OpenSM processes per IB fabric; one SM is sufficient \r
+although redundant SMs are supported. You do not need a Subnet Manager per \r
+node/system.</p>\r
+<h4>OpenIB Subnet Management as a Windows Service</h4>\r
+<p>InfiniBand subnet management (OpenSM), as a Windows service, is installed by default, although it is NOT \r
+started by default. There are two ways to enable the InfiniBand Subnet \r
+Management service.</p>\r
+<ol style="margin-bottom: 0in">\r
+ <li>Reset the installed OpenSM service "InfiniBand Subnet Management" to \r
+ start automatically; See My Computer->Manage->Device Manager->Services->InfiniBand \r
+ subnet Management->Start.<br>\r
+ </li>\r
+ <li>Install OpenSM as a 'running' Windows service:<br>\r
+ Request a 'Custom' install, selecting the OpenSM_service install feature. \r
+ Once the installation has completed, check the running InfiniBand Subnet \r
+ Management service status via the Windows service manager (see #1).</li>\r
+</ol>\r
+<p> </p>\r
+<hr>\r
+<h4 align="left">Manual InfiniBand Subnet Management from a command window</h4>\r
+<p align="left">Usage: opensm.exe [options]</p>\r
+<p align="left">Options:</p>\r
+<blockquote>\r
+ <p align="left">-c<br>\r
+ --cache-options</p>\r
+ <blockquote>\r
+ <p align="left">Cache the given command line options into the file<br>\r
+ /var/cache/osm/opensm.opts for use next invocation<br>\r
+ The cache directory can be changed by the environment<br>\r
+ variable OSM_CACHE_DIR</p>\r
+ </blockquote>\r
+ <p align="left">-g[=]<GUID in hex><br>\r
+ --guid[=]<GUID in hex></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies the local port GUID value with \r
+ which OpenSM should bind. OpenSM may be<br>\r
+ bound to 1 port at a time. If GUID given is 0, OpenSM displays a \r
+ list of possible port GUIDs and waits for user input. Without -g, OpenSM \r
+ trys to use the default port.</p>\r
+ </blockquote>\r
+ <p align="left">-l <LMC><br>\r
+ --lmc <LMC></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies the subnet's LMC value.<br>\r
+ The number of LIDs assigned to each port is 2^LMC.<br>\r
+ The LMC value must be in the range 0-7.<br>\r
+ LMC values > 0 allow multiple paths between ports.<br>\r
+ LMC values > 0 should only be used if the subnet<br>\r
+ topology actually provides multiple paths between<br>\r
+ ports, i.e. multiple interconnects between switches.<br>\r
+ Without -l, OpenSM defaults to LMC = 0, which allows<br>\r
+ one path between any two ports.</p>\r
+ </blockquote>\r
+ <p align="left">-p <PRIORITY><br>\r
+ --priority <PRIORITY></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies the SM's PRIORITY.<br>\r
+ This will effect the handover cases, where master<br>\r
+ is chosen by priority and GUID.<br>\r
+ -smkey <SM_Key><br>\r
+ This option specifies the SM's SM_Key (64 bits).<br>\r
+ This will effect SM authentication.</p>\r
+ </blockquote>\r
+ <p align="left">-r<br>\r
+ --reassign_lids</p>\r
+ <blockquote>\r
+ <p align="left"><br>\r
+ This option causes OpenSM to reassign LIDs to all end nodes. Specifying \r
+ -r on a running subnet<br>\r
+ may disrupt subnet traffic. Without -r, OpenSM attempts to \r
+ preserve existing LID assignments resolving multiple use of same LID.</p>\r
+ </blockquote>\r
+ <p align="left">-u<br>\r
+ --updn</p>\r
+ <blockquote>\r
+ <p align="left">This option activate UPDN algorithm instead of Min Hop \r
+ algorithm (default).</p>\r
+ </blockquote>\r
+ <p align="left">-a<br>\r
+ --add_guid_file <path to file></p>\r
+ <blockquote>\r
+ <p align="left">Set the root nodes for the Up/Down routing algorithm to \r
+ the guids provided in the given file (one per line)</p>\r
+ </blockquote>\r
+ <p align="left">-o<br>\r
+ --once</p>\r
+ <blockquote>\r
+ <p align="left">This option causes OpenSM to configure the subnet once, \r
+ then exit. Ports remain in the ACTIVE state.</p>\r
+ </blockquote>\r
+ <p align="left">-s <interval><br>\r
+ --sweep <interval></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies the number of seconds between \r
+ subnet sweeps. Specifying -s 0 disables sweeping.<br>\r
+ Without -s, OpenSM defaults to a sweep interval of 10 seconds.</p>\r
+ </blockquote>\r
+ <p align="left">-t <milliseconds><br>\r
+ --timeout <milliseconds></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies the time in milliseconds<br>\r
+ used for transaction timeouts.<br>\r
+ Specifying -t 0 disables timeouts.<br>\r
+ Without -t, OpenSM defaults to a timeout value of<br>\r
+ 200 milliseconds.</p>\r
+ </blockquote>\r
+ <p align="left">-maxsmps <number></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies the number of VL15 SMP MADs \r
+ allowed on the wire at any one time.<br>\r
+ Specifying -maxsmps 0 allows unlimited outstanding SMPs.<br>\r
+ Without -maxsmps, OpenSM defaults to a maximum of one outstanding SMP.</p>\r
+ </blockquote>\r
+ <p align="left">-i <equalize-ignore-guids-file><br>\r
+ -ignore-guids <equalize-ignore-guids-file></p>\r
+ <blockquote>\r
+ <p align="left">This option provides the means to define a set of ports\r
+ (by guids) that will be ignored by the link load \r
+ equalization algorithm.</p>\r
+ </blockquote>\r
+ <p align="left">-x<br>\r
+ --honor_guid2lid</p>\r
+ <blockquote>\r
+ <p align="left">This option forces OpenSM to honor the guid2lid file,\r
+ when it comes out of Standby state, if such file exists\r
+ under OSM_CACHE_DIR, and is valid.\r
+ By default this is FALSE.</p>\r
+ </blockquote>\r
+ <p align="left">-f<br>\r
+ --log_file</p>\r
+ <blockquote>\r
+ <p align="left">This option defines the log to be the given file. By \r
+ default the log goes to %SystemRoot%\temp\osm.log.<br>\r
+ For the log to go to standard output use -f stdout.</p>\r
+ </blockquote>\r
+ <p align="left">-e<br>\r
+ --erase_log_file</p>\r
+ <blockquote>\r
+ <p align="left">This option will cause deletion of the log file \r
+ (if it previously exists). By default, the log file is accumulative.</p>\r
+ </blockquote>\r
+ <p align="left">-y<br>\r
+ --stay_on_fatal</p>\r
+ <blockquote>\r
+ <p align="left">This option will cause SM not to exit on fatal \r
+ initialization\r
+ issues: if SM discovers duplicated guids or 12x link with\r
+ lane reversal badly configured.\r
+ By default, the SM will exit on these errors.</p>\r
+ </blockquote>\r
+ <p align="left">-v<br>\r
+ --verbose</p>\r
+ <blockquote>\r
+ <p align="left">This option increases the log verbosity level.\r
+ The -v option may be specified multiple times\r
+ to further increase the verbosity level. \r
+ See the -vf option for more information about.\r
+ log verbosity.</p>\r
+ </blockquote>\r
+ <p align="left">-V</p>\r
+ <blockquote>\r
+ <p align="left">This option sets the maximum verbosity level and\r
+ forces log flushing.<br>\r
+ The -V is equivalent to '-vf 0xFF -d 2'.\r
+ See the -vf option for more information about\r
+ log verbosity.</p>\r
+ </blockquote>\r
+ <p align="left">-D <flags></p>\r
+ <blockquote>\r
+ <p align="left">This option sets the log verbosity level. A flags \r
+ field must follow the -D option.<br>\r
+ A bit set/clear in the flags enables/disables a specific log level as \r
+ follows:<br>\r
+ BIT LOG LEVEL ENABLED<br>\r
+ ---- -----------------<br>\r
+ 0x01 - ERROR (error messages)<br>\r
+ 0x02 - INFO (basic messages, low volume)<br>\r
+ 0x04 - VERBOSE (interesting stuff, moderate volume)<br>\r
+ 0x08 - DEBUG (diagnostic, high volume)<br>\r
+ 0x10 - FUNCS (function entry/exit, very high volume)<br>\r
+ 0x20 - FRAMES (dumps all SMP and GMP frames)<br>\r
+ 0x40 - ROUTING (dump FDB routing information)<br>\r
+ 0x80 - currently unused.<br>\r
+ Without -D, OpenSM defaults to ERROR + INFO (0x3).<br>\r
+ Specifying -D 0 disables all messages.<br>\r
+ Specifying -D 0xFF enables all messages (see -V).<br>\r
+ High verbosity levels may require increasing the transaction timeout \r
+ with the -t option.</p>\r
+ </blockquote>\r
+ <p align="left">-d <number><br>\r
+ --debug <number></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies a debug option. These options are \r
+ not normally needed. The number following -d selects the debug option to \r
+ enable as follows:<br>\r
+ OPT Description<br>\r
+ --- -----------------<br>\r
+ -d0 - Ignore other SM nodes<br>\r
+ -d1 - Force single threaded dispatching<br>\r
+ -d2 - Force log flushing after each log message<br>\r
+ -d3 - Disable multicast support<br>\r
+ -d4 - Put OpenSM in memory tracking mode<br>\r
+ -d10 - Put OpenSM in testability mode<br>\r
+ Without -d, no debug options are enabled</p>\r
+ </blockquote>\r
+ <p align="left">-h<br>\r
+ --help</p>\r
+ <blockquote>\r
+ <p align="left">Display this usage info then exit.</p>\r
+ </blockquote>\r
+ <p align="left">-?</p>\r
+ <blockquote>\r
+ <p align="left">Display this usage info then exit.</p>\r
+ </blockquote>\r
+</blockquote>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
+<h3 align="left"> </h3>\r
+<h3 align="left"><a name="osmtest"></a>Osmtest - Subnet Management Tests</h3>\r
+<p align="left">Invoke open subnet management tests.</p>\r
+<blockquote>\r
+ <p align="left"> Usage: osmtest [options]</p>\r
+ <p align="left">Options:</p>\r
+ <blockquote>\r
+ <p align="left"> -f <c|a|v|s|e|f|m|q|t><br>\r
+ --flow <c|a|v|s|e|f|m|q|t></p>\r
+\r
+ <p align="left">This option directs osmtest to run a specific flow:</p>\r
+ <p align="left">FLOW DESCRIPTIONS<br>\r
+ c = create an inventory file with all nodes, ports & paths.<br>\r
+ a = run all validation tests (expecting an input inventory)<br>\r
+ v = only validate the given inventory file.<br>\r
+ s = run service registration, un-registration and lease.<br>\r
+ e = run event forwarding test.<br>\r
+ f = flood the SA with queries accoring to the stress mode.<br>\r
+ m = multicast flow.<br>\r
+ q = QoS info - VLArb and SLtoVL tables.<br>\r
+ t = run trap 64/65 flow; requires running an external tool.<br>\r
+ (default is all but QoS).</p>\r
+ \r
+ <p align="left">-w <trap_wait_time><br>\r
+ --wait <trap_wait_time></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies the wait time for trap 64/65 \r
+ in seconds.<br>\r
+ It is used only when running -f t - the trap 64/65 flow<br>\r
+ (default to 10 sec).</p>\r
+ </blockquote>\r
+ <p align="left">-d <number><br>\r
+ --debug <number></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies a debug option.\r
+ These options are not normally needed.<br>\r
+ The number following -d selects the debug\r
+ option to enable as follows:<br>\r
+ OPT Description<br>\r
+ --- -----------------<br>\r
+ -d0 - Unused.<br>\r
+ -d1 - Do not scan/compare path records.<br>\r
+ -d2 - Force log flushing after each log message.<br>\r
+ -d3 - Use mem tracking.<br>\r
+ Without -d, no debug options are enabled.</p>\r
+ </blockquote>\r
+ <p align="left">-m <LID in hex><br>\r
+ --max_lid <LID in hex></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies the maximal LID number to be \r
+ searched\r
+ for during inventory file build (default to 100).</p>\r
+ </blockquote>\r
+ <p align="left">-g <GUID in hex><br>\r
+ --guid <GUID in hex></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies the local port GUID value\r
+ with which osmtest should bind. osmtest may be\r
+ bound to 1 port at a time.\r
+ Without -g, osmtest displays a menu of possible\r
+ port GUIDs and waits for user input.</p>\r
+ </blockquote>\r
+ <p align="left">-h<br>\r
+ --help</p>\r
+ <blockquote>\r
+ <p align="left">Display this usage info then exit.</p>\r
+ </blockquote>\r
+ <p align="left">-i <filename><br>\r
+ --inventory <filename></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies the name of the inventory \r
+ file.\r
+ Normally, osmtest expects to find an inventory file,\r
+ which osmtest uses to validate real-time information\r
+ received from the SA during testing.\r
+ If -i is not specified, osmtest defaults to the file\r
+ 'osmtest.dat'.<br>\r
+ See the -c option for related information.</p>\r
+ </blockquote>\r
+ <p align="left">-s<br>\r
+ --stress</p>\r
+ <blockquote>\r
+ <p align="left">This option runs the specified stress test instead \r
+ of the normal test suite.<br>\r
+ Stress test options are as follows:<br>\r
+ OPT Description<br>\r
+ --- -----------------<br>\r
+ -s1 - Single-MAD response SA queries .<br>\r
+ -s2 - Multi-MAD (RMPP) response SA queries.<br>\r
+ -s3 - Multi-MAD (RMPP) Path Record SA queries.<br>\r
+ Without -s, stress testing is not performed.</p>\r
+ </blockquote>\r
+ <p align="left">-M<br>\r
+ --Multicast_Mode</p>\r
+ <blockquote>\r
+ <p align="left">This option specify length of Multicast test :<br>\r
+ OPT Description<br>\r
+ --- -----------------<br>\r
+ -M1 - Short Multicast Flow (default) - single mode.<br>\r
+ -M2 - Short Multicast Flow - multiple mode.<br>\r
+ -M3 - Long Multicast Flow - single mode.<br>\r
+ -M4 - Long Multicast Flow - multiple mode.<br>\r
+ Single mode - Osmtest is tested alone , with no other <br>\r
+ apps that interact vs. OpenSM MC.<br>\r
+ Multiple mode - Could be run with other apps using MC vs.<br>\r
+ OpenSM. Without -M, default flow testing is performed.</p>\r
+ </blockquote>\r
+ <p align="left">-t <milliseconds></p>\r
+ <blockquote>\r
+ <p align="left">This option specifies the time in milliseconds used \r
+ for transaction timeouts.<br>\r
+ Specifying -t 0 disables timeouts.<br>\r
+ Without -t, osmtest defaults to a timeout value of 1 second.</p>\r
+ </blockquote>\r
+ <p align="left">-l<br>\r
+ --log_file</p>\r
+ <blockquote>\r
+ <p align="left">This option defines the log to be the given file.<br>\r
+ By default the log goes to stdout.</p>\r
+ </blockquote>\r
+ <p align="left">-v</p>\r
+ <blockquote>\r
+ <p align="left">This option increases the log verbosity level. The \r
+ -v option may be specified multiple times<br>\r
+ to further increase the verbosity level. See the -vf option for more \r
+ information about log verbosity.</p>\r
+ </blockquote>\r
+ <p align="left">-V</p>\r
+ <blockquote>\r
+ <p align="left">This option sets the maximum verbosity level and \r
+ forces log flushing.<br>\r
+ The -V is equivalent to '-vf 0xFF -d 2'.<br>\r
+ See the -vf option for more information about log verbosity.</p>\r
+ </blockquote>\r
+ <p align="left">-vf <flags></p>\r
+ <blockquote>\r
+ <p align="left">This option sets the log verbosity level. A flags \r
+ field must follow the -vf option.<br>\r
+ A bit set/clear in the flags enables/disables a specific log level \r
+ as follows:<br>\r
+ BIT LOG LEVEL ENABLED<br>\r
+ ---- -----------------<br>\r
+ 0x01 - ERROR (error messages)<br>\r
+ 0x02 - INFO (basic messages, low volume)<br>\r
+ 0x04 - VERBOSE (interesting stuff, moderate volume)<br>\r
+ 0x08 - DEBUG (diagnostic, high volume)<br>\r
+ 0x10 - FUNCS (function entry/exit, very high volume)<br>\r
+ 0x20 - FRAMES (dumps all SMP and GMP frames)<br>\r
+ 0x40 - currently unused.<br>\r
+ 0x80 - currently unused.<br>\r
+ Without -vf, osmtest defaults to ERROR + INFO (0x3).<br>\r
+ Specifying -vf 0 disables all messages.<br>\r
+ Specifying -vf 0xFF enables all messages (see -V).<br>\r
+ High verbosity levels may require increasing<br>\r
+ the transaction timeout with the -t option.</p>\r
+ </blockquote>\r
+ </blockquote>\r
+</blockquote>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
+<h3 align="left"> </h3>\r
+<h3 align="left"><br>\r
+<a name="ibtrapgen"></a>ibtrapgen - Generate Infiniband subnet management traps</h3>\r
+<p align="left">Usage: ibtrapgen -t|--trap_num <TRAP_NUM> -n|--number <NUM_TRAP_CREATIONS><br>\r
+ \r
+-r|--rate <TRAP_RATE> -l|--lid <LIDADDR> <br>\r
+ \r
+-s|--src_port <SOURCE_PORT> -p|--port_num <PORT_NUM><br>\r
+<br>\r
+Options: one of the following optional flows:</p>\r
+<blockquote>\r
+ <p align="left">-t <TRAP_NUM><br>\r
+ --trap_num <TRAP_NUM><br>\r
+ This option specifies the \r
+ number of the trap to generate. Valid values are 128-131.<br>\r
+ -n <NUM_TRAP_CREATIONS><br>\r
+ --number <NUM_TRAP_CREATIONS><br>\r
+ This option specifies the \r
+ number of times to generate this trap.<br>\r
+ If not specified - \r
+ default to 1.<br>\r
+ -r <TRAP_RATE><br>\r
+ --rate <TRAP_RATE><br>\r
+ This option specifies the \r
+ rate of the trap generation.<br>\r
+ What is the time period \r
+ between one generation and another?<br>\r
+ The value is given in \r
+ miliseconds. <br>\r
+ If the number of trap \r
+ creations is 1 - this value is ignored.<br>\r
+ -l <LIDADDR><br>\r
+ --lid <LIDADDR><br>\r
+ This option specifies the \r
+ lid address from where the trap should be generated.<br>\r
+ -s <SOURCE_PORT><br>\r
+ --src_port <SOURCE_PORT><br>\r
+ This option specifies the \r
+ port number from which the trap should<br>\r
+ be generated. If trap \r
+ number is 128 - this value is ignored (since<br>\r
+ trap 128 is not sent with \r
+ a specific port number)<br>\r
+ -p <port num><br>\r
+ --port_num <port num><br>\r
+ This is the port number \r
+ used for communicating with the SA.<br>\r
+ -h<br>\r
+ --help<br>\r
+ Display this usage info \r
+ then exit.<br>\r
+ -o<br>\r
+ --out_log_file<br>\r
+ This option defines the \r
+ log to be the given file.<br>\r
+ By default the log goes \r
+ to stdout.<br>\r
+ -v<br>\r
+ This option increases the \r
+ log verbosity level.<br>\r
+ The -v option may be \r
+ specified multiple times to further increase the verbosity level.<br>\r
+ See the -vf option for \r
+ more information about log verbosity.<br>\r
+ -V<br>\r
+ This option sets the \r
+ maximum verbosity level and forces log flushing.<br>\r
+ The -V is equivalent to \r
+ '-vf 0xFF -d 2'.<br>\r
+ See the -vf option for \r
+ more information about. log verbosity.<br>\r
+ -x <flags><br>\r
+ This option sets the log \r
+ verbosity level.<br>\r
+ A flags field must follow \r
+ the -vf option.<br>\r
+ A bit set/clear in the \r
+ flags enables/disables a<br>\r
+ specific log level as \r
+ follows:</p>\r
+ <blockquote>\r
+ <p align="left">BIT LOG LEVEL ENABLED<br>\r
+ ---- -----------------<br>\r
+ 0x01 - ERROR (error messages)<br>\r
+ 0x02 - INFO (basic messages, low volume)<br>\r
+ 0x04 - VERBOSE (interesting stuff, moderate volume)<br>\r
+ 0x08 - DEBUG (diagnostic, high volume)<br>\r
+ 0x10 - FUNCS (function entry/exit, very high volume)<br>\r
+ 0x20 - FRAMES (dumps all SMP and GMP frames)<br>\r
+ 0x40 - currently unused.<br>\r
+ 0x80 - currently unused.<br>\r
+ Without -x, ibtrapgen defaults to ERROR + INFO (0x3).<br>\r
+ Specifying -x 0 disables all messages.<br>\r
+ Specifying -x 0xFF enables all messages (see -V).</p>\r
+ </blockquote>\r
+</blockquote>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
+<p align="left"> </p>\r
+<p align="left"> </p>\r
+<h2 align="left"><a name="IPoIB"></a>IPoIB - Internet Protocols over InfiniBand</h2>\r
+<p align="left">IPoIB enables the use of Internet Protocol utilities (e.g., ftp, \r
+telnet) to function correctly over an Infiniband fabric. IPoIB is implemented as \r
+an NDIS Miniport driver with a WDM lower edge.</p>\r
+<p align="left">The IPoIB Network adapters are \r
+located via 'My Computer->Manage->Device Manager->Network adapters->IPoIB'.<br>\r
+'My \r
+Network Places->Properties' will display IPoIB Local Area Connection instances and should be used to \r
+configure IP addresses for the IPoIB interfaces; one Local Area Connection \r
+instance per HCA port. The IP \r
+(Internet Protocol) address bound to the IPoIB adapter instance can be assigned \r
+by DHCP or as a static IP addresses via<br>\r
+'My Network Places->Properties->Local \r
+Area Connection X->Properties->(General Tab)Internet Protocol(TCP/IP)->Properties'.</p>\r
+<p align="left">When the subnet manager (opensm) configures/sweeps the local \r
+Infiniband HCA, the Local Area Connection will become enabled. If you discover \r
+the Local Area Connection to be disabled, then likely your subnet manager \r
+(opensm) is not running or functioning correctly.</p>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
+<p align="left"> </p>\r
+<p align="left"> </p>\r
+<h2 align="left"><a name="winsockdirect"></a>Winsock Direct Service Provider</h2>\r
+<p align="left">Winsock Direct (WSD) is Microsoft's proprietary protocol that \r
+predates SDP (Sockets Direct Protocol) for accelerating TCP/IP applications by \r
+using RDMA hardware. Microsoft had a significant role in defining the SDP \r
+protocol, hence SDP and WSD are remarkably similar, though unfortunately \r
+incompatible.<br>\r
+<br>\r
+WSD is made up of two parts, the winsock direct switch and the winsock direct \r
+provider. The WSD switch is in the winsock DLL that ships in all editions of \r
+Windows Server 2003, and is responsible for routing socket traffic over either \r
+the regular TCP/IP stack, or offload it to a WSD provider. The WSD provider is a \r
+hardware specific DLL that implements connection management and data transfers \r
+over particular RDMA hardware.</p>\r
+<p align="left">The WSD Protocol seamlessly transports TCP \r
+ data using Infiniband data packets in 'buffered' mode or Infiniband \r
+ RDMA in 'direct' mode. Either way the user mode socket application sees no \r
+ difference in the standard Inet socket which it created other than \r
+reduced data transfer times and increased bandwidth.<br>\r
+<br>\r
+The Windows OpenFabrics release includes a WSD provider library that has been \r
+extensively tested with Microsoft Windows Server 2003.</p>\r
+<div id="tiki-main">\r
+ <div id="tiki-mid">\r
+ <table id="table1" cellSpacing="0" cellPadding="0" border="0">\r
+ <tr>\r
+ <td id="centercolumn">\r
+ <div id="tiki-center">\r
+ <div class="wikitext">\r
+ Environment variables can be used to change the behavior \r
+ of the WSD provider:<br>\r
+ <br>\r
+ IBWSD_NO_READ - Disables RDMA Read operations when set \r
+ to any value. Note that this variable must be used \r
+ consistently throughout the cluster or communication \r
+ will fail.<br>\r
+ <br>\r
+ IBWSD_POLL - Sets the number of times to poll the \r
+ completion queue after processing completions in \r
+ response to a CQ event. Reduces latency at the cost of \r
+ CPU utilization. Default is 500.<br>\r
+ <br>\r
+ IBWSD_SA_RETRY - Sets the number of times to retry SA \r
+ query requests. Default is 4, can be increased if \r
+ connection establishment fails.<br>\r
+ <br>\r
+ IBWSD_SA_TIMEOUT - Sets the number of milliseconds to \r
+ wait before retrying SA query requests. Default is 4, \r
+ can be increased if connection establishment fails.<br>\r
+ <br>\r
+ IBWSD_NO_IPOIB - SA query timeouts by default allow the \r
+ connection to be established over IPoIB. Setting this \r
+ environment variable to any value prevents fall back to \r
+ IPoIB if SA queries time out.<br>\r
+ <br>\r
+ IBWSD_DBG - Controls debug output when using a debug \r
+ version of the WSD provider. Takes a hex value, with \r
+ leading '0x', default value is '0x80000000'<br>\r
+ <br>\r
+ <table class="wikitable" id="table2">\r
+ <tr>\r
+ <td class="wikicell">0x00000001</td>\r
+ <td class="wikicell">DLL</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00000002</td>\r
+ <td class="wikicell">socket info</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00000004</td>\r
+ <td class="wikicell">initialization code</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00000008</td>\r
+ <td class="wikicell">WQ related functions</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00000010</td>\r
+ <td class="wikicell">Enpoints related functions</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00000020</td>\r
+ <td class="wikicell">memory registration</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00000040</td>\r
+ <td class="wikicell">CM</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00000080</td>\r
+ <td class="wikicell">connections</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00000200</td>\r
+ <td class="wikicell">socket options</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00000400</td>\r
+ <td class="wikicell">network events</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00000800</td>\r
+ <td class="wikicell">Hardware</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00001000</td>\r
+ <td class="wikicell">Overlapped I/O request</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00002000</td>\r
+ <td class="wikicell">Socket Duplication</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x00004000</td>\r
+ <td class="wikicell">Performance Monitoring</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x01000000</td>\r
+ <td class="wikicell">More verbose than \r
+ IBSP_DBG_LEVEL3</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x02000000</td>\r
+ <td class="wikicell">More verbose than \r
+ IBSP_DBG_LEVEL2</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x04000000</td>\r
+ <td class="wikicell">More verbose than \r
+ IBSP_DBG_LEVEL1</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x08000000</td>\r
+ <td class="wikicell">Verbose output</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x20000000</td>\r
+ <td class="wikicell">Function enter/exit</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x40000000</td>\r
+ <td class="wikicell">Warnings</td>\r
+ </tr>\r
+ <tr>\r
+ <td class="wikicell">0x80000000</td>\r
+ <td class="wikicell">Errors</td>\r
+ </tr>\r
+ </table>\r
+ </div>\r
+ </div>\r
+ </td>\r
+ </tr>\r
+ </table>\r
+ </div>\r
+</div>\r
+<p align="left"><br>\r
+See <a href="https://wiki.openfabrics.org/tiki-index.php?page=Winsock+Direct">\r
+https://wiki.openfabrics.org/tiki-index.php?page=Winsock+Direct</a> for the \r
+latest WSD status.</p>\r
+<h3 align="left">Install Winsock Direct Service Provider</h3>\r
+<p align="left">When the custom install option 'WSD' is selected the WSD service \r
+is automatically installed and started as part of the installation.<br>\r
+Manual control is performed via the \Program Files\WinOF\installsp.exe utility.</p>\r
+<blockquote>\r
+ <p align="left">usage: installsp [-i | -r | -l]<br>\r
+ <br>\r
+ -i Install the Winsock Direct (WSD) service provider<br>\r
+ -r Remove the WSD service provider<br>\r
+ -r <name> Remove the specified service provider<br>\r
+ -l List service providers<br>\r
+ </p>\r
+</blockquote>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
+<p align="left"> </p>\r
+<p align="left"> </p>\r
+<h2 align="left"><a name="DAT"></a>Direct Access Transport and usermode Direct Access Programing \r
+Libraries</h2>\r
+<p align="left">DAT and uDAPL are based on the 1.1 DAT specification. The DAPL \r
+(Direct Access Provider Library) provider now fully supports Infiniband RDMA and \r
+IPoIB.</p>\r
+<div align="left">\r
+ <h3 align="left"><font face="Courier New" size="3">DAT EXECUTION ENVIRONMENT</font><font face="Courier New" size="2">:</font></h3>\r
+</div>\r
+<blockquote>\r
+ <p align="left"><font face="Courier New" size="2">In order for DAT/uDAPL \r
+ programs to execute correctly, the 'dat.dll' file must be present in the \r
+ current directory,\r
+ %SystemRoot%\system32, %SystemRoot% or in the library search path.</font></p>\r
+ <p align="left"><font face="Courier New" size="2">The default WinOF \r
+ installation places the file dat.dll in the '%SystemRoot%' folder.</font></p>\r
+ <p align="left"><font face="Courier New" size="2">The DAPL configuration \r
+ file by default is defined as '%SystemDrive%\DAT\dat.conf'. This default \r
+ specification can be overriden by use of the environment variable \r
+ DAT_OVERRIDE; see following environment variable discussion.</font></p>\r
+ <p align="left"><font face="Courier New" size="2">Within the dat.conf file, \r
+ the DAPL library specification can be located as the 5th whitespace \r
+ separated line argument. By default the DAPL library file is installed as<br>\r
+ '%SystemRoot%\dapl.dll'.</font></p>\r
+ <p align="left"><font face="Courier New" size="2">Should you choose to \r
+ relocated the DAPL library file to a path where whitespace appears in the \r
+ full library path specification, then the full library file specification \r
+ must be contained within double-quotes. A side effect of the double-quotes \r
+ is the library specification is treated as a Windows string which implies \r
+ the '\' (backslash character) is treated as an 'escape' character. Hence \r
+ all backslashes in the library path must be duplicated when enclosed in \r
+ double-quotes\r
+ (e.g., "C:\\Programs Files\\WinOF\\dapl.dll").</font></p>\r
+ <p align="left"><font face="Courier New" size="2">A sample dat.conf file is \r
+ installed as '\Program Files\WinOF\dat.conf '.<br>\r
+ After the WinOF installation, move the \Program Files\WinOF\dat.conf file to \r
+ the default DAT configuration file location\r
+ '%SystemDrive%\DAT\dat.conf'.</font></p>\r
+ <p align="left"><font face="Courier New" size="2">In order to preserve existing installations, \r
+ the dat.conf file is not automatically installed in it's default location.</font></p>\r
+ <p align="left"> </p>\r
+ <h4>\r
+<u>DAT library environment variables</u>:<br>\r
+ </h4>\r
+ <pre>\r
+DAT_OVERRIDE\r
+------------\r
+Value used as the static registry configuration file, overriding the\r
+default location, 'C:\DAT\dat.conf'.\r
+\r
+Example: set DAT_OVERRIDE=%SystemDrive%\path\to\my\private.conf\r
+\r
+\r
+DAT_DBG_TYPE\r
+------------\r
+\r
+Value specifies which parts of the registry will print debugging\r
+information, valid values are \r
+\r
+DAT_OS_DBG_TYPE_ERROR = 0x1\r
+DAT_OS_DBG_TYPE_GENERIC = 0x2\r
+DAT_OS_DBG_TYPE_SR = 0x4\r
+DAT_OS_DBG_TYPE_DR = 0x8\r
+DAT_OS_DBG_TYPE_PROVIDER_API = 0x10\r
+DAT_OS_DBG_TYPE_CONSUMER_API = 0x20\r
+DAT_OS_DBG_TYPE_ALL = 0xff\r
+\r
+or any combination of these. For example you can use 0xC to get both \r
+static and dynamic registry output.\r
+\r
+Example set DAT_DBG_TYPE=0xC\r
+\r
+DAT_DBG_DEST\r
+------------ \r
+\r
+Value sets the output destination, valid values are \r
+\r
+DAT_OS_DBG_DEST_STDOUT = 0x1\r
+DAT_OS_DBG_DEST_SYSLOG = 0x2 \r
+DAT_OS_DBG_DEST_ALL = 0x3 \r
+\r
+For example, 0x3 will output to both stdout and the syslog. \r
+</pre>\r
+ <h4>\r
+<u>DAPL Provider library environment variables</u></h4>\r
+ <p>\r
+<br>\r
+<font size="2">DAPL_DBG_TYPE<br>\r
+-------------<br>\r
+<br>\r
+<font face="Courier New">Value specifies which parts of the registry will print \r
+debugging information, valid values are</font> <br>\r
+<br>\r
+</font><font face="Courier New"><font size="2">DAPL_DBG_TYPE_ERR = 0x0001<br>\r
+DAPL_DBG_TYPE_WARN = 0x0002<br>\r
+DAPL_DBG_TYPE_EVD = 0x0004<br>\r
+DAPL_DBG_TYPE_CM = 0x0008<br>\r
+DAPL_DBG_TYPE_EP = 0x0010<br>\r
+DAPL_DBG_TYPE_UTIL = 0x0020<br>\r
+DAPL_DBG_TYPE_CALLBACK = 0x0040<br>\r
+DAPL_DBG_TYPE_DTO_COMP_ERR = 0x0080<br>\r
+DAPL_DBG_TYPE_API = 0x0100<br>\r
+DAPL_DBG_TYPE_RTN = 0x0200<br>\r
+DAPL_DBG_TYPE_EXCEPTION = 0x0400<br>\r
+<br>\r
+or any combination of these. For example you can use 0xC to get both <br>\r
+EVD and CM output.<br>\r
+<br>\r
+Example set DAPL_DBG_TYPE=0xC<br>\r
+<br>\r
+<br>\r
+DAPL_DBG_DEST<br>\r
+-------------<br>\r
+<br>\r
+Value sets the output destination, valid values are <br>\r
+<br>\r
+DAPL_DBG_DEST_STDOUT = 0x1<br>\r
+DAPL_DBG_DEST_SYSLOG = 0x2 <br>\r
+DAPL_DBG_DEST_ALL = 0x3 <br>\r
+<br>\r
+For example, 0x3 will output to both stdout and the syslog.</font> </font><br>\r
+<br>\r
+<br>\r
+\r
+</p>\r
+</blockquote><hr>\r
+<h3>DAPLTEST</h3>\r
+<pre>\r
+\r
+ dapltest - test for the Direct Access Provider Library (DAPL)\r
+\r
+DESCRIPTION\r
+\r
+ Dapltest is a set of tests developed to exercise, characterize,\r
+ and verify the DAPL interfaces during development and porting.\r
+ At least two instantiations of the test must be run. One acts\r
+ as the server, fielding requests and spawning server-side test\r
+ threads as needed. Other client invocations connect to the\r
+ server and issue test requests.\r
+\r
+ The server side of the test, once invoked, listens continuously\r
+ for client connection requests, until quit or killed. Upon\r
+ receipt of a connection request, the connection is established,\r
+ the server and client sides swap version numbers to verify that\r
+ they are able to communicate, and the client sends the test\r
+ request to the server. If the version numbers match, and the\r
+ test request is well-formed, the server spawns the threads\r
+ needed to run the test before awaiting further connections.\r
+\r
+USAGE\r
+\r
+ dapltest [ -f script_file_name ]\r
+ [ -T S|Q|T|P|L ] [ -D device_name ] [ -d ] [ -R HT|LL|EC|PM|BE ]\r
+\r
+ With no arguments, dapltest runs as a server using default values,\r
+ and loops accepting requests from clients. The -f option allows\r
+ all arguments to be placed in a file, to ease test automation.\r
+ The following arguments are common to all tests:\r
+\r
+ [ -T S|Q|T|P|L ] Test function to be performed:\r
+ S - server loop\r
+ Q - quit, client requests that server\r
+ wait for any outstanding tests to\r
+ complete, then clean up and exit\r
+ T - transaction test, transfers data between \r
+ client and server\r
+ P - performance test, times DTO operations\r
+ L - limit test, exhausts various resources,\r
+ runs in client w/o server interaction\r
+ Default: S\r
+\r
+ [ -D device_name ] Specifies the name of the device (interface adapter).\r
+ Default: host-specific, look for DT_MdepDeviceName\r
+ in dapl_mdep.h\r
+\r
+ [ -d ] Enables extra debug verbosity, primarily tracing\r
+ of the various DAPL operations as they progress.\r
+ Repeating this parameter increases debug spew.\r
+ Errors encountered result in the test spewing some\r
+ explanatory text and stopping; this flag provides\r
+ more detail about what lead up to the error.\r
+ Default: zero\r
+\r
+ [ -R BE ] Indicate the quality of service (QoS) desired.\r
+ Choices are:\r
+ HT - high throughput\r
+ LL - low latency\r
+ EC - economy (neither HT nor LL)\r
+ PM - premium\r
+ BE - best effort\r
+ Default: BE\r
+\r
+USAGE - Quit test client\r
+\r
+ dapltest [Common_Args] [ -s server_name ]\r
+\r
+ Quit testing (-T Q) connects to the server to ask it to clean up and\r
+ exit (after it waits for any outstanding test runs to complete).\r
+ In addition to being more polite than simply killing the server,\r
+ this test exercises the DAPL object teardown code paths.\r
+ There is only one argument other than those supported by all tests:\r
+\r
+ -s server_name Specifies the name of the server interface.\r
+ No default.\r
+\r
+\r
+USAGE - Transaction test client\r
+\r
+ dapltest [Common_Args] [ -s server_name ]\r
+ [ -t threads ] [ -w endpoints ] [ -i iterations ] [ -Q ] \r
+ [ -V ] [ -P ] OPclient OPserver [ op3, \r
+\r
+ Transaction testing (-T T) transfers a variable amount of data between \r
+ client and server. The data transfer can be described as a sequence of \r
+ individual operations; that entire sequence is transferred 'iterations' \r
+ times by each thread over all of its endpoint(s).\r
+\r
+ The following parameters determine the behavior of the transaction test:\r
+\r
+ -s server_name Specifies the hostname of the dapltest server.\r
+ No default.\r
+\r
+ [ -t threads ] Specify the number of threads to be used.\r
+ Default: 1\r
+\r
+ [ -w endpoints ] Specify the number of connected endpoints per thread.\r
+ Default: 1\r
+\r
+ [ -i iterations ] Specify the number of times the entire sequence\r
+ of data transfers will be made over each endpoint.\r
+ Default: 1000\r
+\r
+ [ -Q ] Funnel completion events into a CNO.\r
+ Default: use EVDs\r
+\r
+ [ -V ] Validate the data being transferred.\r
+ Default: ignore the data\r
+\r
+ [ -P ] Turn on DTO completion polling\r
+ Default: off\r
+\r
+ OP1 OP2 [ OP3, ... ]\r
+ A single transaction (OPx) consists of:\r
+\r
+ server|client Indicates who initiates the\r
+ data transfer.\r
+\r
+ SR|RR|RW Indicates the type of transfer:\r
+ SR send/recv\r
+ RR RDMA read\r
+ RW RDMA write\r
+ Defaults: none\r
+\r
+ [ seg_size [ num_segs ] ]\r
+ Indicates the amount and format\r
+ of the data to be transferred.\r
+ Default: 4096 1\r
+ (i.e., 1 4KB buffer)\r
+\r
+ [ -f ] For SR transfers only, indicates\r
+ that a client's send transfer\r
+ completion should be reaped when\r
+ the next recv completion is reaped.\r
+ Sends and receives must be paired\r
+ (one client, one server, and in that\r
+ order) for this option to be used.\r
+\r
+ Restrictions: \r
+ \r
+ Due to the flow control algorithm used by the transaction test, there \r
+ must be at least one SR OP for both the client and the server. \r
+\r
+ Requesting data validation (-V) causes the test to automatically append \r
+ three OPs to those specified. These additional operations provide \r
+ synchronization points during each iteration, at which all user-specified \r
+ transaction buffers are checked. These three appended operations satisfy \r
+ the "one SR in each direction" requirement.\r
+\r
+ The transaction OP list is printed out if -d is supplied.\r
+\r
+USAGE - Performance test client\r
+\r
+ dapltest [Common_Args] -s server_name [ -m p|b ]\r
+ [ -i iterations ] [ -p pipeline ] OP\r
+\r
+ Performance testing (-T P) times the transfer of an operation.\r
+ The operation is posted 'iterations' times.\r
+\r
+ The following parameters determine the behavior of the transaction test:\r
+\r
+ -s server_name Specifies the hostname of the dapltest server.\r
+ No default.\r
+\r
+ -m b|p Used to choose either blocking (b) or polling (p)\r
+ Default: blocking (b)\r
+\r
+ [ -i iterations ] Specify the number of times the entire sequence\r
+ of data transfers will be made over each endpoint.\r
+ Default: 1000\r
+\r
+ [ -p pipeline ] Specify the pipline length, valid arguments are in \r
+ the range [0,MAX_SEND_DTOS]. If a value greater than \r
+ MAX_SEND_DTOS is requested the value will be\r
+ adjusted down to MAX_SEND_DTOS.\r
+ Default: MAX_SEND_DTOS\r
+\r
+ OP\r
+ An operation consists of:\r
+\r
+ RR|RW Indicates the type of transfer:\r
+ RR RDMA read\r
+ RW RDMA write\r
+ Default: none\r
+\r
+ [ seg_size [ num_segs ] ]\r
+ Indicates the amount and format\r
+ of the data to be transferred.\r
+ Default: 4096 1\r
+ (i.e., 1 4KB buffer)\r
+\r
+USAGE - Limit test client\r
+\r
+ Limit testing (-T L) neither requires nor connects to any server\r
+ instance. The client runs one or more tests which attempt to\r
+ exhaust various resources to determine DAPL limits and exercise\r
+ DAPL error paths. If no arguments are given, all tests are run.\r
+\r
+ Limit testing creates the sequence of DAT objects needed to\r
+ move data back and forth, attempting to find the limits supported\r
+ for the DAPL object requested. For example, if the LMR creation\r
+ limit is being examined, the test will create a set of\r
+ {IA, PZ, CNO, EVD, EP} before trying to run dat_lmr_create() to\r
+ failure using that set of DAPL objects. The 'width' parameter\r
+ can be used to control how many of these parallel DAPL object\r
+ sets are created before beating upon the requested constructor.\r
+ Use of -m limits the number of dat_*_create() calls that will\r
+ be attempted, which can be helpful if the DAPL in use supports\r
+ essentailly unlimited numbers of some objects.\r
+\r
+ The limit test arguments are:\r
+\r
+ [ -m maximum ] Specify the maximum number of dapl_*_create()\r
+ attempts.\r
+ Default: run to object creation failure\r
+\r
+ [ -w width ] Specify the number of DAPL object sets to\r
+ create while initializing.\r
+ Default: 1\r
+\r
+ [ limit_ia ] Attempt to exhaust dat_ia_open()\r
+\r
+ [ limit_pz ] Attempt to exhaust dat_pz_create()\r
+\r
+ [ limit_cno ] Attempt to exhaust dat_cno_create()\r
+\r
+ [ limit_evd ] Attempt to exhaust dat_evd_create()\r
+\r
+ [ limit_ep ] Attempt to exhaust dat_ep_create()\r
+\r
+ [ limit_rsp ] Attempt to exhaust dat_rsp_create()\r
+\r
+ [ limit_psp ] Attempt to exhaust dat_psp_create()\r
+\r
+ [ limit_lmr ] Attempt to exhaust dat_lmr_create(4KB)\r
+\r
+ [ limit_rpost ] Attempt to exhaust dat_ep_post_recv(4KB)\r
+\r
+ [ limit_size_lmr ] Probe maximum size dat_lmr_create()\r
+\r
+ Default: run all tests\r
+\r
+\r
+EXAMPLES\r
+\r
+ dapltest -T S -d -D ibnic0\r
+\r
+ Starts a server process with debug verbosity.\r
+ \r
+ dapltest -T T -d -s winIB -D ibnic0 -i 100 \\r
+ client SR 4096 2 server SR 4096 2\r
+\r
+ Runs a transaction test, with both sides\r
+ sending one buffer with two 4KB segments,\r
+ one hundred times; dapltest server is on host winIB.\r
+\r
+ dapltest -T P -d -s winIB -D JniIbdd0 -i 100 SR 4096 2\r
+\r
+ Runs a performance test, with the client \r
+ sending one buffer with two 4KB segments,\r
+ one hundred times.\r
+\r
+ dapltest -T Q -s winIB -D ibnic0\r
+\r
+ Asks the dapltest server at host 'winIB' to clean up and exit.\r
+\r
+ dapltest -T L -D ibnic0 -d -w 16 -m 1000\r
+\r
+ Runs all of the limit tests, setting up\r
+ 16 complete sets of DAPL objects, and\r
+ creating at most a thousand instances\r
+ when trying to exhaust resources.\r
+\r
+ dapltest -T T -V -d -t 2 -w 4 -i 55555 -s winIB -D ibnic0 \\r
+ client RW 4096 1 server RW 2048 4 \\r
+ client SR 1024 4 server SR 4096 2 \\r
+ client SR 1024 3 -f server SR 2048 1 -f\r
+\r
+ Runs a more complicated transaction test,\r
+ with two thread using four EPs each,\r
+ sending a more complicated buffer pattern\r
+ for a larger number of iterations,\r
+ validating the data received.\r
+\r
+\r
+BUGS (and To Do List)\r
+\r
+ Use of CNOs (-Q) is not yet supported.\r
+\r
+ Further limit tests could be added.</pre>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
+<p align="left"> </p>\r
+<p align="left"> </p>\r
+<h2 align="left"><u><a name="SRP"></a>SRP - SCSI RDMA Protocol</u></h2>\r
+<p align="left">[ADD text here]</p>\r
+<h4 align="left"><a href="#TOP"><font color="#000000"><return-to-top></font></a></h4>\r
--- /dev/null
+<html>\r
+\r
+<head>\r
+<meta http-equiv=Content-Type content="text/html; charset=windows-1252">\r
+<meta name=Generator content="Microsoft Word 11 (filtered)">\r
+\r
+<style>\r
+<!--\r
+ /* Font Definitions */\r
+ @font-face\r
+ {font-family:Wingdings;\r
+ panose-1:5 0 0 0 0 0 0 0 0 0;}\r
+@font-face\r
+ {font-family:"MS Mincho";\r
+ panose-1:2 2 6 9 4 2 5 8 3 4;}\r
+@font-face\r
+ {font-family:"\@MS Mincho";\r
+ panose-1:2 2 6 9 4 2 5 8 3 4;}\r
+ /* Style Definitions */\r
+ p.MsoNormal, li.MsoNormal, div.MsoNormal\r
+ {margin:0in;\r
+ margin-bottom:.0001pt;\r
+ font-size:12.0pt;\r
+ font-family:"Times New Roman";}\r
+h1\r
+ {margin-right:0in;\r
+ margin-left:0in;\r
+ font-size:24.0pt;\r
+ font-family:"Times New Roman";\r
+ font-weight:bold;}\r
+h2\r
+ {margin-right:0in;\r
+ margin-left:0in;\r
+ font-size:18.0pt;\r
+ font-family:"Times New Roman";\r
+ font-weight:bold;}\r
+h3\r
+ {margin-right:0in;\r
+ margin-left:0in;\r
+ font-size:13.5pt;\r
+ font-family:"Times New Roman";\r
+ font-weight:bold;}\r
+h4\r
+ {margin-right:0in;\r
+ margin-left:0in;\r
+ font-size:12.0pt;\r
+ font-family:"Times New Roman";\r
+ font-weight:bold;}\r
+a:link, span.MsoHyperlink\r
+ {color:blue;\r
+ text-decoration:underline;}\r
+a:visited, span.MsoHyperlinkFollowed\r
+ {color:blue;\r
+ text-decoration:underline;}\r
+p.MsoPlainText, li.MsoPlainText, div.MsoPlainText\r
+ {margin:0in;\r
+ margin-bottom:.0001pt;\r
+ font-size:10.0pt;\r
+ font-family:"Courier New";}\r
+p\r
+ {margin-right:0in;\r
+ margin-left:0in;\r
+ font-size:12.0pt;\r
+ font-family:"Times New Roman";}\r
+@page Section1\r
+ {size:8.5in 11.0in;\r
+ margin:1.0in 65.95pt 1.0in 65.95pt;}\r
+div.Section1\r
+ {page:Section1;}\r
+ /* List Definitions */\r
+ ol\r
+ {margin-bottom:0in;}\r
+ul\r
+ {margin-bottom:0in;}\r
+-->\r
+</style>\r
+\r
+</head>\r
+\r
+<body lang=EN-US link=blue vlink=blue>\r
+\r
+<div class=Section1>\r
+\r
+<h1 align=center style='text-align:left'><img width=107 height=93\r
+src=openfabrics.gif></h1>\r
+\r
+<h1 align=center style='text-align:center'>Windows OpenFabrics </h1>\r
+\r
+<h1 align=center style='text-align:center'>1.0 Release Notes</h1>\r
+\r
+<h3 align=center style='text-align:center'>\r
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->06/04/2007<!--webbot bot="Timestamp" endspan i-checksum="12566" --></h3>\r
+\r
+<div class=MsoNormal align=center style='text-align:center'>\r
+\r
+<hr size=2 width="100%" align=center>\r
+\r
+</div>\r
+\r
+<h2><u>Overview</u></h2>\r
+\r
+<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Times New Roman"'>The\r
+Windows OpenFabrics (WinOF) release package is composed of software modules\r
+intended for use on Microsoft Windows based computer systems connected via an\r
+InfiniBand fabric.</span></p>\r
+\r
+<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Times New Roman"'> Binary\r
+files from the openib-windows developers release tree <a\r
+href="http://openib.tc.cornell.edu/downloads/binaries/1.0.0.614">http://openib.tc.cornell.edu/downloads/binaries/1.0.0.614</a>\r
+are packaged into an InstallShield single file install package referred to as\r
+the Windows OpenFabrics (WinOF) release.</span></p>\r
+\r
+<p>The Windows OpenFabrics (WinOF) release package contains the following:<br>\r
+<br>\r
+OpenFabrics InfiniBand core drivers and Upper Level Protocols (ULPs):</p>\r
+<ul>\r
+ <li>\r
+ <p style="text-indent: -.25in; margin-left: .5in"><span dir="LTR">MTHCA -<span style='background-position: 0% 0%; mso-highlight:yellow; background-image:none; background-repeat:repeat; background-attachment:scroll'> \r
+ Mellanox </span></span><st1:stockticker>\r
+ <span\r
+ style='background-position: 0% 0%; mso-highlight:yellow; background-image:none; background-repeat:repeat; background-attachment:scroll'>HCA</span></st1:stockticker><span\r
+style='background-position: 0% 0%; mso-highlight:yellow; background-image:none; background-repeat:repeat; background-attachment:scroll'> low level driver; See list of\r
+supported devices below<br>\r
+ </span></li>\r
+ <li>\r
+ <p style="text-indent: -.25in; margin-left: .5in">\r
+ <span style="background-position: 0% 0%">Infiniband Core components<br>\r
+ </span></li>\r
+ <li>\r
+ <p style="text-indent: -.25in; margin-left: .5in">Upper Layer Protocols: \r
+ IPoIB, WSD, SRP Initiator and uDAPL</li>\r
+</ul>\r
+\r
+<p>OpenFabrics utilities:</p>\r
+\r
+<ul>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>OpenSM: InfiniBand fabric Subnet Manager</span></p>\r
+ </li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>Performance tests</span></p>\r
+ </li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>Diagnostic tools</span></p>\r
+ </li>\r
+</ul>\r
+\r
+<p>Documentation</p>\r
+\r
+<ul>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>User's manual</span></p>\r
+ </li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>Release Notes</span></p>\r
+ </li>\r
+</ul>\r
+\r
+<h2> </h2>\r
+<h2><u>Supported Platforms, Operating Systems and Infiniband Hardware</u></h2>\r
+\r
+<h4>CPU architectures</h4>\r
+\r
+<ul>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>x64 (x86_64, amd64)</span></p>\r
+ </li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>x86</span></p>\r
+ </li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>IA64</span></p>\r
+ </li>\r
+</ul>\r
+\r
+<h4>Operating Systems</h4>\r
+\r
+<ul>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>Windows Server 2003</span></p>\r
+ </li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>Windows Server 2003 Compute Cluster Edition</span></p>\r
+ </li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>Windows XP (SP2)</span></p>\r
+ </li>\r
+</ul>\r
+\r
+<h4><u>Supported HCAs (Host Channel Adapters)</u></h4>\r
+\r
+<p>Mellanox (mthca.inf)</p>\r
+<ul>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in;mso-list:l13 level1 lfo1;\r
+tab-stops:list .5in'><![if !supportLists]><font size="3">\r
+ <span style='background-position: 0% 0%; font-style:normal; font-variant:normal; font-weight:normal; font-family:Times New Roman; mso-list:Ignore; mso-bidi-font-size:12.0pt; mso-fareast-font-family:Symbol; mso-bidi-font-family:Symbol; mso-highlight:yellow; background-image:none; background-repeat:repeat; background-attachment:scroll'>\r
+ MT23108 - InfiniHost</span></font><![endif]></p></li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in;mso-list:l13 level1 lfo1;\r
+tab-stops:list .5in'>\r
+ <span style='background-position: 0% 0%; mso-highlight:yellow; background-image:none; background-repeat:repeat; background-attachment:scroll' dir="LTR">MT25218 \96 InfiniHost III Ex, memfree</span></p>\r
+ </li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in;mso-list:l13 level1 lfo1;\r
+tab-stops:list .5in'>\r
+ <span style='background-position: 0% 0%; mso-highlight:yellow; background-image:none; background-repeat:repeat; background-attachment:scroll' dir="LTR">MT25204 \96 InfiniHost III Lx<o:p></o:p></span></p>\r
+ </li>\r
+</ul>\r
+<p>Both SDR and DDR mode of the InfiniHost III family are supported.<br><br>For official Firmware (FW) versions and update tools please see:<br>\r
+<a href="http://www.mellanox.com/support/firmware_table.php">http://www.mellanox.com/support/firmware_table.php</a></p>\r
+\r
+<h4><u>Supported Switches</u></h4>\r
+\r
+<ul>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir="LTR">QLogic</span></p>\r
+ </li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>SilverStorm</span></p>\r
+ </li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir="LTR">Voltaire</span></p>\r
+ </li>\r
+ <li>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><span dir=LTR>Flextronics</span></p>\r
+ </li>\r
+</ul>\r
+\r
+<h2> </h2>\r
+<h2><u>Installation Specifics</u></h2>\r
+\r
+<p>All installed files are located in '%SystemDrive%\Program\r
+Files\WinOF'. Installed user mode executables are designed to be run from\r
+a Command Prompt window; see 'Start->Program Files-> Windows OpenFabrics-> Command Prompt'.</p>\r
+<p>'%SystemDrive%\Program Files\WinOF' is appended to the system wide search \r
+path.</p>\r
+\r
+<p>The \91default\92 installation installs \91released/free\92 (not\r
+checked/debug) versions of drivers, libraries and executables.</p>\r
+\r
+<p>A single instance of a subnet manager, opensm.exe, must be\r
+running on a fabric connected node in order for the Infiniband fabric to be\r
+configured and useful; either Windows or Linux opensm work fine.</p>\r
+<p>It is recommended that OpenSM be run as a Windows service. A typical install will install OpenSM as a Windows service which \r
+is disabled; after an installation, choose your openSM node and start the openSM \r
+service. \r
+See the WinOF Manual for details on opensm as a service.<br>\r
+By selecting the 'OpenSM_service_enabled' feature of a 'Custom' install, an OpenSM subnet \r
+management service will be automatically started. </p>\r
+\r
+<p>Note, the opensm.exe process must continue to run in order\r
+to maintain Infiniband fabric configuration. Should the opensm.exe process die,\r
+restart the service if not automatic or re-run opensm.exe in order to continue\r
+correct fabric operation.</p>\r
+\r
+<p>For more subnet management information, consult the Windows\r
+OpenFabrics manual.</p>\r
+\r
+<p class=MsoNormal> </p>\r
+\r
+<h2><u>How to Install</u></h2>\r
+\r
+<h3>Requirements</h3>\r
+\r
+<p>Install HCA hardware prior to installing the Windows OpenFabrics Release\r
+package. Upon reboot, cancel any attempts to install new device hardware from \r
+the "Found New Hardware Wizard".</p>\r
+\r
+<p>If you have previously installed openib-windows, Windows OpenFabrics\r
+packages or vendor supplied Infiniband packages, uninstall and reboot prior to\r
+installing this version of Windows OpenFabrics.</p>\r
+\r
+<p>openib-windows uninstall:</p>\r
+\r
+<ol start=1 type=1>\r
+ <li class=MsoNormal>Stop the openSM subnet manager if it is running on the \r
+ local node.</li>\r
+ <li class=MsoNormal>Disable any Local Area Connections which are bound to the\r
+ IPoIB network adapter.</li>\r
+ <li class=MsoNormal>Uninstall the IPoIB driver - My\r
+ computer->Manage->Devices->Network Adapters->IPoIB*</li>\r
+ <li class=MsoNormal>Uninstall the Infiniband HCA device; don't forget the \r
+ System Device-> InfiniBand Fabric</li>\r
+</ol>\r
+\r
+<p> For an existing Windows OpenFabrics uninstall<br>\r
+ Programs-> Windows OpenFabrics-> Uninstall WinOF<br>\r
+ -or-<br>\r
+ Control Panel -> Add or Remove Programs-> Windows\r
+OpenFabrics->Remove.</p>\r
+\r
+<p><b>REBOOT</b></p>\r
+\r
+<p>Upon system restart, cancel the 'Found New Hardware Wizard' attempt to install \r
+drivers for newly discovered PCI device.</p>\r
+<p>'My Computer->Manage->Device Manager' should display\r
+'?Other Devices->?PCI device' which is your Infiniband HCA device.</p>\r
+\r
+<h3><u>Install</u></h3>\r
+\r
+<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>\r
+\r
+<p>From a login with administrator privileges, double-click the\r
+WinOF_arch_setup.exe file to begin the Windows OpenFabrics installation; \r
+where '_arch_' can be (_x64_ for Intel EMT64 systems or amd64, _x86_ for x86\r
+compatible systems or _ia64_ for Intel IA64 systems). </p>\r
+\r
+<p>Follow the instructions.<br>\r
+Answer 'yes' or 'Continue' to any notifier windows which reference non-signed \r
+driver installation. These non-signed driver install questions can be disabled \r
+via 'My Computer->Properties->Hardware->Driver Signing->Ignore'.</p>\r
+<p>Bottom-line - WinOF drivers in this package are not WHQL'ed although they are \r
+built from driver source which has been WHQL'ed.</p>\r
+<p> </p>\r
+<p> <font size="4">**** WARNING ****</font></p>\r
+<blockquote>\r
+ <p>Should any 'Welcome to the Found New Hardware Wizard' windows popup after the \r
+ WinOF install has started, just ignore (window will disappear in a few \r
+ seconds) or 'Cancel' the errant popup window. \r
+ For Windows Server 2003 (SP1) you can safely ignore the errant FNHW popup \r
+ window; for Windows XP (SP2) the errant FNHW popups need to be 'cancelled' \r
+ in order for the WinOF install to proceed. The report back from Microsoft on these 'Found New Hardware Wizard' windows \r
+ popping up is they are due to the fact the WinOF drivers are not Digitally \r
+ signed (non-WHQL'ed) and hence are not trusted by Windows. Even though the \r
+ Ignore warning on installation of non-signed drivers is enabled (My \r
+ Computer->Properties->Hardware->Driver Signing->Ignore) the FNHW is still \r
+ invoked. MS claims this is a 'feature'.</p>\r
+ <p>An artifact of cancelling an errant 'Found New Hardware' popup window may \r
+ induce an errant taskbar Information notifier/bubble indicating there may \r
+ have been problems installing your hardware drivers;<br>\r
+ IGNORE/cancel this information bubble, likely the device installation \r
+ proceeded without error. Check the Device Manager views for the \r
+ Infiniband HCA and IPoIB Network Adapters for initial verification of \r
+ correct installation.</p>\r
+ <p>You do need to answer 'Yes' or 'Continue' to those notifier windows which \r
+ reference non-signed driver installation. If you have previously \r
+ set My Computer->Properties->Hardware->Driver Signing->Ignore, then you will \r
+ NOT be queried about installation of non-signed drivers; although the FNHW \r
+ windows likely will occur.</p>\r
+ <p>Should the install appear to hang, look around for occluded notifier windows \r
+ waiting for a response which \r
+ are covered by existing windows.<br>\r
+ </p>\r
+</blockquote>\r
+\r
+<h4>Install types:</h4>\r
+\r
+<h4>Minimal</h4>\r
+\r
+<ul type=disc>\r
+ <li class=MsoNormal>Basics - Release Notes, Manual, Command Window</li>\r
+ <li class=MsoNormal>Tools - Subnet Management [opensm.exe, SM is installed, not \r
+ started], Performance &\r
+ Diagnostic utilities</li>\r
+ <li class=MsoNormal>IBcore - mthca HCA driver + IB fabric driver (ibal)</li>\r
+</ul>\r
+\r
+<h4>Typical</h4>\r
+\r
+<ul style='margin-top:0in' type=disc>\r
+ <li class=MsoNormal>Minimal install 'plus'</li>\r
+</ul>\r
+\r
+<ul style='margin-top:0in' type=disc>\r
+ <li class=MsoNormal>IPoIB - Internet Protocols over InfiniBand (aka, \r
+ ftp/telnet/... over IB fabric)</li>\r
+ <li class=MsoNormal>WinsockDirect - Winsock Direct Provider, service started; see \r
+ WinOF\installsp.exe -l</li>\r
+ <li class=MsoNormal>DAPL - DAT and uDAPL support</li>\r
+</ul>\r
+\r
+<h4>Custom</h4>\r
+\r
+<ul type=disc>\r
+ <li class=MsoNormal>Basics - Release Notes, Manual, Command Window</li>\r
+ <li class=MsoNormal>Tools - Subnet Management [opensm], Performance &\r
+ Diagnostic utilities</li>\r
+ <li class=MsoNormal>IB core + IB fabric driver</li>\r
+ <li class=MsoNormal>Optional:<br> IPoIB<br> \r
+ WinsockDirect<br> VNIC - Virtual Ethernet device over Infiniband<br> SRP - SCSI over RDMA Protocol<br> DAPL<br>\r
+ OpenSM_service_enabled - InfiniBand Subnet Management started as a Windows Service</li>\r
+</ul>\r
+\r
+</blockquote>\r
+\r
+<h3> </h3>\r
+<h3><u>Unattended Install using InstallShield</u></h3>\r
+\r
+<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>\r
+\r
+<div id="main-copy">\r
+ <a target="_blank" rel="external" href="http://www.installshield.com/">\r
+ InstallShield</a> is one of the oldest and most widely used application \r
+ packaging systems.<p>Installers created by InstallShield recognize the <code>\r
+ /r</code>, <code>/s</code>, <code>/sms</code>, <code>/f1</code>, and <code>\r
+ /f2</code> switches. The installer itself is invariably named\r
+ <font face="Courier New">WinOF_arch_M-m_</font><code>setup.exe</code>.</p>\r
+ <p>To perform a silent/unattended installation, you need an InstallShield \r
+ "answer file", customarily named <code>setup.iss</code>. The WinOF \r
+ distribution does not ship with such a file, but you can easily create one \r
+ during a single node installation.</p>\r
+ <p>Here is how it works. Run the installer with the <code>/r</code> \r
+ ("record") switch. Proceed through the dialogs and complete the \r
+ installation. This will create a <code>setup.iss</code> file and place it in \r
+ the <code>%WINDIR%</code> directory (see /f1 switch discussion below to \r
+ alter this behavior). This file will include all of your responses to the \r
+ InstallShield dialogs, allowing you to perform unattended installations as \r
+ if you were giving the same answers again. Simply copy <code>setup.iss</code> \r
+ to the same directory as the installer executable.</p>\r
+ <p>Once you have a <code>setup.iss</code> file, run the installer with the\r
+ <code>/s</code> ("silent") option. This will perform an unattended \r
+ installation.</p>\r
+ <p>Unfortunately, the installer will fork a separate process and exit, \r
+ meaning it will return immediately even if you run it under <code>\r
+ start /wait</code>. This makes it useless for scripting purposes. Luckily, \r
+ there is another switch, <code>/sms</code>, which will cause the installer \r
+ to pause until the installation completes.</p>\r
+ <p>Hence, for an InstallShield application, you want to provide both the\r
+ <code>/s</code> and the <code>/sms</code> switches for the unattended \r
+ install.</p>\r
+ <p>The <code>/f1<var>filename</var></code> switch allows you to specify a \r
+ fully-qualified alternate name for the <code>setup.iss</code> file. Note \r
+ that there must be <strong>no</strong> space between the <code>/f1</code> \r
+ switch and the file name. This switch works both with <code>/r</code> to \r
+ create the file and with <code>/s</code> to read it.</p>\r
+ <p>The <code>/f2<var>filename</var></code> switch specifies a log file. Once \r
+ again, there must be <strong>no</strong> space between the switch and the \r
+ file name.</p>\r
+ <p><strong>WARNING</strong>: Be careful what characters you use in these \r
+ file names, because InstallShield silently strips certain non-alphanumerics \r
+ (like hyphens).</div>\r
+<p>Recording Mechanics (how to generate an .iss answer file):</p>\r
+<ol>\r
+ <li>From a login with administrator privileges bring up a Command Window \r
+ (cmd.exe).</li>\r
+ <li>cd to where the WinOF installation file (.exe) is located, for now \r
+ assume %TEMP% (cd %TEMP%)</li>\r
+ <li>cmd-prompt> <font size="4">start/wait WinOF_arch_1-0_setup.exe /r /f1%TEMP%\WinOF.iss</font><br>\r
+ The above command creates 'WinOF.iss' in the %TEMP% directory. Yes, an \r
+ actual install is performed, be prepared.</li>\r
+</ol>\r
+<p>Unattended/Silent Install Mechanics (using the .iss answer file):</p>\r
+<ol>\r
+ <li>From a login with administrator privileges bring up a Command Window \r
+ (cmd.exe).</li>\r
+ <li>cd to where the WinOF installation file (.exe) and silent install answer \r
+ file (.iss) files are located, for now<br>\r
+ assume %TEMP% 'cd %TEMP%'</li>\r
+ <li>cmd-prompt> <font size="4">start/wait WinOF_arch_1-0_setup.exe /s /sms \r
+ /f2%TEMP%\WinOF.log<br>\r
+ </font>assumes .iss file is in the same directory.</li>\r
+ <li>When the cmd-prompt returns, the WinOF unattended install has completed. \r
+ Results can be viewed in the WinOF.log file.</li>\r
+</ol>\r
+\r
+</blockquote>\r
+\r
+<p>See <a href="http://unattended.sourceforge.net/installers.php">Unattended \r
+Installations</a> for further references.</p>\r
+<p> </p>\r
+<h3>Setting the IPoIB Interface IP Address</h3>\r
+<p>The Windows command 'netsh' will assist in assigning an IP address to an \r
+IPoIB interface.<br>\r
+By default, an IPoIB interface is configured to use DHCP. The following \r
+discussion deals with setting a static IP address on an IPoIB interface.</p>\r
+<p>Display all network interface configuration information<br>\r
+ netsh interface ip show config<br>\r
+ netsh interface ip show address \r
+"Local Area Connection 3"</p>\r
+<p>Config a static IP address for an IPoIB interface: [Local Area Connection 3 \r
+== 1st IPoIB interface], 10.10.4.300 is the assigned IP address<br>\r
+with a netmask of 255.255.255.0, the gateway is 10.10.4.1 metric is 2.</p>\r
+<p> netsh interface ip set address \r
+"Local Area Connection 3" static 10.10.4.300 255.255.255.0 10.10.4.1 2</p>\r
+<p>See <a href="http://support.microsoft.com/kb/257748">netsh</a> for further \r
+reference.</p>\r
+<p> </p>\r
+<h2><u>Uninstall</u></h2>\r
+\r
+<p>To uninstall a WinOF package</p>\r
+<ol>\r
+ <li>Programs-> Windows OpenFabrics-> Uninstall WinOF</li>\r
+ <li>Control Panel-> Add Remove Programs-> Windows OpenFabrics</li>\r
+</ol>\r
+<p>For unattended uninstalls (WinOF only, from a command window)</p>\r
+<ul>\r
+ <li>Recorded an uninstall answer file:<br>\r
+ "%ProgramFiles(x86)%\InstallShield Installation \r
+ Information\{51798BCA-98EE-43ED-95D6-CCA11E369044}\setup.exe" -runfromtemp \r
+ -l0x0409 /r /f1%TEMP%\uninstall.iss</li>\r
+ <li>Uninstal using the answer file: <br>\r
+ "%ProgramFiles(x86)%\InstallShield Installation \r
+ Information\{51798BCA-98EE-43ED-95D6-CCA11E369044}\setup.exe" -runfromtemp \r
+ -l0x0409 /s /sms /f1%TEMP%\uninstall.iss</li>\r
+ <li>see setup.exe /? for details.</li>\r
+ <li>Add/Remove Programs for InstallShield-12 uses the following registry \r
+ entries for WinOF:<br>Windows 2003 Server: HKLM\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Install_Shield_{51798BCA-98EE-43ED-95D6-CCA11E369044}\UninstallString<br>Windows XP: HKLM\Microsoft\Windows\CurrentVersion\Uninstall\Install_Shield_{51798BCA-98EE-43ED-95D6-CCA11E369044}\UninstallString</li>\r
+ <li>If for some reason the Product Code {GUID} changes, the latest code can \r
+ be located via<br>Programs-> Windows OpenFabrics-> Uninstall WinOF<right-click>Properties</li>\r
+</ul>\r
+<p> </p>\r
+\r
+<h2><u>Trouble Shooting</u></h2>\r
+<p> </p>\r
+\r
+<h3><u>Current Mellanox Firmware Revisions Matrix</u></h3><p:colorscheme\r
+ colors="#ffffff,#000000,#808080,#000000,#ffc86c,#acc5ff,#fff4b4,#c4f48a"/>\r
+\r
+<div v:shape="_x0000_s1026" style="tab-stops:.6215in">\r
+ <div class="O" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:145;\r
+mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family:"Arial Narrow";\r
+font-size:106%;color:#F2862F">\r
+ <span style="mso-special-format:bullet;\r
+position:absolute;left:-3.41%">\95</span></span><span style="font-family:"Arial Narrow";\r
+font-size:19pt;color:#F2862F"><b> </b></span></div>\r
+ <blockquote>\r
+ <div class="O1" style="mso-line-spacing:"80 0 0";mso-margin-left-alt:395;\r
+mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family:"Arial Narrow";font-size:94%;color:#241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-4.4%">\96</span></span><span style="font-family: Arial Narrow; color: #241172"><b>MT23108 \r
+ (InfiniHost) </b></span></div>\r
+ <blockquote>\r
+ <div class="O2" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:577;\r
+mso-text-indent-alt:468;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-2.71%;font-family:\r
+Wingdings">§</span>Minimal FW version: 3.3.2 </span></div>\r
+ <div class="O2" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:577;\r
+mso-text-indent-alt:468;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-2.71%;font-family:\r
+Wingdings">§</span>Optimal FW version: 3.4.0</span><span style="font-family:"Arial Narrow";font-size:\r
+16pt;color:#241172"> </span></div>\r
+ </blockquote>\r
+ <div class="O1" style="mso-line-spacing:"80 0 0";mso-margin-left-alt:395;\r
+mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family:"Arial Narrow";font-size:94%;color:#241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-4.4%">\96</span></span><b><span style="font-family: Arial Narrow; color: #241172">MT25208 \r
+ (InfiniHost III Ex, Tavor mode) </span></b></div>\r
+ <blockquote>\r
+ <div class="O2" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:577;\r
+mso-text-indent-alt:468;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-2.71%;font-family:\r
+Wingdings">§</span>Minimal FW version: 4.7.0 </span></div>\r
+ <div class="O2" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:577;\r
+mso-text-indent-alt:468;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-2.71%;font-family:\r
+Wingdings">§</span>Optimal FW version: 4.7.400<font size="4"> </font></span>\r
+ </div>\r
+ </blockquote>\r
+ <div class="O1" style="mso-line-spacing:"80 0 0";mso-margin-left-alt:395;\r
+mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family:"Arial Narrow";font-size:94%;color:#241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-4.4%">\96</span></span><span style="font-family: Arial Narrow; color: #241172"><b>MT25218 \r
+ (InfiniHost III Ex, memfree) </b></span></div>\r
+ <blockquote>\r
+ <div class="O2" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:577;\r
+mso-text-indent-alt:468;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-2.71%;font-family:\r
+Wingdings">§</span>Minimal FW version: 5.1.0 </span></div>\r
+ <div class="O2" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:577;\r
+mso-text-indent-alt:468;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-2.71%;font-family:\r
+Wingdings">§</span>Optimal FW version: 5.1.400 </span></div>\r
+ </blockquote>\r
+ <div class="O1" style="mso-line-spacing:"80 0 0";mso-margin-left-alt:395;\r
+mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-4.4%">\96</span><b>MT25204 \r
+ (InfiniHost III Lx)</b></span></div>\r
+ <blockquote>\r
+ <div class="O2" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:577;\r
+mso-text-indent-alt:468;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-2.71%;font-family:\r
+Wingdings">§</span>Minimal FW version: 1.0.800 </span></div>\r
+ <div class="O2" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:577;\r
+mso-text-indent-alt:468;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-2.71%;font-family:\r
+Wingdings">§</span>Optimal FW version: 1.1.0<b> </b></span></div>\r
+ </blockquote>\r
+ </blockquote>\r
+ <div class="O" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:145;\r
+mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family:"Arial Narrow";\r
+font-size:106%;color:#F2862F">\r
+ <span style="mso-special-format:bullet;\r
+position:absolute;left:-3.41%">\95</span></span><b><span style="font-family: Arial Narrow; ">If \r
+ HCA FW is older than minimal FW</span><span style="font-family: Arial Narrow; color: #F2862F"> </span> </b></div>\r
+ <blockquote>\r
+ <div class="O1" style="mso-line-spacing:"80 0 0";mso-margin-left-alt:395;\r
+mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172"><b>Error \r
+ reported to system event log </b></span></div>\r
+ <div class="O1" style="mso-line-spacing:"80 0 0";mso-margin-left-alt:395;\r
+mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-4.4%">\r
+ \96</span><b>HCA loads as memory controller to allow FW upgrade </b>\r
+ </span></div>\r
+ </blockquote>\r
+ <div class="O" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:145;\r
+mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #F2862F">\r
+ <span style="mso-special-format:bullet;\r
+position:absolute;left:-3.41%">\95</span></span><b><span style="font-family: Arial Narrow; ">If HCA<span style="mso-spacerun:yes"> \r
+ </span>FW is equal or newer than optimal version</span><span style="font-family: Arial Narrow; color: #F2862F"><br>\r
+ </span></b></div>\r
+ <div class="O1" style="mso-line-spacing:"80 0 0";mso-margin-left-alt:395;\r
+mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <blockquote>\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-4.4%">\r
+ \96</span><b>HCA starts OK. </b></span>\r
+ </blockquote>\r
+ </div>\r
+ <div class="O" style="mso-line-spacing:"80 20 0";mso-margin-left-alt:145;\r
+mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #F2862F">\r
+ <span style="mso-special-format:bullet;\r
+position:absolute;left:-3.41%">\95</span></span><b><span style="font-family: Arial Narrow; ">Else</span></b></div>\r
+ <blockquote>\r
+ <div class="O1" style="mso-line-spacing:"80 0 0";mso-margin-left-alt:395;\r
+mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <b>HCA loads OK. </b></span></div>\r
+ <div class="O1" style="mso-line-spacing:"80 0 0";mso-margin-left-alt:395;\r
+mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <span style="font-family: Arial Narrow; color: #241172">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-4.4%">\r
+ \96</span><b>Warning will be issued to system event log </b></span>\r
+ </div>\r
+ </blockquote>\r
+ <div class="O1" style="mso-line-spacing:"80 0 0";mso-margin-left-alt:395;\r
+mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">\r
+ <![if ppt]>\r
+ <span style="font-family:"Arial Narrow";font-size:94%;color:#241172;visibility:hidden">\r
+ <span style="mso-special-format:bullet;position:absolute;left:-4.4%">\96</span></span><![endif]><span style="font-family:"Arial Narrow";font-size:17pt;color:#241172"><b>\r
+ </b></span></div>\r
+ <div class="O" style="mso-line-spacing:"80 50 0";mso-margin-left-alt:145">\r
+ My computer-> Manage-> Event Viewer-> System Events<p>Firmware updates \r
+ are available at\r
+ <a href="http://www.mellanox.com/support/firmware_download.php">\r
+ www.mellanox.com/support/firmware_download.php</a></p>\r
+ <p> </div>\r
+</div>\r
+<h3><u>Correct Installation Validation</u></h3>\r
+<p>From the Device Manager you should find the following devices:</p>\r
+<ul>\r
+ <li>InfiniBand Host Channel Adapters -> Infinihost</li>\r
+ <li>System Devices -> InfiniBand Fabric</li>\r
+ <li>Network Adapters -> OpenIB IPoIB Adapter (an Instance per HCA port).</li>\r
+</ul>\r
+<blockquote>\r
+ <h4>Validation Test</h4>\r
+ <p>Open a WinOF command window</p>\r
+ <ol>\r
+ <li>Start->Program Files->Windows OpenFabrics -> Command \r
+Window</li>\r
+ <li>run vstat.exe to view HCA configuration.</li>\r
+ <li>If IPoIB is installed (Device Manager->Network Adapters), ping another node on the InfiniBand fabric 'ping a.b.c.d'<br>\r
+ </li>\r
+ </ol>\r
+</blockquote>\r
+<h3><u>OpenIB Subnet Management as a Windows Service</u></h3>\r
+<p>Limit the number of Subnet Managers on your fabric; one SM per fabric is \r
+sufficient, although redundant Subnet Managers are supported.</p>\r
+<ol>\r
+ <li>After a 'typical' WinOF install, OpenSM is installed as a <b>disabled</b> \r
+ Windows service named "InfiniBand Subnet Management". To start the OpenSM \r
+ service, use My computer->Manage->Device \r
+ Manager->Services->InfiniBand Subnet Manager->Start.<br>\r
+ Set the service properties to 'auto' in order to restart upon the next \r
+ system reboot.<br>\r
+ </li>\r
+ <li>Install OpenSM as an automatic/running Windows service:<br>\r
+ a) Request a 'Custom' install, selecting the 'OpenSM_service_enabled' feature. Once \r
+ the install has completed, check that the Infiniband Subnet Manager service is \r
+ running: My computer->Manage->Device Manager->Services->InfiniBand Subnet \r
+ Manager</li>\r
+</ol>\r
+<p> </p>\r
+<h3><u>Local Network Adapter Ordering</u></h3>\r
+<p>Local Network Adapter ordering, which results in the IP address advertised \r
+for the system, can be managed from<br> 'My Network Places-> Advanced Tab-> Advanced settings'<br>From the Advanced settings display, the ordering \r
+of Local Network Adapters can be \r
+reordered after the IPoIB Local Network Adapters have been installed. Please \r
+check for your desired adapter ordering.<br> </p>\r
+<h3><u>Which WinOF release is installed</u>?</h3>\r
+<p>1) Start->Programs->Windows OpenFabrics->Release Notes \r
+(2nd Line)<br>2) Driver confirmation:<br> Query My Computer-> Manage-> Device Manager-> Network \r
+Adapters-> OpenIB IPoIB Adapter-> Properties-> Driver-> Details<br> The subversion (svn) revision number will be listed under \r
+'Driver Version'. The svn revision number will match what's listed in the \r
+release<br> notes.</p>\r
+<p>WinOF 1.0 is based on svn revision 614.</p>\r
+<h3> </h3>\r
+<h3><u>DAT & uDAPL Configuration</u></h3>\r
+<p align="left">In order for DAT/uDAPL programs to execute correctly, the 'dat.dll' \r
+file must be present in the current directory,<br>\r
+%WINDIRt% or in the library search path.</p>\r
+<p align="left">The 'typical' WinOF installation places the dat.dll and dapl.dll \r
+files in the '%WINDIR%' \r
+folder (a.k.a. \Windows).</p>\r
+<p align="left">The DAPL configuration file by convention is defined as \r
+'%SystemDrive%\DAT\dat.conf'. This default specification can be overridden by use \r
+of the environment variable DAT_OVERRIDE. Such that 'DAT_OVERRIDE=D:\MyDAT\test.conf' \r
+would be a valid override specification.</p>\r
+<p align="left">Within the dat.conf file, the DAPL library specification can be \r
+located as the 5th whitespace separated line argument. By default the DAPL \r
+library file is installed as %WINDIR%\dapl.dll'.</p>\r
+<p align="left">Should you choose to relocated the DAPL library file to a path \r
+where whitespace appears in the full library path specification, then the full \r
+library file specification must be contained within double-quotes. A side effect \r
+of the double-quotes is the library specification is treated as a Windows string \r
+which implies the '\' (backslash character) is treated as an 'escape' character. \r
+Hence all backslashes in the library path must be duplicated when enclosed in \r
+double-quotes (e.g., "C:\\Programs Files\\WinOF\\dapl.dll").</p>\r
+<p align="left">A sample dat.conf file is installed as '\Program Files\WinOF\dat.conf \r
+'.<br>\r
+After the WinOF installation, move the \Program Files\WinOF\dat.conf file to the \r
+default DAT configuration file location<br>\r
+'%SystemDrive%\DAT\dat.conf'. In order to preserve existing installations, the \r
+dat.conf file is not automatically installed in it's default location.</p>\r
+<p align="left"> </p>\r
+\r
+<h2><u>Known Issues</u></h2>\r
+\r
+<ul>\r
+ <li>\r
+ <p class=MsoPlainText><font face="Times New Roman" size="3">Sometimes an \r
+ errant "Welcome to the Found New Hardware Wizard" window pops up during \r
+ InfiniBand device installation.<br>\r
+ Just 'ignore' (windows will disappear within a few seconds) or 'cancel' the FNHW popup window and proceed with installation.<br>\r
+ An artifact of the 'Cancel' operation may cause a taskbar Information bubble \r
+ to appear which incorrectly claims problems with the Infiniband device \r
+ installation; Check IB device status via the Device Manager.<br>\r
+ Microsoft claims this behavior is resultant from installation of non-signed \r
+ device drivers coupled with the IB fabric coinstaller.<br> </font></p></li>\r
+</ul>\r
+<p class=MsoPlainText><br>\r
+ </p>\r
+<p class=MsoPlainText> </p>\r
+\r
+</div>\r
+\r
+</body>\r
+\r
+</html>\r
--- /dev/null
+#\r
+# Generic DAT 1.1 configuration file [4-30-07]\r
+#\r
+\r
+# Each entry should have the following fields:\r
+# <ia_name> <api_version> <threadsafety> <default> <dapl_lib_path> \\r
+# <provider_version> <ia_params> <platform_params>\r
+\r
+# Verify %SystemRoot% == C:\Windows\r
+# This is the dapl provider configuration for HCA0 port 1\r
+\r
+IbalHca0 u1.1 nonthreadsafe default C:\Windows\dapl.dll mv_dapl.1.1 "IbalHca0 1" ""\r
+\r
+# Intel MPI\r
+#ibnic0 u1.1 threadsafe default C:\Windows\dapl.dll ri.1.1 "IbalHca0 1" " "\r
+\r
--- /dev/null
+\r
+If this file exists in %ProgramFiles%\WinOF, then an 'opensm' service will be\r
+created and started at the end of the Install process. See\r
+Device Manager->Services->InfiniBand Subnet Manager\r
+\r
+\r
projects / ~shefty / rdma-win.git / commitdiff