<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
+<h1 align=center style='text-align:center'>OpenFabrics Enterprise Distribution \r
+for Windows</h1>\r
\r
-<h1 align=center style='text-align:center'><a name="WinOF_Release_Notes">2.2 Release Notes</a></h1>\r
+<h1 align=center style='text-align:center'><a name="OFED_Release_Notes">2.3 Release Notes</a></h1>\r
\r
<h3 align=center style='text-align:center'>\r
-<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->01/13/2010<!--webbot bot="Timestamp" endspan i-checksum="12535" --></h3>\r
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->09/09/2010<!--webbot bot="Timestamp" endspan i-checksum="12639" --></h3>\r
\r
<div class=MsoNormal align=center style='text-align:center'>\r
\r
<h3><u><a href="#Local_Network_Adapter_Ordering"><font color="#000000">\r
Local Network Adapter Ordering</font></a></u></h3>\r
<h3><u><a href="#Which_WinOF_release_is_installed"><font color="#000000">\r
-Which WinOF release is installed</font></a></u><a href="#Which_WinOF_release_is_installed"><font color="#000000">?</font></a></h3>\r
+Which release is installed</font></a></u><a href="#Which_OFED_release_is_installed"><font color="#000000">?</font></a></h3>\r
<h3><u><a href="#QLogic_VNIC_Configuration"><font color="#000000">\r
QLogic VNIC Configuration</font></a></u></h3>\r
<h3><u><a href="#DAT_&_uDAPL_Configuration"><font color="#000000">\r
<BLOCKQUOTE></BLOCKQUOTE>\r
<h2><u><a name="Overview">Overview</a></u></h2>\r
\r
-<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial"'>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
+<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial"'>The OpenFabrics \r
+Enterprise Distribution release package is composed of software modules\r
+intended for use on Microsoft Windows based computer systems connected via an InfiniBand fabric.</span></p>\r
\r
<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial"'> Binary\r
files generated from the OpenIB-windows developers subversion (svn) source tree </span>\r
<font face="Arial">'<font size="3">svn://openib.tc.cornell.edu</font>'<span style='font-size:12.0pt;'> \r
-(branches\WOF2-2 svn revision <font color="#FF0000">2667</font>)\r
+(branches\OFED2-3 svn revision 2909\r
are packaged into a <a href="http://www.dalun.com/wix/default.htm">WIX \r
-(Windows Installer Xml)</a> single file install package referred to as the \r
-Windows OpenFabrics (WinOF) release 2.2.</span></font><span style='font-size:12.0pt;font-family:"Times New Roman"'><br>\r
+(Windows Installer Xml)</a> single file install package referred to as the OpenFabrics Enterprise \r
+Distribution for Windows release 2.3.</span></font><span style='font-size:12.0pt;font-family:"Times New Roman"'><br>\r
</span></p>\r
<p class=MsoPlainText><font size="3"><span style="font-family: Arial">\r
-This WinOF 2.2 is a full release as it contains:</span></font></p>\r
+This OFED 2.3 is a full release as it contains:</span></font></p>\r
\r
</div>\r
<ul>\r
<li>\r
<p class="MsoPlainText"><font face="Arial" size="3">Windows 7, Windows Server \r
- 2008 R2 and HPC SP2 are now supported.</font></p></li>\r
+ 2008 R2 and HPC Edition are now supported.</font></p></li>\r
<li>\r
<p class="MsoPlainText"><font face="Arial" size="3">NDIS 6 IPoIB for Server \r
- 2008, Serverr 2008 R2, Windows 7 and Vista.</font></p></li>\r
+ 2008, Server 2008 R2, Windows 7 and Vista.</font></p></li>\r
<li>\r
<p class="MsoPlainText"><font face="Arial" size="3">NDIS 5.1 IPoIB for \r
Server 2003 & XP.</font></p></li>\r
<li>\r
<p class="MsoPlainText"><font face="Arial" size="3">NetworkDirect \r
- is supported for Server 2008/HPC and Server 2008 R2/HPC (SP2).</font></p></li>\r
+ is supported for Server 2008/HPC and Server 2008 R2/HPC Edition.</font></p></li>\r
<li>\r
<p class="MsoPlainText"><font face="Arial" size="3">Mellanox ConnectX(mlx4) drivers \r
enhanced for increased performance and stability.</font></p></li>\r
diagnostics.</font></p></li>\r
<li>\r
<p class="MsoPlainText"><font face="Arial" size="3">OFED verbs library \r
- enables easy porting of Linux OFED applications into the WinOF environment.</font></p>\r
+ enables easy porting of Linux OFED applications into the OFED for Windows environment.</font></p>\r
</li>\r
<li>\r
<p class="MsoPlainText"><font face="Arial" size="3">uDAT/DAPL is now a \r
</ul>\r
<div class=Section1>\r
\r
-<p><font face="Arial">The Windows OpenFabrics (WinOF) release package contains the following:<br>\r
+<p><font face="Arial">The OpenFabrics Enterprise Distribtuion for Windows (OFED-W) release package contains the following:<br>\r
<br>\r
OpenFabrics InfiniBand core drivers and Upper Level Protocols (ULPs):</font></p>\r
<ul>\r
<p style='margin-left:.5in;text-indent:-.25in'><font face="Arial"><span dir=LTR>Performance \r
tests</span></font></p></li>\r
<li>\r
- <p style='margin-left:.5in;text-indent:-.25in'><font face="Arial"><span dir="LTR">\r
- OFED Diagnostics</span></font></p>\r
+ <p style='margin-left:.5in;text-indent:-.25in'><font face="Arial">\r
+ <span dir="LTR">\r
+ Diagnostic tools</span></font></p>\r
</li>\r
</ul>\r
\r
</li>\r
<li>\r
<p style='margin-left:.5in;text-indent:-.25in'><font face="Arial"><span dir="LTR">Windows \r
- Server 2008 R2 + HPC SP2</span></font></p>\r
+ Server 2008 R2 HPC Edition</span></font></p>\r
</li>\r
<li>\r
<p style='margin-left:.5in;text-indent:-.25in'><font face="Arial">Windows 7</font></p>\r
<br>\r
Current HCA firmware version can be viewed from the 'vstat' command or the \r
Mellanox firmware tool flint.</font></p>\r
+<h4><font face="Arial"><a name="How_to_find_the_PSID_of_a_Mellanox_HCA">How to \r
+find the PSID of a Mellanox HCA</a></font></h4>\r
+<blockquote>\r
+ <p><font face="Arial">Should the OFED stack not install; possibly due to outdated \r
+ firmware:<br>\r
+ <br>\r
+ Download and install the Mellanox Firmware burning tools from\r
+ <a href="http://www.mellanox.com/content/pages.php?pg=management_tools&menu_section=34">\r
+ Mellanox Support</a></font></p>\r
+ <p><font face="Arial">After you determine the PSID,<br>\r
+ <br>\r
+ Download Mx Firmware image .zip file from\r
+ <a href="http://www.mellanox.com/content/pages.php?pg=firmware_download">\r
+ Mellanox Firmware download</a></font></p>\r
+ <p><font face="Arial">How to find the PSID of the Mellanox card if the OFED stack did not install, \r
+ otherwise use vstat.<br>\r
+ <br>\r
+ mst status<br>\r
+ Found 2 devices:<br>\r
+ mt26418_pciconf0<br>\r
+ mt26418_pci_cr0<br>\r
+ <br>\r
+ flint -d mt26418_pci_cr0 query<br>\r
+ In the output, you will find the PSID.</font></p>\r
+</blockquote>\r
\r
<h4><font face="Arial"><u>Supported Switches</u></font></h4>\r
\r
<a name="Installation_Specifics"><u>Notes</u></a></h2>\r
\r
<p><font face="Arial">User mode tools and diagnostics are installed in '%SystemDrive%\Program \r
-Files\WinOF'. Although device driver modules initially reside in \r
-'%SystemDrive%\Program Files\WinOF\Drivers', when installed the Windows device \r
+Files\OFED'. Although device driver modules initially reside in \r
+'%SystemDrive%\Program Files\OFED\Drivers', when installed the Windows device \r
installer copies driver files to %SystemRoot%\system32 & %SystemRoot%\SysWOW64'. \r
DAT & DAPL runtime libraries are installed into %SystemRoot% in order to be \r
accessible by user mode applications.<br>\r
-WinOF user mode executables are designed to be run from\r
-a Command Prompt window; see 'Start->Program Files-> Windows OpenFabrics-> Command Prompt'. </font></p>\r
-<p><font face="Arial">'%SystemDrive%\Program Files\WinOF' is appended to the system wide search \r
+OFED user mode executables are designed to be run from a Command Prompt window; \r
+see 'Start->Program Files->OpenFabrics Enterprise Distribution-> OFED-> Command Prompt'. </font></p>\r
+<p><font face="Arial">'%SystemDrive%\Program Files\OFED' is appended to the system wide search \r
path environment variable 'PATH'; any command windows created after the installation will have the updated \r
-%PATH% environment variable, hence will be able to access WinOF executables.</font></p>\r
+%PATH% environment variable, hence will be able to access OFED executables.</font></p>\r
\r
<p><font face="Arial">The \91default\92 installation installs \91released/free\92 (not\r
checked/debug) versions of drivers and executables. Debug/Checked versions are \r
\r
<p><font face="Arial">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 OFED opensm work well.</font></p>\r
+configured and useful; either Windows or Linux versions of openSM work well.</font></p>\r
<p><font face="Arial">It is recommended that OpenSM be run as a Windows service. A typical \r
-WinOF install will install OpenSM as a Windows service which \r
+OFED 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
+See the OFED Manual for details on opensm as a service.<br>\r
By selecting the 'OpenSM_Service_Started' install feature, a local OpenSM subnet \r
management service will be automatically started. </font> </p>\r
\r
<p><font face="Arial">Note, the opensm.exe process must continue to run in order\r
-to maintain Infiniband fabric configuration. Should the opensm.exe process die,\r
+to maintain an 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.</font></p>\r
\r
<p><font face="Arial">For more subnet management information, consult the Windows\r
-OpenFabrics manual.</font></p>\r
+OpenFabrics Enterprise Distribution manual.</font></p>\r
\r
<p class=MsoNormal><a href="#WinOF_Release_Notes"><font color="#000000">\r
<Return-to-Top></font></a></p>\r
<li><font face="Arial">Double-click the .msi installer file, <b>Except for \r
Vista. </b></font></li>\r
<li><font face="Arial">For Vista installs, from an privileged administrator command window, execute 'msiexec /I \r
- WinOF_2-2_wlh_xxx.msi'.</font></li>\r
+ OFED_2-2_wlh_xxx.msi'.</font></li>\r
</ul>\r
<h3>Requirements</h3>\r
\r
the "Found New Hardware Wizard".</font></p>\r
\r
<p><font face="Arial">If you have previously installed openib-windows, WinOF (Windows OpenFabrics)\r
-packages or vendor supplied Infiniband packages, uninstall and reboot prior to\r
-installing this version of Windows OpenFabrics (WinOF).</font></p>\r
+packages or vendor supplied Infiniband packages, uninstall and reboot prior to \r
+installing this version of OpenFabrics Enterprise Distribution for Windows.</font></p>\r
\r
-<p><font face="Arial">For an existing Windows OpenFabrics (WinOF) uninstall<br>\r
- Start-> Programs-> Windows OpenFabrics-> Uninstall WinOF<br>\r
+<p><font face="Arial">For an existing Windows OpenFabrics Enterprise \r
+Distribution (OFED) uninstall<br>\r
+ Start-> Programs-> OpenFabrics Enterprise Distribution-> Uninstall OFED<br>\r
-or-<br>\r
- Control Panel -> Add or Remove Programs-> Windows\r
-OpenFabrics->Remove.</font></p>\r
+ Control Panel -> Add or Remove Programs->OpenFabrics \r
+Enterprise Distribution->Remove.</font></p>\r
<p><font face="Arial">openib-windows (IB stack before WinOF 1.0 release) uninstall: (not the normal \r
uninstall case)</font></p>\r
\r
\r
<p><font face="Arial">Vista installation <b>only</b>; open a privileged Administrator command \r
window and type</font></p>\r
-<p><font face="Arial"> start/wait msiexec /I WinOF_2-1_wlh_xxx.msi</font></p>\r
+<p><font face="Arial"> start/wait msiexec /I OFED_2-1_wlh_xxx.msi</font></p>\r
<p><font face="Arial">For all other Windows variants, double-clicking the installer file (.msi) \r
-works correctly to start a WinOF installation.<br>\r
-From a login session with administrator privileges, File Explorer view, double-click the WinOF_M-m{-p}_OSE_arch.msi file to begin the Windows OpenFabrics \r
+works correctly to start an OFED installation.<br>\r
+From a login session with administrator privileges, File Explorer view, double-click the OFED_M-m{-p}_OSE_arch.msi file to begin the Windows OpenFabrics \r
+Enterprise Distribution \r
installation.</font></p>\r
<p><font face="Arial">Where 'M-n{-p}' indicates Major release number, Minor release number, and \r
optional point-release number.</font></p>\r
<p><font face="Arial"> OSE - Operating System Environment:</font></p>\r
<ul>\r
+ <li><font face="Arial">win7 - Windows 7 or Windows Server 2008 R2 HPC \r
+ Edition</font></li>\r
<li><font face="Arial">wlh - (Windows LongHorn) Windows Server 2008, HPC or Vista</font></li>\r
<li><font face="Arial">wnet - Windows Server 2003 or Windows XP 64-bit version</font></li>\r
<li><font face="Arial">wxp - Windows XP x86/32-bit version</font></li>\r
driver installation.<br>\r
These non-WHQL'ed driver install questions can <b>not</b> be disabled \r
via 'My Computer->Properties->Hardware->Driver Signing->Ignore'.</font></p>\r
-<p><font face="Arial">Bottom-line - The digitally signed WinOF drivers in this package are not WHQL'ed \r
+<p><font face="Arial">Bottom-line - The digitally signed OFED drivers in this package are not WHQL'ed \r
per se, although they are \r
built from driver source which has been or is in process of being WHQL'ed by \r
-hardware vendors who participate in the open source WinOF development process.</font></p>\r
+hardware vendors who participate in the open source OFED for Windows development process.</font></p>\r
<p> </p>\r
<p> <font size="4">**** WARNING ****</font></p>\r
<blockquote>\r
<p><font face="Arial">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
+ OFED 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 WHQL'ed \r
+ in order for the OFED 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 OFED drivers are not WHQL'ed \r
and hence are not trusted by Windows; MS claims this is a 'feature'.</font></p>\r
<p><font face="Arial">An artifact of cancelling an errant 'Found New Hardware' popup window may \r
induce an errant taskbar Information notifier/bubble indicating there may \r
\r
<ul type=disc>\r
<li class=MsoNormal><font face="Arial">InfiniBand Core:</font><ul>\r
- <li><font face="Arial">HCA driver - Mellanox: InfiniHost or ConnectX<br>\r
+ <li><font face="Arial">Mellanox HCA driver: InfiniHost or ConnectX<br>\r
Windows PNP will select the correct HCA driver.</font></li>\r
<li><font face="Arial">IB core stack and libraries - includes winverbs, \r
winmad and OFED verbs library.</font></li>\r
Network Direct (MS supported only for Server 2008 HPC).<br> VNIC - Virtual Ethernet device over Infiniband<br> SRP - SCSI over RDMA Protocol<br> \r
DAT/DAPL \r
- RDMA device independent, user-mode Direct Access Transport & Direct Access \r
- Provider<br> - DAT v1.1 runtime libraries.<br> - DAT v1.1 application build environment \r
- (header files & link files).<br> - DAT/DAPL v2.0 runtime libraries<br> - DAT v2.0 application build environment<br> OpenSM_service_started - InfiniBand Subnet Management \r
+ Provider<br> - DAT/DAPL v2.0 runtime libraries<br> - DAT v2.0 application build environment<br> OpenSM_service_started - InfiniBand Subnet Management \r
enabled and started as a Windows Service.<br> \r
By default OpenSM is installed as a disabled Windows Service.<br>\r
Checked versions of driver files.<br>\r
</font></li>\r
<li><font face="Arial">The '<b>default</b>' installation includes IB core, IPoIB, WSD (Win2K3 only), \r
- DAT 1.1 runtime libraries, OpenSM service (disabled).</font></li>\r
+ DAT 2.0 runtime libraries, OpenSM service (disabled).</font></li>\r
</ul>\r
\r
</blockquote>\r
<p> </p>\r
<BLOCKQUOTE></BLOCKQUOTE>\r
<h2><u><a name="HCA Driver Installation">HCA Driver Installation</a></u></h2>\r
-<p><font face="Arial">WinOF driver installation uses the Device Installation \r
+<p><font face="Arial">OFED driver installation uses the Device Installation \r
Frameworks for Applications (DIFxApp) and the Windows Driver Store.<br>\r
The Microsoft Plug-n-Play (PNP) subsystem \r
controls which Infiniband HCA (Host Channel Adapter) device driver is loaded \r
from the Windows Driver Store. HCA driver selection is based on PNP device \r
ID probing, thus InfiniHost, ConnectX or both drivers can be loaded \r
by the PNP subsystem.<br>\r
-Using DIFxApp and PNP device probing results in the WinOF installation not \r
+Using DIFxApp and PNP device probing results in the OFED installation not \r
requiring a specific HCA model [ConnectX or InfiniHost] feature selection; HCA \r
vendor is the feature selection criteria.</font></p>\r
<p><font face="Arial"><br>\r
<div id="main-copy0">\r
\r
<div id="main-copy1">\r
- <font face="Arial">An unattended
WinOF install will install the following 'default' options</font><ul>
\r+ <font face="Arial">An unattended
OFED install will install the following 'default' options</font><ul>
\r <li><font face="Arial">Infiniband Core modules - Mellanox HCA driver \r
(see HCA driver selection note), IB core stack, libraries, utilities and \r
documentation.</font></li>\r
<li><font face="Arial">WSD - (Win2K8/3 only, not installed on XP) Win Sock Direct</font></li>\r
<li><font face="Arial">ND - NetworkDirect [started automatically (via ndinstall.exe) only for Server \r
2008/HPC and Vista].</font></li>\r
- <li><font face="Arial">DAT & DAPL (v1.1 & v2.0) runtime libraries + dapltest.exe \r
+ <li><font face="Arial">DAT & DAPL (v2.0) runtime libraries + dapltest2.exe \r
(dt-svr & dt-cli).</font></li>\r
</ul>\r
</div>\r
<p><font face="Arial"><b>HCA selection for all Windows variants </b>\r
- (Server 2008, HPC & Vista)</font></p>\r
+ (Windows 7, Server 2008, HPC & Vista)</font></p>\r
<blockquote>\r
<p><font face="Arial">Default HCA driver selection is driven by the \r
Windows PNP subsystem; no user selection required or supported.</font></p>\r
2003/XP, invoke the following command \r
from a command window.</font></p>\r
<blockquote>\r
- <p><font face="Arial">start/wait msiexec.exe /i WinOF_2-1_wnet_x64.msi /qn /quiet /log \r
- %TEMP%\WOF-install.log</font></p>\r
+ <p><font face="Arial">start/wait msiexec.exe /i OFED_2-1_wnet_x64.msi /qn /quiet /log \r
+ %TEMP%\OFED-install.log</font></p>\r
<p><font face="Arial">'/log dev:path\logFilename.log' is optional.</font></p>\r
<p><font face="Arial">msiexec.exe /? for all options.</font></p>\r
</blockquote>\r
name change (wnet --> wxp).</font></p>\r
<ul>\r
<li><font face="Arial">ConnectX HCA<br>\r
- start/wait msiexec.exe /i WinOF_2-1_wxp_x86.msi /qb /quiet HCA=cx<br>\r
+ start/wait msiexec.exe /i OFED_2-1_wxp_x86.msi /qb /quiet HCA=cx<br>\r
</font></li>\r
</ul>\r
<p><font face="Arial"><b>Server 2008 / Vista </b>- any Mellanox HCA Hardware</font></p>\r
<ul>\r
<li><font face="Arial">No need to specify HCA type as PNP (Plug-n-Play) \r
figures out the correct HCA to install.<br>\r
- start/wait msiexec.exe /i WinOF_2-1_wlh_x64.msi /qb /quiet<br>\r
+ start/wait msiexec.exe /i OFED_2-1_wlh_x64.msi /qb /quiet<br>\r
</font></li>\r
- <li><font face="Arial">If you desire an unattended WinOF install with a \r
+ <li><font face="Arial">If you desire an unattended OFED install with a \r
progress bar, from a console window<br>\r
- start/wait msiexec.exe /i WinOF_2-1_wlh_x64.msi /passive</font></li>\r
+ start/wait msiexec.exe /i OFED_2-1_wlh_x64.msi /passive</font></li>\r
</ul>\r
<p> </p>\r
<p><font face="Arial">Non-HCA Install Features added to above msiexec command \r
<p><font face="Arial">Default install + OpenSM Started on the local \r
system</font></p>\r
<ul>\r
- <li><font face="Arial">Server 2003, Mellanox HCA - start/wait msiexec.exe /i WinOF_2-1_wnet_x64.msi \r
+ <li><font face="Arial">Server 2003, Mellanox HCA - start/wait msiexec.exe /i OFED_2-1_wnet_x64.msi \r
/passive OSMS=1<br>\r
</font></li>\r
</ul>\r
<p> </p>\r
<BLOCKQUOTE></BLOCKQUOTE>\r
<h2><u><a name="Server_2008_HPC_Install_Notes">Server 2008 HPC Install Notes</a></u></h2>\r
-<p><font face="Arial">Device drivers in WinOF 2.0 and later releases are Digitally \r
+<p><font face="Arial">Device drivers in OFED 2.0 and later releases are Digitally \r
signed by the 3rd party Software Publisher 'OpenFabrics Alliance', although they are not WHQL'ed (Windows Quality Hardware Labs) certified. \r
-The WinOF source code is used by hardware vendors to achieve WHQL \r
+The OFED source code is used by hardware vendors to achieve WHQL \r
certification.</font></p>\r
-<p><font face="Arial">The lack of WHQL driver certification places WinOF drivers \r
+<p><font face="Arial">The lack of WHQL driver certification places OFED drivers \r
in the 'unknown 3rd party SW publishers' category. <br>\r
When installing 'Unknown 3rd party SW publishers' drivers, Windows prompts on \r
the install console for instructions as what to do (Install, Trust or not)?<br>\r
This prompting results in a failed remote node install when performing a \r
-<font color="#FF0000">first-time</font> unattended WinOF install.<br>\r
+<font color="#FF0000">first-time</font> unattended OFED install.<br>\r
By preloading the remote node's Trusted 3rd party Software Publisher Certificate \r
-Store, the unattended install will proceed without prompting, thus allowing the WinOF install to complete \r
+Store, the unattended install will proceed without prompting, thus allowing the \r
+OFED install to complete \r
successfully.</font></p>\r
<p><font face="Arial">Be aware: if a node is reimaged (same or different template applied) the \r
established trust of the OpenFabric Alliance is destroyed, thus the OFA certificate \r
needs to be reinstalled.</font></p>\r
-<p><font face="Arial">How to install WinOF drivers and components in the HPC \r
+<p><font face="Arial">How to install OFED drivers and components in the HPC \r
Server 2008 environment.</font></p>\r
<ul>\r
<li><font face="Arial">Add the OpenFabrics Alliance Trusted SW Publisher certificate to the head-node's Trusted Publisher Certificate store by</font><ul>\r
- <li><font face="Arial">Installing WinOF on the head node - start Open Subnet \r
+ <li><font face="Arial">Installing OFED on the head node - start Open Subnet \r
Manager if needed, otherwise depend on another OpenSM on the IB fabric.</font></li>\r
- <li><font face="Arial">Our recommendation is to install WinOF on the \r
- head-node; Set head-node IPoIB interface IPv4 address after WinOF install.</font></li>\r
+ <li><font face="Arial">Our recommendation is to install OFED on the \r
+ head-node; Set head-node IPoIB interface IPv4 address after OFED install.</font></li>\r
<li><font face="Arial">Or - Installing the OFA certificate from the \r
installer .msi file by</font><ul>\r
<li><font face="Arial">right-clicking the .msi file, select Properties</font></li>\r
network accessible), then run the digital certificate install script 'cert-add.bat' \r
to 'add' the 'Open Fabrics Alliance' as a Trusted 3rd party Software Publisher \r
to the remote node 's certificate stores.</font><ul>\r
- <li><font face="Arial">CD your administrator command window to the WinOF \r
+ <li><font face="Arial">CD your administrator command window to the OFED \r
folder which contains the 'cert-add.bat' script file. </font></li>\r
- <li><font face="Arial">If WinOF was installed on the head-node, then 'cd /d \r
- %ProgramFiles%\WinOF </font></li>\r
- <li><font face="Arial">Otherwise unpack, not install, the WinOF files to \r
+ <li><font face="Arial">If OFED was installed on the head-node, then 'cd /d \r
+ %ProgramFiles%\OFED </font></li>\r
+ <li><font face="Arial">Otherwise unpack, not install, the OFED files to \r
gain access to cert-add.bat file by executing the following commands:</font><ul>\r
<li><font face="Arial">Folder %TARGETDIR% folder must not exist, msiexec \r
/A will create it.</font></li>\r
- <li><font face="Arial">msiexec /A WinOF_2-1_wlh.msi TARGETDIR=%TEMP%\WOF \r
- # WOF folder does not exist.</font></li>\r
- <li><font face="Arial">cd /d %TEMP%\WOF\PFiles\WinOF</font></li>\r
+ <li><font face="Arial">msiexec /A OFED_2-1_wlh.msi TARGETDIR=%TEMP%\OFED \r
+ # OFED folder does not exist.</font></li>\r
+ <li><font face="Arial">cd /d %TEMP%\OFED\PFiles\OFED</font></li>\r
</ul></li>\r
</ul>\r
<ul>\r
<li><font face="Arial">Cert add command format: cert-add \r
share-folder list-of-remote-nodes</font></li>\r
<li><font face="Arial">For the examples, assume <a href="file://HN/WOF">\r
- \\HN\WOF</a> is the compute node visible share name;<br>\r
- head-node local name is \Program Files\Microsoft HPC Pack\Data\InstallShare\WOF<br>\r
- Head-node uses remote share name \\HN\WOF.</font></li>\r
+ \\HN\OFED</a> is the compute node visible share name;<br>\r
+ head-node local name is \Program Files\Microsoft HPC Pack\Data\InstallShare\OFED<br>\r
+ Head-node uses remote share name \\HN\OFED.</font></li>\r
<li><font face="Arial">First extract OFA TP certificate to remote \r
node visible share, creates\r
- <a href="file://orion-hn/winof">\\HN\WOF\OFA_TP.cer</a> &\r
- <a href="file://orion-hn/winof">\\HN\WOF\rem-cert-ADD.bat</a><br>\r
+ <a href="file://orion-hn/winof">\\HN\OFED\OFA_TP.cer</a> &\r
+ <a href="file://orion-hn/winof">\\HN\OFED\rem-cert-ADD.bat</a><br>\r
cert-add\r
- <a href="file://orion-hn/winof">\\HN\WOF</a> </font></li>\r
+ <a href="file://orion-hn/winof">\\HN\OFED</a> </font></li>\r
<li><font face="Arial">example: add OFA Trusted Publisher \r
certificate to remote node's local certificate store<br> cert-add\r
- <a href="file://orion-hn/winof">\\HN\WOF</a> cn01 cn02 cn03 cn04 \r
+ <a href="file://orion-hn/winof">\\HN\OFED</a> cn01 cn02 cn03 cn04 \r
cn05</font></li>\r
<li></li>\r
<li><font face="Arial">For all compute nodes: clusrun /nodes:X msiexec /I\r
- <a href="file://orion-hn/winof">\\HN\WOF\</a>WinOF_xxx_yyy.msi \r
+ <a href="file://orion-hn/winof">\\HN\OFED\</a>OFED_xxx_yyy.msi \r
/quiet /qn /Lv msi.log <br> </font></li>\r
</ul></li>\r
<li><font face="Arial"><b>Node Template Provisioning:</b> if remote nodes are <b>not \r
operational </b>(not yet provisioned) then do the following:</font><ul>\r
- <li><font face="Arial">See %ProgramFiles%\WinOF\HPC\* for provisioning \r
+ <li><font face="Arial">See %ProgramFiles%\OFED\HPC\* for provisioning \r
example scripts; customization is required.<br>\r
</font></li>\r
<li><font face="Arial">From the head node, extract the OFA certificate to a \r
file in the remote node visible share file OFA_TP.cer;<br> (example \r
- Remote node visible share: \Program Files\Microsoft HPC Pack\Data\InstallShare\WOF \r
- == \\HN\WOF)<br>\r
- Start -->All Programs -->Windows OpenFabric --> WinOF Command \r
+ Remote node visible share: \Program Files\Microsoft HPC Pack\Data\InstallShare\OFED \r
+ == \\HN\OFED)<br>\r
+ Start -->All Programs -->Windows OpenFabric --> OFED Command \r
Window<br>\r
cd HPC<br>\r
- cert-add <a href="file://orion-hn/winof">\\HN\WOF</a> \r
- # <a href="file://orion-hn/winof">\\HN\WOF</a> is the remote node visible \r
- share; create <a href="file://orion-hn/winof">\\HN\WOF</a>\OFA_TP.cer<br> </font></li>\r
+ cert-add <a href="file://orion-hn/winof">\\HN\OFED</a> \r
+ # <a href="file://orion-hn/winof">\\HN\OFED</a> is the remote node visible \r
+ share; create <a href="file://orion-hn/winof">\\HN\OFED</a>\OFA_TP.cer<br> </font></li>\r
<li><font face="Arial">copy the following files to (example: \Program \r
- Files\Microsoft HPC Pack\Data\InstallShare\
WOF)</font><ul>
\r- <li><font face="Arial">WinOF installer .msi file</font></li>\r
- <li><font face="Arial">%ProgramFiles%\WinOF\HPC\OFA-cert-install.bat</font></li>\r
- <li><font face="Arial">%ProgramFiles%\WinOF\HPC\WinOF-install.bat<br>\r
+ Files\Microsoft HPC Pack\Data\InstallShare\
OFED)</font><ul>
\r+ <li><font face="Arial">OFED installer .msi file</font></li>\r
+ <li><font face="Arial">%ProgramFiles%\OFED\HPC\OFA-cert-install.bat</font></li>\r
+ <li><font face="Arial">%ProgramFiles%\OFED\HPC\OFED-install.bat<br>\r
</font></li>\r
</ul></li>\r
- <li><font face="Arial">Verify you have the required WinOF provisioning files \r
+ <li><font face="Arial">Verify you have the required OFED provisioning files \r
in the remote node visible share:</font><ul>\r
- <li><font face="Arial">WinOF installer .msi file, referenced in \r
- WinOF-install.bat</font></li>\r
+ <li><font face="Arial">OFED installer .msi file, referenced in \r
+ OFED-install.bat</font></li>\r
<li><font face="Arial">OFA-cert-install.bat</font></li>\r
- <li><font face="Arial">WinOF-install.bat</font></li>\r
+ <li><font face="Arial">OFED-install.bat</font></li>\r
<li><font face="Arial">rem-cert-ADD.bat</font></li>\r
<li><font face="Arial">OFA_TP.cer<br>\r
</font></li>\r
template; include the following steps as part of the node provisioning \r
template steps after the HPC pack has been installed:</font><ul>\r
<li><font face="Arial"> copy entire contents of (example: \Program \r
- Files\Microsoft HPC Pack\Data\InstallShare\WOF) to remote node as <br>\r
- %INSTALLDRIVE%\WOF</font></li>\r
- <li><font face="Arial">execute the DOS command: %INSTALLDRIVE%\WOF\OFA-cert-install.bat</font></li>\r
- <li><font face="Arial">execute the DOS command: %INSTALLDRIVE%\WOF\WinOF-install.bat<br>\r
+ Files\Microsoft HPC Pack\Data\InstallShare\OFED) to remote node as <br>\r
+ %INSTALLDRIVE%\OFED</font></li>\r
+ <li><font face="Arial">execute the DOS command: %INSTALLDRIVE%\OFED\OFA-cert-install.bat</font></li>\r
+ <li><font face="Arial">execute the DOS command: %INSTALLDRIVE%\OFED\OFED-install.bat<br>\r
</font></li>\r
</ul></li>\r
<li><font face="Arial">Use 'cluster manager' to provision all compute nodes \r
<li><font face="Arial">IPoIB supports DHCP IP address assignment for those \r
who choose to use it. Static IP address binding allows a direct mapping from \r
IP address to physical node number.<br>\r
- </font></li>\r
+ <br>\r
+ If you are running OpenSM somewhere other than the head node, then disregard \r
+ the following.<br>\r
+ When running OpenSM on the head-node and using DHCP to assign IPoIB \r
+ interface IPv4 addresses to compute nodes, the best-known-install method is:</font></li>\r
+</ul>\r
+\r
+</div>\r
+<blockquote>\r
+ <ul>\r
+ <li><font face="Arial">install winOFED on the head-node 1st; select \r
+ 'start OpenSM' as an install feature to run OpenSM on the Head-node.</font></li>\r
+ <li><font face="Arial">Add 'OpenSM' as a startup dependency for \r
+ the DHCP server; see regedit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp\DependOnService</font></li>\r
+ <li><font face="Arial">After registry modifications a head-node reboot \r
+ is required.</font></li>\r
+ </ul>\r
+</blockquote>\r
+<div class=Section1>\r
+\r
+<ul>\r
<li><font face="Arial">IPoIB static IPv4 address assignment points of \r
Interest<br>\r
- When installing WinOF one must consider how the Interface name 'Local Area \r
+ When installing OFED one must consider how the Interface name 'Local Area \r
Connection {x}' is assigned to the IPoIB ports in order to correctly target \r
IP address assignment. <br>\r
Assume the target compute node has two Ethernet port and your HCA has two IB \r
- ports. After the 1st WinOF installation, or node reprovisioing \r
+ ports. After the 1st OFED installation, or node reprovisioing \r
you will see the following assignments:</font><ul>\r
<li><font face="Arial">Ethernet port 0 is 'Local Area Connection'</font></li>\r
<li><font face="Arial">Ethernet port 1 is 'Local Area Connection 2'</font></li>\r
<li><font face="Arial">IB port 1 is 'Local Area Connection 3'</font></li>\r
<li><font face="Arial">IB port 2 is 'Local Area Connection 4'</font></li>\r
</ul>\r
- <p><font face="Arial">A few minutes after the WinOF install completes, the \r
- HPC manager will rename the active IPoIB 'Local Area Connection 3' network \r
+ <p><font face="Arial">A few minutes after the OFED install completes, the HPC manager will rename the active IPoIB 'Local Area Connection 3' network \r
interface to the 'Application' network interface along with the active \r
Ethernet interface being renamed to the 'Private' network; 'Local Area \r
Connection' is no longer in use.<br>\r
- If WinOF is uninstalled and then reinstalled without node reprovisioning, \r
+ If OFED is uninstalled and then reinstalled without node reprovisioning, \r
the active IPoIB network interface is installed as 'Local Area Connection'. \r
Within a few minutes, the active IPoIB network interface will again be \r
renamed the 'Application' network interface.<br>\r
Summary:<br>\r
- 1st WinOF install, an IB cable is attached to HCA port 1, \r
+ 1st OFED install, an IB cable is attached to HCA port 1, \r
IPoIB is named 'Local Area Connection 3'.<br>\r
- 2nd WinOF install, IPoIB is named 'Local Area Connection' as \r
+ 2nd OFED install, IPoIB is named 'Local Area Connection' as \r
the Ethernet interface is renamed the 'Private' network.<br>\r
</font></li>\r
- <li><font face="Arial">At this juncture, the WinOF drivers are installed.<br>\r
+ <li><font face="Arial">At this juncture, the OFED drivers are installed.<br>\r
</font></li>\r
</ul>\r
<h3><u>Windows Deployment Manager usage for HPC compute node provisioning</u></h3>\r
<a href="http://technet.microsoft.com/en-us/library/dd391826.aspx">Microsoft HPC \r
installs</a> for details.</font></p>\r
<p><font face="Arial">In support of the new Microsoft WDM HPC cluster \r
-provisioning process, WinOF now supports an administrative install mode which is \r
-a method to extract WinOF files to the local filesystem without actually installing them; \r
-thus making WinOF files accessible to WDM provisioning.</font></p>\r
+provisioning process, OFED now supports an administrative install mode which is \r
+a method to extract OFED files to the local filesystem without actually installing them; \r
+thus making OFED files accessible to WDM provisioning.</font></p>\r
<p><font face="Arial">Disclaimer - WDM 'driver' provisioning ONLY works for \r
-WHQL'ed drivers; WinOF drivers are not WHQL'ed. For WinOF installs, see \r
+WHQL'ed drivers; OFED drivers are not WHQL'ed. For OFED installs, see \r
previous node template provisioning discussion.</font></p>\r
-<p><font face="Arial">msiexec /A WinOF_2-1_wlh_x64.msi TARGETDIR=dev:\path-to-extracted-files \r
+<p><font face="Arial">msiexec /A OFED_2-1_wlh_x64.msi TARGETDIR=dev:\path-to-extracted-files \r
# last folder in path-to-extracted-files must NOT exist.</font></p>\r
-<p><font face="Arial">example: msiexec /A WinOF_2-1_wlh_x64.msi TARGETDIR=%TEMP%\WOF \r
-(note: TARGETDIR is case sensitive, WOF must not exist)</font></p>\r
+<p><font face="Arial">example: msiexec /A OFED_2-1_wlh_x64.msi TARGETDIR=%TEMP%\OFED \r
+(note: TARGETDIR is case sensitive, OFED must not exist)</font></p>\r
<p><font face="Arial">The above command creates the folder structure:\r
-<a href="file:///C:/windows/Temp/WOF/PFiles/WinOF/">%TEMP%\WOF\PFiles\WinOF\</a></font></p>\r
-<h3><u>WinOF device driver-less installs:</u></h3>\r
-<p><font face="Arial">Normally WinOF device driver files are installed by processing the driver '.inf' \r
-files. To install the WinOF package by selecting install features without \r
+<a href="file:///C:/windows/Temp/WOF/PFiles/WinOF/">%TEMP%\OFED\PFiles\OFED\</a></font></p>\r
+<h3><u>OFED device driver-less installs:</u></h3>\r
+<p><font face="Arial">Normally OFED device driver files are installed by processing the driver '.inf' \r
+files. To install the OFED package by selecting install features without \r
installing any device drivers [HCA, IPoIB, ND, WSD, SRP or VNIC] (assumed \r
reliance on WDM to install device drivers) can be accomplished with the following \r
interactive install command:</font></p>\r
-<p><font face="Arial">start/wait msiexec /I WinOF_2-1_wlh_x64.msi NODRV=1</font></p>\r
+<p><font face="Arial">start/wait msiexec /I OFED_2-1_wlh_x64.msi NODRV=1</font></p>\r
<p><font face="Arial">To skip driver installation for an unattended install</font></p>\r
-<p><font face="Arial"> start/wait msiexec /I WinOF_2-1_wlh_x64.msi /qn /quiet NODRV=1</font></p>\r
-<p><font face="Arial"><b>Note</b>: when uninstalling WinOF from an installation \r
+<p><font face="Arial"> start/wait msiexec /I OFED_2-1_wlh_x64.msi /qn /quiet NODRV=1</font></p>\r
+<p><font face="Arial"><b>Note</b>: when uninstalling OFED from an installation \r
which was done with NODRV=1, you <b>MUST </b>include NODRV=1 on the uninstall \r
-command line; otherwise WinOF drivers will be uninstalled also.</font></p>\r
-<p><font face="Arial"> start/wait msiexec /X WinOF_2-1_wlh_x64.msi /qn /quiet NODRV=1</font></p>\r
+command line; otherwise OFED drivers will be uninstalled also.</font></p>\r
+<p><font face="Arial"> start/wait msiexec /X OFED_2-1_wlh_x64.msi /qn /quiet NODRV=1</font></p>\r
<p><font face="Arial">See <a href="http://unattended.sourceforge.net/installers.php">Unattended \r
Installations</a> for further references.</font></p>\r
<p><a href="#WinOF_Release_Notes"><font color="#000000"><Return-to-Top></font></a></p>\r
will be assigned to 'Local Area Connection 3' and 'Local Area Connection 4'. \r
If you system has a single Ethernet port, then IPoIB interface is 'Local Area \r
Connection 2'.</font></p>\r
-<p><font face="Arial">For Server 2008/HPC systems, the WinOF installation follows the above \r
+<p><font face="Arial">For Server 2008/HPC systems, the OFED installation follows the above \r
discussion. In defining HPC network interfaces, the IPoIB network will \r
eventually be \r
identified as the 'Application' network '. A few minutes after a \r
<BLOCKQUOTE></BLOCKQUOTE>\r
<h2><u><a name="Uninstall">Uninstall</a></u></h2>\r
\r
-<p><font face="Arial">To uninstall a WinOF package from a single node</font></p>\r
+<p><font face="Arial">To uninstall a OFED package from a single node</font></p>\r
<ol>\r
- <li><font face="Arial">Start--> All Programs-> Windows OpenFabrics-> Uninstall WinOF</font></li>\r
+ <li><font face="Arial">Start--> All Programs-> Windows OpenFabrics-> \r
+ Uninstall OFED</font></li>\r
<li><font face="Arial">Control Panel-> Add Remove Programs-> Windows OpenFabrics-> Remove</font></li>\r
</ol>\r
<h3><span style="font-weight: 400; text-decoration: underline">Unattended \r
/quiet \r
/forcerestart<br>\r
- or -<br>\r
- start/wait msiexec.exe /x WinOF_wlh_2-1_x64.msi /quiet /forcerestart \r
- # WinOF_xxxx.msi is the file used to install WinOF.</font></p>\r
+ start/wait msiexec.exe /x OFED_wlh_2-1_x64.msi /quiet /forcerestart \r
+ # OFED_xxxx.msi is the file used to install OFED.</font></p>\r
<p><font face="Arial">msiexec.exe /help for details.</font></p>\r
<p><font face="Arial">'/log dev:path\logfilename.log' if you wish to later view the install \r
results.</font></p>\r
<p><font face="Arial">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</font></p>\r
+ be located via<br>Programs-> Windows OpenFabrics-> Uninstall OFED<right-click>Properties</font></p>\r
</blockquote>\r
<p><font face="Arial">Infrequently, the 'System Device->Infiniband Fabric' may not correctly uninstall. Make sure the Infiniband Fabric device is \r
completely uninstalled; use device manager for checking. The effect of a \r
partially uninstalled Infiniband Fabric device is IPoIB load failure \r
- upon the next WinOF install.</font></p>\r
+ upon the next OFED install.</font></p>\r
<h3><span style="text-decoration: underline">Uninstall Notes</span></h3>\r
<ol>\r
<li><font face="Arial">If the SRP (SCSI RDMA Protocol) driver has been previously installed, \r
<p><a href="#WinOF_Release_Notes"><font color="#000000"><Return-to-Top></font></a></p>\r
<p> </p>\r
<h2><u><font face="Arial"><a name="Verifying_the_WinOF_install">Verifying the \r
-WinOF install</a></font></u></h2>\r
+OFED install</a></font></u></h2>\r
<ul>\r
<li><font face="Arial">From a command windows type 'devmgmt.msc'. Look for \r
InfiniBand HCA device(s) along with Network IPoIB devices .<br>\r
If the Subnet Manager was installed as 'started' on this system, find the \r
InfiniBand Subnet Manager entry; entry should be automatic & started.</font></li>\r
</ul>\r
-<p><font face="Arial">A Vista WinOF installation can fail due to protection failures when \r
+<p><font face="Arial">A Vista OFED installation can fail due to protection failures when \r
installing the HCA driver. Vista HCA driver installation failure can be caused \r
by double-clicking the .msi installer \r
file to start the installation.<br>\r
-WinOF installs for (Vista only) require the installation be started from a \r
+OFED installs for (Vista only) require the installation be started from a \r
privileged Administrator command window.<br>Start a privileged Administrator command window (Start->Command \r
Prompt->Right-click->Run as Administrator) and execute:<br>\r
msiexec /I \r
-WinOF_xxx_yyy.msi</font></p>\r
-<p><font face="Arial">To create a LOG file of your WinOF installation, execute this command: \r
-msiexec /I WinOF_xxx_yyy.msi /Lv %TEMP%\WOF-install.log<br>\r
-View %TEMP%\WOF-install.log</font></p>\r
+OFED_xxx_yyy.msi</font></p>\r
+<p><font face="Arial">To create a LOG file of your OFED installation, execute this command: msiexec /I \r
+OFED_xxx_yyy.msi /Lv %TEMP%\OFED-install.log<br>\r
+View %TEMP%\OFED-install.log</font></p>\r
<p><font face="Arial">msiexec /? for details.</font></p>\r
<p><font face="Arial">Server 2008 or Vista can also fail to install due to driver install files \r
left over from previously failed install attempts; see %windir%\system32\DriverStore\{Temp|FileRepository}. \r
device from 'InfiniBand Host Channel Adapters', and make sure you uninstall the system device\r
'InfiniBand Fabric' if it is present.<br>\r
<br>\r
- <u><b>REBOOT</b></u> and retry the
WinOF installation again.</font><p>
\r+ <u><b>REBOOT</b></u> and retry the
OFED installation again.</font><p>
\r <font face="Arial">See \r
ibscan.bat and ibcleanup.bat @\r
- <a href="http://www.openfabrics.org/downloads/WinOF/etc/">\r
- http://www.openfabrics.org/downloads/WinOF/etc/</a>.<br>\r
- ibscan will display WinOF files on your system.<br>\r
- ibcleanup will attempt to remove all WinOF files from your syste. \r
- WARNING - ibcleanup is not valid as a
WinOF uninstall tool!</font><p><a href="#WinOF_Release_Notes"><font color="#000000"><Return-to-Top></font></a><p> </div>
\r+ <a href="http://www.openfabrics.org/downloads/windows/etc/">\r
+ http://www.openfabrics.org/downloads/windows/etc/</a>.<br>\r
+ ibscan will display OFED files on your system.<br>\r
+ ibcleanup will attempt to remove all OFED files from your syste. \r
+ WARNING - ibcleanup is not valid as a
OFED uninstall tool!</font><p><a href="#WinOF_Release_Notes"><font color="#000000"><Return-to-Top></font></a><p> </div>
\r </div>\r
<h3><u><a name="Correct_Installation_Validation">Correct Installation Validation</a></u></h3>\r
<p><font face="Arial">From the Device Manager you should find the following devices:</font></p>\r
<li><font face="Arial">From a command window type 'devmgmt.msc' </font></li>\r
<li><font face="Arial">InfiniBand Host Channel Adapters -> InfiniHost or Mellanox ConnectX</font></li>\r
<li><font face="Arial">The System Devices -> InfiniBand Fabric device is no longer present in \r
- WinOF 2.0 and following releases.</font></li>\r
+ OFED 2.0 and following releases.</font></li>\r
<li><font face="Arial">Network Adapters -> OpenIB IPoIB Adapter (an Instance per HCA port).</font></li>\r
</ul>\r
<blockquote>\r
<h4><font face="Arial">Validation Test</font></h4>\r
- <p><font face="Arial">Open a WinOF command window</font></p>\r
+ <p><font face="Arial">Open a OFED command window</font></p>\r
<ol>\r
<li><font face="Arial">Start->Program Files->Windows OpenFabrics -> Command \r
Window</font></li>\r
<p><font face="Arial">Limit the number of Subnet Managers on your fabric; one SM per fabric is \r
sufficient, although redundant Subnet Managers are supported.</font></p>\r
<ol>\r
- <li><font face="Arial">After a 'typical' WinOF install, OpenSM is installed as a <b>disabled</b> \r
+ <li><font face="Arial">After a 'typical' OFED install, OpenSM is installed as a <b>disabled</b> \r
Windows service named "InfiniBand Subnet Management".<br>\r
To start the OpenSM service, from a command window type 'services.msc' to \r
start the Services manager. From the Services manager, find and select \r
<Return-to-Top></font></a></font></p>\r
<p> </p>\r
<BLOCKQUOTE></BLOCKQUOTE>\r
-<h2><u><a name="Which_WinOF_release_is_installed">Which
WinOF release is installed</a></u><a name="Which_WinOF_release_is_installed">?</a></h2>
\r+<h2><u><a name="Which_WinOF_release_is_installed">Which
OFED release is installed</a></u><a name="Which_WinOF_release_is_installed">?</a></h2>
\r <ol>\r
<li><font face="Arial">Control Pannel -->Add/Remove Programs or \r
- -->Programs/Features entry identifies the installed WinOF release version.</font></li>\r
+ -->Programs/Features entry identifies the installed OFED release version.</font></li>\r
<li><font face="Arial">Start->Programs->Windows OpenFabrics (check \r
Uninstall entry).</font></li>\r
<li><font face="Arial">Driver confirmation from the Device Manager:<br> Query My Computer-> Manage-> Device Manager-> Network \r
Adapters-> OpenFabrics 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 notes.</font></li>\r
- <li><font face="Arial">Hold the mouse point over \Program Files\WinOF\ib_read_bw.exe to display \r
-the file version; [WinOF-Major.Minor.not-used.svn revision number].</font></li>\r
+ <li><font face="Arial">Hold the mouse point over \Program Files\OFED\ib_read_bw.exe to display \r
+the file version; [OFED-Major.Minor.not-used.svn revision number].</font></li>\r
</ol>\r
<ul>\r
<li><font face="Arial">WinOF 1.0 is based on openib-windows <b><u>svn revision 614</u></b> @\r
</b></font></li>\r
<li><font face="Arial">WinOF 2.1 is based on<b> (<u>svn.2476 branches\WOF2-1</u>)<br>\r
</b></font></li>\r
- <li><font face="Arial">WinOF 2.2 is based on<b> (<u>svn.2667 branches\WOF2-2</u>)</b></font></li>\r
+ <li><font face="Arial">WinOF 2.2 is based on<b> (<u>svn.2667 branches\WOF2-2</u>)<br>\r
+ </b></font></li>\r
+ <li><font face="Arial">OFED 2.3 is based on<b> (<u>svn.2909 branches\WOF2-3</u>)</b></font></li>\r
</ul>\r
<p><a href="#WinOF_Release_Notes"><font color="#000000"><Return-to-Top></font></a></p>\r
<p> </p>\r
<p align="left"><font face="Arial">In order for DAT/DAPL programs to execute correctly, the 'dat.dll' \r
file must be present in the current directory,\r
%SystemRoot% or in the library search path.</font></p>\r
-<p align="left"><font face="Arial">WinOF installation places the dat2.dll and dapl2.dll \r
+<p align="left"><font face="Arial">OFED installation places the dat2.dll and dapl2.dll \r
files in the '%SystemRoot%' \r
folder (a.k.a. \Windows).</font></p>\r
<p align="left"><font face="Arial">The DAT/DAPL configuration file by convention is defined as \r
a template configuration file will be installed as '%SystemDrive%\DAT\dat.conf'.<br>\r
In order to preserve existing installations, the dat.conf file is not \r
automatically installed if '%SystemDrive%\DAT\dat.conf' exists.<br>\r
-A sample dat.conf file is always installed as '\Program Files\WinOF\dat.conf \r
+A sample dat.conf file is always installed as '\Program Files\OFED\dat.conf \r
'.</font></p>\r
<p align="left"><font face="Arial">The default DAT configuration file specification can be overridden by use \r
of the environment variable DAT_OVERRIDE. Such that 'DAT_OVERRIDE=D:\MyDAT\test.conf' \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").</font></p>\r
+double-quotes (e.g., "C:\\Programs Files\\OFED\\dapl.dll").</font></p>\r
<h4 align="left"><span style="font-weight: 400"><font face="Arial">uDAT/uDAPL version 2.0 runtime \r
libraries are identified as dat2.dll and dapl2.dll, both in %SystemRoot%; see \r
manual for further details.<br>\r
<p align="left"> </p>\r
<BLOCKQUOTE></BLOCKQUOTE>\r
<h2 align="left"><u><a name="SRP_-_SCSI_RDMA_Protocol_Driver_Installation">SRP (SCSI RDMA Protocol) Driver Installation</a></u></h2>\r
-<p align="left"><font face="Arial">The WinOF installer does not install the SRP driver as part of a default \r
+<p align="left"><font face="Arial">The OFED installer does not install the SRP driver as part of a default \r
installation. \r
If the SRP feature is selected in the custom installation window, an InfiniBand \r
SRP Miniport driver will be installed; see the device manager view under SCSI \r
and RAID controllers.</font></p>\r
<p align="left"><font face="Arial">The system device 'InfiniBand I/O Unit' (IOU) \r
-device is required for correct SRP operation. The WinOF installer will \r
+device is required for correct SRP operation. The OFED installer will \r
install/load the IOU driver if the SRP feature is selected. See the device \r
manager view System Devices --> InfiniBand I/O Unit for conformation of correct \r
IOU driver loading.</font></p>\r
then will load the IBiou.sys driver along with the ib_srp.sys driver.</font></p>\r
<p align="left"><font face="Arial">An invocation of 'diskmgmt.msc' will display \r
available SRP target disks.</font></p>\r
-<p align="left"><font face="Arial">Consult the WinOF manual for further SRP \r
+<p align="left"><font face="Arial">Consult the OFED manual for further SRP \r
topics including configuring a Linux OFED SRP target.</font></p>\r
<h3 align="left"><u>SRP Driver Uninstall</u></h3>\r
<p align="left"><font face="Arial">If the SRP (SCSI RDMA Protocol) driver has been previously \r
Letter.</font></li>\r
</ul>\r
<p><font face="Arial">The consequences of not releasing the SRP target drive(s) are that after the \r
-WinOF uninstall reboot there are lingering InfiniBand driver files. These driver \r
+OFED uninstall reboot there are lingering InfiniBand driver files. These driver \r
files remain because while the SRP target is active they have references, thus \r
-when the WinOF uninstall attempts to delete the files the operation fails.</font></p>\r
+when the OFED uninstall attempts to delete the files the operation fails.</font></p>\r
<p align="left">\r
<br>\r
<a href="#WinOF_Release_Notes"><font color="#000000"><Return-to-Top></font></a></p>\r
userspace libraries install as part of the Winverbs driver installation package.<br>\r
Additionally, a Windows port of the OFED libibverbs library, several test\r
programs and OFED InfiniBand diagnostic utilities are also included.</font></p>\r
-<p><font face="Arial">As of WinOF 2.1, Winverbs components are now integral \r
-components of a default WinOF installation.<br>\r
+<p><font face="Arial">As of OFED 2.1, Winverbs components are now integral \r
+components of a default OFED installation.<br>\r
Although WinVerbs, WinMAD drivers, OFED libraries and utilities are install \r
selectable features, they are automatically included as part of the default \r
-WinOF install.</font></p>\r
+OFED install.</font></p>\r
\r
</div>\r
\r
<Return-to-Top></font></a><br>\r
</p>\r
<BLOCKQUOTE></BLOCKQUOTE>\r
-<h2><u><a name="Known_Issues">Known Issues</a></u><font face="Arial" size="3"><br> </font></h2>\r
-\r
+<h2><u><a name="Known_Issues">Known Issues</a></u></h2>\r
<ul>\r
+ <li>\r
+ <p class=MsoPlainText><font face="Arial" size="3">Should the OFED stack not \r
+ install with a notifier "Possible HCA driver install failure", the likely \r
+ cause is outdated HCA firmware.<br>\r
+ See <a href="#How_to_find_the_PSID_of_a_Mellanox_HCA">finding the PSID</a> \r
+ text for firmware burning instructions.<br>\r
+ </font></p></li>\r
<li>\r
<p class=MsoPlainText><font face="Arial" size="3">HCA drivers are now \r
classified as 'BOOT START' drivers; the implication being for a first time \r
- install, the system will reboot after installation.<br>\r
- </font></p></li>\r
+ install, the system will reboot after installation.<br> </font></p>\r
+ </li>\r
<li>\r
<p class=MsoPlainText><font face="Arial" size="3">IPoIB partition \r
multicast \r
adapter" igmpprototype=igmprtrv2</span></font></font></p>\r
<p class="MsoNormal"> </p></font></font>\r
<font face="Tahoma" size="2">\r
- <p class="MsoNormal"><font face="Arial">F</font></font><font size="3" face="Arial">uture WinOF releases</font><font size="2" face="Arial"> \r
+ <p class="MsoNormal"><font face="Arial">F</font></font><font size="3" face="Arial">uture \r
+ OFED releases</font><font size="2" face="Arial"> \r
will support IGMP V3.</font></div></span></div>\r
<p class=MsoPlainText> </p></li>\r
<li>\r
projects / ~shefty / rdma-win.git / commitdiff