<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/27/2007<!--webbot bot="Timestamp" endspan i-checksum="12630" --></h3>\r
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->08/01/2007<!--webbot bot="Timestamp" endspan i-checksum="12522" --></h3>\r
\r
<div class=MsoNormal align=center style='text-align:center'>\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
+are packaged into a <a href="http://www.dalun.com/wix/default.htm">WIX 2.0 \r
+(Windows Installer Xml)</a> 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
packages or vendor supplied Infiniband packages, uninstall and reboot prior to\r
installing this version of Windows OpenFabrics.</p>\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
<p>openib-windows uninstall:</p>\r
\r
<ol start=1 type=1>\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
+<p> </p>\r
\r
<p><b>REBOOT</b></p>\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
+WinOF_M-m_arch_setup.msi 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>\r
</blockquote>\r
\r
-<h4>Install types:</h4>\r
-\r
-<h4>Minimal</h4>\r
+<h4>Install type: Custom only</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 & Diagnostics</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 (Win2K3 only), 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 (Win2K3 only)<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
+ <li class=MsoNormal>InfiniBand Core:<ul type=disc>\r
+ <li>HCA driver, IB core stack and libraries.</li>\r
+ <li>Release Notes, Manual</li>\r
+ <li>Subnet Management [opensm], Performance & Diagnostic tools</li>\r
+ </ul></li>\r
+ <li>Optional:<br> IPoIB<br> \r
+ Winsock Direct (Win2K3 only)<br> VNIC - Virtual Ethernet device over Infiniband<br> SRP - SCSI over RDMA Protocol<br> DAPL \r
+ - RDMA device independent, user-mode Direct Access Transport & Direct Access \r
+ Provider Libraries.<br> OpenSM_service_started - InfiniBand Subnet Management \r
+ enabled and started as a Windows Service.<br>\r
+ \r
+ By default OpenSM is installed as a disabled 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
+<h3><u>Unattended Install</u></h3>\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>To perform a silent/unattended installation, invoke the following command \r
+ from a command window.</p>\r
+ <blockquote>\r
+ <p>start/wait msiexec.exe /i WinOF_R1-1_x64.msi /quiet /passive /log \r
+ %TEMP%\WOF_install.log</p>\r
+ <p>'/log dev:path\logFilename.log' is optional.</p>\r
+ <p>msiexec.exe /? for all options.</p>\r
+ </blockquote>\r
+ <p>An unattended install will install the following default install options:</p>\r
+ <ul>\r
+ <li>Infiniband Core - HCA driver, IB core stack and libraries, \r
+ Documentation</li>\r
+ <li>IPoIB - Internet Protocols over InfiniBand</li>\r
+ <li>WSD - (Win2k3 only, not installed on XP) Win Sock Direct</li>\r
+ <li>DAPL - uDAT & DAPL</li>\r
+ </ul>\r
+</div>\r
+<p>Should WSD not be a desirable unattended install option (Win2K3 only), \r
+currently you would install unattended then execute the command 'installsp -r' \r
+on each node to remove WSD.</p>\r
<p>See <a href="http://unattended.sourceforge.net/installers.php">Unattended \r
Installations</a> for further references.</p>\r
<p> </p>\r
<p> </p>\r
<h2><u>Uninstall</u></h2>\r
\r
-<p>To uninstall a WinOF package</p>\r
+<p>To uninstall a WinOF package from a single node</p>\r
<ol>\r
<li>Programs-> Windows OpenFabrics-> Uninstall WinOF</li>\r
- <li>Control Panel-> Add Remove Programs-> Windows OpenFabrics</li>\r
+ <li>Control Panel-> Add Remove Programs-> Windows OpenFabrics-> Remove</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
+<h3><span style="font-weight: 400; text-decoration: underline">Unattended \r
+Uninstall</span></h3>\r
+<p>From a Command Window invoke the following command; a system reboot will \r
+occur after the uninstall.</p>\r
+<blockquote>\r
+ <p>start/wait msiexec.exe /x {51798BCA-98EE-43ED-95D6-CCA11E369044} /quiet /passive<br>\r
+ - or -<br>\r
+ start/wait msiexec.exe /x WinOF_R1-1_x64.msi /quiet /passive \r
+ # WinOF_xxxx.msi is the file used to install WinOF.</p>\r
+ <p>msiexec.exe /help for details.</p>\r
+ <p>'/log dev:path\logfilename.log' if you wish to later view the install \r
+ results.</p>\r
+ <p>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</p>\r
+</blockquote>\r
+<p>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.</p>\r
<p> </p>\r
\r
<h2><u>Trouble Shooting</u></h2>\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
+ service, use My computer->Manage->Services and Applications->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
+ running: My computer->Manage->Services and Applications->Services->InfiniBand Subnet \r
+ Manager.<br>\r
+ </li>\r
+ <li>Consult the OpenSM log file @ %SystemRoot%\temp\osm.log to see what \r
+ OpenSM thinks is happening.</li>\r
</ol>\r
<p> </p>\r
<h3><u>Local Network Adapter Ordering</u></h3>\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"> </p>\r
+<h4 align="left"> </h4>\r
+<h3 align="left"><u>SRP - SCSI RDMA Protocol Driver Installation</u></h3>\r
+<p align="left">The WinOF stack does not install the SRP driver by default. \r
+If SRP is\r
+selected in the custom installation window, it will only be copied during WinOF\r
+installation. To complete the SRP driver installation, an SRP target must be\r
+detected; a Subnet Manager must be running somewhere in the InfiniBand subnet.<br>\r
+<br>\r
+Upon the detection of an SRP target, the "New Hardware Found" Wizard pops up.<br>\r
+- Select Install Automatically and click Next. This installs the I/O unit \r
+device.<br>\r
+<br>\r
+Once completed, the "New Hardware Found" Wizard pops up again.<br>\r
+- Select Install Automatically and click Next. This installs the SRP driver.<br>\r
+ </p>\r
\r
<h2><u>Known Issues</u></h2>\r
\r
</font></p></li>\r
<li>\r
<p class=MsoPlainText><font face="Times New Roman" size="3">WinOF x64 \r
- Add/Remove Programs entry for support does not display all ARP information.<br> </font></p></li>\r
+ Add/Remove Programs entry for support does not display all ARP information.<br>\r
+ </font></p></li>\r
+ <li>\r
+ <p class=MsoPlainText><font face="Times New Roman" size="3">The Windows \r
+ OpenFabrics release includes a WSD provider library that has been \r
+ extensively tested with Microsoft Windows Server 2003.<br>\r
+ During testing, bugs where found in the WSD switch that could lead to hangs, \r
+ crashes, data corruption, and other unwanted behavior. Microsoft released a \r
+ hotfix to address these issues which should be installed if using WSD.<br>\r
+ The Microsoft Windows Server 2003 hotfix for WSD can be located\r
+ <a class="wiki" href="http://support.microsoft.com/?kbid=910481">here</a>.</font><br>\r
+ <font face="Times New Roman" size="3"><br> </font></p></li>\r
</ul>\r
<p class=MsoPlainText><br>\r
</p>\r
projects / ~shefty / rdma-win.git / commitdiff