\r
<h1 align=center style='text-align:center'>Windows OpenFabrics </h1>\r
\r
-<h1 align=center style='text-align:center'>1.0 Release Notes [RC2]</h1>\r
+<h1 align=center style='text-align:center'>1.0 Release Notes [RC3]</h1>\r
\r
<h3 align=center style='text-align:center'>\r
-<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->05/17/2007<!--webbot bot="Timestamp" endspan i-checksum="12620" --></h3>\r
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->05/24/2007<!--webbot bot="Timestamp" endspan i-checksum="12580" --></h3>\r
\r
<div class=MsoNormal align=center style='text-align:center'>\r
\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</p>\r
-<blockquote>\r
- <p>'Start->Program Files-> Windows OpenFabrics-> Command Prompt'.</p>\r
-</blockquote>\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
<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. By selecting \r
-the OpenSM feature of a 'Custom' install, an OpenSM service is created and \r
-started. OpenSM is installed and not started as the typical install. \r
-See the WinOF Manual for details on opensm as a service.</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 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
<p>openib-windows uninstall:</p>\r
\r
<ol start=1 type=1>\r
- <li class=MsoNormal>Disable any Local Area Connections which are bound to the\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
</ol>\r
</blockquote>\r
<h3><u>OpenIB Subnet Management as a Windows Service</u></h3>\r
-<p>InfiniBand subnet management is installed by default, although it is NOT \r
-enabled by default. There are two ways to enable OpenSM on a node:</p>\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>Manual - In a command window run 'opensm.exe'. The opensm.exe \r
- process must remain in order for the fabric to remain configured.</li>\r
- <li>OpenSM running as a Windows service:<br>\r
- a) Request a 'Custom' install, selecting the OpenSM feature.<br>\r
- b) Manually create and start the OpenSM service: (space prior to '=' is \r
- required)<br>\r
- 1) sc create opensm binPath= "<a href="file:///C:/Program%20Files/WinOF/opensm.exe%20--service">C:\Program \r
- Files\WinOF\opensm.exe --service</a>" start= auto DisplayName= "IB Subnet \r
- Manager"<br>\r
- 2) sc start opensm<br>\r
- 3) sc qc opensm \r
- rem Query service description, 'sc stop opensm' Stops the opensm \r
- service</li>\r
+ <li>After a 'typical' WinOF install, OpenSM is installed as a <b>disabled</b> \r
+ Windows service called "InfiniBand Subnet Management". To start the OpenSM \r
+ service on the system 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 feature. Once \r
+ the install is complete, 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
<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
-%SystemRoot%\ or in the library search path.</p>\r
-<p align="left">The default WinOF installation places the file dat.dll in '%SystemRoot%' \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 default is defined as \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 %SystemRoot%\dapl.dll'.</p>\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
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>\r
- </font></p></li>\r
- <li>\r
- <p class=MsoPlainText><font face="Times New Roman" size="3">The \r
- InstallShield-12 'Current Settings' window is empty; Resolution is underway.<br>\r
- </font></p></li>\r
+ device drivers coupled with the IB fabric coinstaller.<br> </font></p></li>\r
</ul>\r
<p class=MsoPlainText><br>\r
</p>\r