[ofw] RE: WinOF 2.0 installation question

[Smith, Stan]

Hello,
  Please see below.


________________________________
From: wwg-bounces at lists.openfabrics.org [mailto:wwg-bounces at lists.openfabrics.org] On Behalf Of Casano, Warenne
Sent: Monday, July 20, 2009 9:59 AM
To: wwg at lists.openfabrics.org
Subject: [Wwg] WinOF 2.0 installation question


Hi,

I am migrating an MPI application from Linux to Windows (Intel Xeon platform with
Windows 2008 server).  At first, I installed Mellanox WinOF 2.0 and tried to use it
with Intel MPI Library.  The Intel MPI library requires DAT runtime library which was
not part of the Mellanox WinOF 2.0 installation.  So, I uninstalled Mellanox WinOF 2.0.
I downloaded WinOF 2.0 and tried to install.  However, the installation failed.
>From the release notes, installation may fail if the certain files
are in DriverStore\Temp directory.  I could not removed those files even when I'm
logged in as "administrator".

I need to know how to remove those files from DriverStore\Temp directory.  I
tried using ibcleanup; but that did not remove the files in DriverStore\Temp.

<Stan> Latest version of ibcleanup.bat @  http://www.openfabrics.org/downloads/WinOF/etc/ know how to remove these files.
Are you sure the Mellanox WinOF 2.0 installation is removed? Check device manager (devmgr.msc)
 (You did reboot after Mellanox uninstall?)
Take a look at how ibcleanup.bat removes DriverStore folders if per-chance if does not work for you; perform task manually from privileged cmd window.

I am new in this area; so I would like to know how I could verify whether dapltest
works or not.  What I need is a sample output of when dapltest works after
WinOF is installed properly.

>From a head-node WinOF cmd window (Start->All Programs-->Windows OpenFabrics->Command Window
start a dapl2test server; type 'dt-svr<Enter>'
The dapl2test svr is listening on the IPv4 address you assigned to your IPoIB instance.
You will need that IPoIB IPv4 address in the next step; ipconfig will reveal if you're not sure.

>From another WinOF cmd window, type 'dt-cli IPoIB-IPv4-address conn' for a simple node local connection test; 'dt-cli' with no args gives help message.
Example: If 10.104.200 is assigned to your 1st IPoIB instance @ 'Local Area Connection 3' or in HPC speak 'Application Network'

    dt-svr<Enter>      # dapl2test server is listening on 10.10.4.200

    dt-cli 10.10.4.200 conn<Enter>
    dt-cli 10.10.4.200 transmet        # a more complicated test
    dt-cli 10.10.4.200 stop            # causes dap2test server to stop; otherwise it is persistent.

Now that you have proven Dapl2test is functional on the head-node, make sure the dapl2test server is still running on the head-node.
using clurun run dapltest clients from compute nodes; from the head-node command window type 'clusrun /nodes:n1,n2,n3 dt-cli 10.10.4.200 conn' for the 1st step.
Expand at your leisure.

Let me know how things go.

Stan.

PS: I you can wait until Tuesday 7/21 afternoon (PDT) WinOF 2.1 RC2 will be available - a much cleaner device install/uninstall! Strongly recommended.
PSS: wwg at lists.openfabrics.org<mailto:wwg at lists.openfabrics.org> is a small forum, I changed the reply to much larger audience of developers.

Thank you for your help.
Warenne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20090720/2b94fb35/attachment.html>