-
The Windows OpenFabrics (WinOF) release package contains the following:
+The OpenFabrics Enterprise Distribtuion for Windows (OFED-W) release package contains the following:
OpenFabrics InfiniBand core drivers and Upper Level Protocols (ULPs):
@@ -243,8 +243,9 @@ style='background-position: 0% 0%; mso-highlight:yellow; background-image:none;
Performance
tests
-
-
- OFED Diagnostics
+
+
+ Diagnostic tools
@@ -288,7 +289,7 @@ style='background-position: 0% 0%; mso-highlight:yellow; background-image:none;
Windows
- Server 2008 R2 + HPC SP2
+ Server 2008 R2 HPC Edition
Windows 7
@@ -319,6 +320,31 @@ Mellanox Firmware (FW) versions and update tools
Current HCA firmware version can be viewed from the 'vstat' command or the
Mellanox firmware tool flint.
+
+
+ Should the OFED stack not install; possibly due to outdated
+ firmware:
+
+ Download and install the Mellanox Firmware burning tools from
+
+ Mellanox Support
+ After you determine the PSID,
+
+ Download Mx Firmware image .zip file from
+
+ Mellanox Firmware download
+ How to find the PSID of the Mellanox card if the OFED stack did not install,
+ otherwise use vstat.
+
+ mst status
+ Found 2 devices:
+ mt26418_pciconf0
+ mt26418_pci_cr0
+
+ flint -d mt26418_pci_cr0 query
+ In the output, you will find the PSID.
+
Supported Switches
@@ -350,16 +376,16 @@ Mellanox firmware tool flint.
Notes
User mode tools and diagnostics are installed in '%SystemDrive%\Program
-Files\WinOF'. Although device driver modules initially reside in
-'%SystemDrive%\Program Files\WinOF\Drivers', when installed the Windows device
+Files\OFED'. Although device driver modules initially reside in
+'%SystemDrive%\Program Files\OFED\Drivers', when installed the Windows device
installer copies driver files to %SystemRoot%\system32 & %SystemRoot%\SysWOW64'.
DAT & DAPL runtime libraries are installed into %SystemRoot% in order to be
accessible by user mode applications.
-WinOF user mode executables are designed to be run from
-a Command Prompt window; see 'Start->Program Files-> Windows OpenFabrics-> Command Prompt'.
-'%SystemDrive%\Program Files\WinOF' is appended to the system wide search
+OFED user mode executables are designed to be run from a Command Prompt window;
+see 'Start->Program Files->OpenFabrics Enterprise Distribution-> OFED-> Command Prompt'.
+'%SystemDrive%\Program Files\OFED' is appended to the system wide search
path environment variable 'PATH'; any command windows created after the installation will have the updated
-%PATH% environment variable, hence will be able to access WinOF executables.
+%PATH% environment variable, hence will be able to access OFED executables.
The default installation installs released/free (not
checked/debug) versions of drivers and executables. Debug/Checked versions are
@@ -367,22 +393,22 @@ available as an install feature.
A single instance of a subnet manager, opensm.exe, must be
running on a fabric connected node in order for the Infiniband fabric to be
-configured and useful; either Windows or Linux OFED opensm work well.
+configured and useful; either Windows or Linux versions of openSM work well.
It is recommended that OpenSM be run as a Windows service. A typical
-WinOF install will install OpenSM as a Windows service which
+OFED install will install OpenSM as a Windows service which
is disabled; after an installation, choose your openSM node and start the openSM
service.
-See the WinOF Manual for details on opensm as a service.
+See the OFED Manual for details on opensm as a service.
By selecting the 'OpenSM_Service_Started' install feature, a local OpenSM subnet
management service will be automatically started.
Note, the opensm.exe process must continue to run in order
-to maintain Infiniband fabric configuration. Should the opensm.exe process die,
+to maintain an Infiniband fabric configuration. Should the opensm.exe process die,
restart the service if not automatic or re-run opensm.exe in order to continue
correct fabric operation.
For more subnet management information, consult the Windows
-OpenFabrics manual.
+OpenFabrics Enterprise Distribution manual.
<Return-to-Top>
@@ -396,7 +422,7 @@ OpenFabrics manual.
Double-click the .msi installer file, Except for
Vista.
For Vista installs, from an privileged administrator command window, execute 'msiexec /I
- WinOF_2-2_wlh_xxx.msi'.
+ OFED_2-2_wlh_xxx.msi'.
Requirements
@@ -405,14 +431,15 @@ package. Upon reboot, cancel any attempts to install new device hardware from
the "Found New Hardware Wizard".
If you have previously installed openib-windows, WinOF (Windows OpenFabrics)
-packages or vendor supplied Infiniband packages, uninstall and reboot prior to
-installing this version of Windows OpenFabrics (WinOF).
+packages or vendor supplied Infiniband packages, uninstall and reboot prior to
+installing this version of OpenFabrics Enterprise Distribution for Windows.
-
For an existing Windows OpenFabrics (WinOF) uninstall
- Start-> Programs-> Windows OpenFabrics-> Uninstall WinOF
+For an existing Windows OpenFabrics Enterprise
+Distribution (OFED) uninstall
+ Start-> Programs-> OpenFabrics Enterprise Distribution-> Uninstall OFED
-or-
- Control Panel -> Add or Remove Programs-> Windows
-OpenFabrics->Remove.
+ Control Panel -> Add or Remove Programs->OpenFabrics
+Enterprise Distribution->Remove.
openib-windows (IB stack before WinOF 1.0 release) uninstall: (not the normal
uninstall case)
@@ -442,15 +469,18 @@ drivers for newly discovered PCI device (HCA).
Vista installation only; open a privileged Administrator command
window and type
-
start/wait msiexec /I WinOF_2-1_wlh_xxx.msi
+
start/wait msiexec /I OFED_2-1_wlh_xxx.msi
For all other Windows variants, double-clicking the installer file (.msi)
-works correctly to start a WinOF installation.
-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
+works correctly to start an OFED installation.
+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
+Enterprise Distribution
installation.
Where 'M-n{-p}' indicates Major release number, Minor release number, and
optional point-release number.
OSE - Operating System Environment:
+ - win7 - Windows 7 or Windows Server 2008 R2 HPC
+ Edition
- wlh - (Windows LongHorn) Windows Server 2008, HPC or Vista
- wnet - Windows Server 2003 or Windows XP 64-bit version
- wxp - Windows XP x86/32-bit version
@@ -470,20 +500,20 @@ Answer 'yes' or 'Continue' to any notifier windows which reference non-WHQL'ed
driver installation.
These non-WHQL'ed driver install questions can not be disabled
via 'My Computer->Properties->Hardware->Driver Signing->Ignore'.
-Bottom-line - The digitally signed WinOF drivers in this package are not WHQL'ed
+Bottom-line - The digitally signed OFED drivers in this package are not WHQL'ed
per se, although they are
built from driver source which has been or is in process of being WHQL'ed by
-hardware vendors who participate in the open source WinOF development process.
+hardware vendors who participate in the open source OFED for Windows development process.
**** WARNING ****
Should any 'Welcome to the Found New Hardware Wizard' windows popup after the
- WinOF install has started, just ignore (window will disappear in a few
+ OFED install has started, just ignore (window will disappear in a few
seconds) or 'Cancel' the errant popup window.
For Windows Server 2003 (SP1) you can safely ignore the errant FNHW popup
window; for Windows XP (SP2) the errant FNHW popups need to be 'cancelled'
- in order for the WinOF install to proceed. The report back from Microsoft on these 'Found New Hardware Wizard' windows
- popping up, is they are due to the fact the WinOF drivers are not WHQL'ed
+ in order for the OFED install to proceed. The report back from Microsoft on these 'Found New Hardware Wizard' windows
+ popping up, is they are due to the fact the OFED drivers are not WHQL'ed
and hence are not trusted by Windows; MS claims this is a 'feature'.
An artifact of cancelling an errant 'Found New Hardware' popup window may
induce an errant taskbar Information notifier/bubble indicating there may
@@ -506,7 +536,7 @@ hardware vendors who participate in the open source WinOF development process.
- InfiniBand Core:
- - HCA driver - Mellanox: InfiniHost or ConnectX
+ - Mellanox HCA driver: InfiniHost or ConnectX
Windows PNP will select the correct HCA driver.
- IB core stack and libraries - includes winverbs,
winmad and OFED verbs library.
@@ -520,14 +550,13 @@ hardware vendors who participate in the open source WinOF development process.
Network Direct (MS supported only for Server 2008 HPC).
VNIC - Virtual Ethernet device over Infiniband
SRP - SCSI over RDMA Protocol
DAT/DAPL
- RDMA device independent, user-mode Direct Access Transport & Direct Access
- Provider
- DAT v1.1 runtime libraries.
- DAT v1.1 application build environment
- (header files & link files).
- DAT/DAPL v2.0 runtime libraries
- DAT v2.0 application build environment
OpenSM_service_started - InfiniBand Subnet Management
+ Provider
- DAT/DAPL v2.0 runtime libraries
- DAT v2.0 application build environment
OpenSM_service_started - InfiniBand Subnet Management
enabled and started as a Windows Service.
By default OpenSM is installed as a disabled Windows Service.
Checked versions of driver files.
- The 'default' installation includes IB core, IPoIB, WSD (Win2K3 only),
- DAT 1.1 runtime libraries, OpenSM service (disabled).
+ DAT 2.0 runtime libraries, OpenSM service (disabled).
@@ -536,14 +565,14 @@ hardware vendors who participate in the open source WinOF development process.
-
WinOF driver installation uses the Device Installation
+OFED driver installation uses the Device Installation
Frameworks for Applications (DIFxApp) and the Windows Driver Store.
The Microsoft Plug-n-Play (PNP) subsystem
controls which Infiniband HCA (Host Channel Adapter) device driver is loaded
from the Windows Driver Store. HCA driver selection is based on PNP device
ID probing, thus InfiniHost, ConnectX or both drivers can be loaded
by the PNP subsystem.
-Using DIFxApp and PNP device probing results in the WinOF installation not
+Using DIFxApp and PNP device probing results in the OFED installation not
requiring a specific HCA model [ConnectX or InfiniHost] feature selection; HCA
vendor is the feature selection criteria.
@@ -554,7 +583,7 @@ vendor is the feature selection criteria.
-
An unattended WinOF install will install the following 'default' options
+ An unattended OFED install will install the following 'default' options
- Infiniband Core modules - Mellanox HCA driver
(see HCA driver selection note), IB core stack, libraries, utilities and
documentation.
@@ -562,12 +591,12 @@ vendor is the feature selection criteria.
- WSD - (Win2K8/3 only, not installed on XP) Win Sock Direct
- ND - NetworkDirect [started automatically (via ndinstall.exe) only for Server
2008/HPC and Vista].
- - DAT & DAPL (v1.1 & v2.0) runtime libraries + dapltest.exe
+
- DAT & DAPL (v2.0) runtime libraries + dapltest2.exe
(dt-svr & dt-cli).
HCA selection for all Windows variants
- (Server 2008, HPC & Vista)
+ (Windows 7, Server 2008, HPC & Vista)
Default HCA driver selection is driven by the
Windows PNP subsystem; no user selection required or supported.
@@ -580,8 +609,8 @@ on each node to remove WSD.
2003/XP, invoke the following command
from a command window.
- start/wait msiexec.exe /i WinOF_2-1_wnet_x64.msi /qn /quiet /log
- %TEMP%\WOF-install.log
+ start/wait msiexec.exe /i OFED_2-1_wnet_x64.msi /qn /quiet /log
+ %TEMP%\OFED-install.log
'/log dev:path\logFilename.log' is optional.
msiexec.exe /? for all options.
@@ -591,18 +620,18 @@ on each node to remove WSD.
name change (wnet --> wxp).
- ConnectX HCA
- start/wait msiexec.exe /i WinOF_2-1_wxp_x86.msi /qb /quiet HCA=cx
+ start/wait msiexec.exe /i OFED_2-1_wxp_x86.msi /qb /quiet HCA=cx
Server 2008 / Vista - any Mellanox HCA Hardware
- No need to specify HCA type as PNP (Plug-n-Play)
figures out the correct HCA to install.
- start/wait msiexec.exe /i WinOF_2-1_wlh_x64.msi /qb /quiet
+ start/wait msiexec.exe /i OFED_2-1_wlh_x64.msi /qb /quiet
- - If you desire an unattended WinOF install with a
+
- If you desire an unattended OFED install with a
progress bar, from a console window
- start/wait msiexec.exe /i WinOF_2-1_wlh_x64.msi /passive
+ start/wait msiexec.exe /i OFED_2-1_wlh_x64.msi /passive
Non-HCA Install Features added to above msiexec command
@@ -614,7 +643,7 @@ line examples:
Default install + OpenSM Started on the local
system
- - Server 2003, Mellanox HCA - start/wait msiexec.exe /i WinOF_2-1_wnet_x64.msi
+
- Server 2003, Mellanox HCA - start/wait msiexec.exe /i OFED_2-1_wnet_x64.msi
/passive OSMS=1
@@ -622,30 +651,31 @@ system
-Device drivers in WinOF 2.0 and later releases are Digitally
+Device drivers in OFED 2.0 and later releases are Digitally
signed by the 3rd party Software Publisher 'OpenFabrics Alliance', although they are not WHQL'ed (Windows Quality Hardware Labs) certified.
-The WinOF source code is used by hardware vendors to achieve WHQL
+The OFED source code is used by hardware vendors to achieve WHQL
certification.
-The lack of WHQL driver certification places WinOF drivers
+The lack of WHQL driver certification places OFED drivers
in the 'unknown 3rd party SW publishers' category.
When installing 'Unknown 3rd party SW publishers' drivers, Windows prompts on
the install console for instructions as what to do (Install, Trust or not)?
This prompting results in a failed remote node install when performing a
-first-time unattended WinOF install.
+first-time unattended OFED install.
By preloading the remote node's Trusted 3rd party Software Publisher Certificate
-Store, the unattended install will proceed without prompting, thus allowing the WinOF install to complete
+Store, the unattended install will proceed without prompting, thus allowing the
+OFED install to complete
successfully.
Be aware: if a node is reimaged (same or different template applied) the
established trust of the OpenFabric Alliance is destroyed, thus the OFA certificate
needs to be reinstalled.
-How to install WinOF drivers and components in the HPC
+How to install OFED drivers and components in the HPC
Server 2008 environment.
- Add the OpenFabrics Alliance Trusted SW Publisher certificate to the head-node's Trusted Publisher Certificate store by
- - Installing WinOF on the head node - start Open Subnet
+
- Installing OFED on the head node - start Open Subnet
Manager if needed, otherwise depend on another OpenSM on the IB fabric.
- - Our recommendation is to install WinOF on the
- head-node; Set head-node IPoIB interface IPv4 address after WinOF install.
+ - Our recommendation is to install OFED on the
+ head-node; Set head-node IPoIB interface IPv4 address after OFED install.
- Or - Installing the OFA certificate from the
installer .msi file by
- right-clicking the .msi file, select Properties
@@ -667,17 +697,17 @@ Server 2008 environment.
network accessible), then run the digital certificate install script 'cert-add.bat'
to 'add' the 'Open Fabrics Alliance' as a Trusted 3rd party Software Publisher
to the remote node 's certificate stores.
- - CD your administrator command window to the WinOF
+
- CD your administrator command window to the OFED
folder which contains the 'cert-add.bat' script file.
- - If WinOF was installed on the head-node, then 'cd /d
- %ProgramFiles%\WinOF
- - Otherwise unpack, not install, the WinOF files to
+
- If OFED was installed on the head-node, then 'cd /d
+ %ProgramFiles%\OFED
+ - Otherwise unpack, not install, the OFED files to
gain access to cert-add.bat file by executing the following commands:
- Folder %TARGETDIR% folder must not exist, msiexec
/A will create it.
- - msiexec /A WinOF_2-1_wlh.msi TARGETDIR=%TEMP%\WOF
- # WOF folder does not exist.
- - cd /d %TEMP%\WOF\PFiles\WinOF
+ - msiexec /A OFED_2-1_wlh.msi TARGETDIR=%TEMP%\OFED
+ # OFED folder does not exist.
+ - cd /d %TEMP%\OFED\PFiles\OFED
@@ -689,52 +719,52 @@ Server 2008 environment.
Cert add command format: cert-add
share-folder list-of-remote-nodes
For the examples, assume
- \\HN\WOF is the compute node visible share name;
- head-node local name is \Program Files\Microsoft HPC Pack\Data\InstallShare\WOF
- Head-node uses remote share name \\HN\WOF.
+ \\HN\OFED is the compute node visible share name;
+ head-node local name is \Program Files\Microsoft HPC Pack\Data\InstallShare\OFED
+ Head-node uses remote share name \\HN\OFED.
First extract OFA TP certificate to remote
node visible share, creates
- \\HN\WOF\OFA_TP.cer &
- \\HN\WOF\rem-cert-ADD.bat
+ \\HN\OFED\OFA_TP.cer &
+ \\HN\OFED\rem-cert-ADD.bat
cert-add
- \\HN\WOF
+ \\HN\OFED
example: add OFA Trusted Publisher
certificate to remote node's local certificate store
cert-add
- \\HN\WOF cn01 cn02 cn03 cn04
+ \\HN\OFED cn01 cn02 cn03 cn04
cn05
For all compute nodes: clusrun /nodes:X msiexec /I
- \\HN\WOF\WinOF_xxx_yyy.msi
+ \\HN\OFED\OFED_xxx_yyy.msi
/quiet /qn /Lv msi.log
Node Template Provisioning: if remote nodes are not
operational (not yet provisioned) then do the following:
- - See %ProgramFiles%\WinOF\HPC\* for provisioning
+
- See %ProgramFiles%\OFED\HPC\* for provisioning
example scripts; customization is required.
- From the head node, extract the OFA certificate to a
file in the remote node visible share file OFA_TP.cer;
(example
- Remote node visible share: \Program Files\Microsoft HPC Pack\Data\InstallShare\WOF
- == \\HN\WOF)
- Start -->All Programs -->Windows OpenFabric --> WinOF Command
+ Remote node visible share: \Program Files\Microsoft HPC Pack\Data\InstallShare\OFED
+ == \\HN\OFED)
+ Start -->All Programs -->Windows OpenFabric --> OFED Command
Window
cd HPC
- cert-add \\HN\WOF
- # \\HN\WOF is the remote node visible
- share; create \\HN\WOF\OFA_TP.cer
+ cert-add \\HN\OFED
+ # \\HN\OFED is the remote node visible
+ share; create \\HN\OFED\OFA_TP.cer
- copy the following files to (example: \Program
- Files\Microsoft HPC Pack\Data\InstallShare\WOF)
- - WinOF installer .msi file
- - %ProgramFiles%\WinOF\HPC\OFA-cert-install.bat
- - %ProgramFiles%\WinOF\HPC\WinOF-install.bat
+ Files\Microsoft HPC Pack\Data\InstallShare\OFED)
+ - OFED installer .msi file
+ - %ProgramFiles%\OFED\HPC\OFA-cert-install.bat
+ - %ProgramFiles%\OFED\HPC\OFED-install.bat
- - Verify you have the required WinOF provisioning files
+
- Verify you have the required OFED provisioning files
in the remote node visible share:
- - WinOF installer .msi file, referenced in
- WinOF-install.bat
+ - OFED installer .msi file, referenced in
+ OFED-install.bat
- OFA-cert-install.bat
- - WinOF-install.bat
+ - OFED-install.bat
- rem-cert-ADD.bat
- OFA_TP.cer
@@ -743,10 +773,10 @@ Server 2008 environment.
template; include the following steps as part of the node provisioning
template steps after the HPC pack has been installed:
- copy entire contents of (example: \Program
- Files\Microsoft HPC Pack\Data\InstallShare\WOF) to remote node as
- %INSTALLDRIVE%\WOF
- - execute the DOS command: %INSTALLDRIVE%\WOF\OFA-cert-install.bat
- - execute the DOS command: %INSTALLDRIVE%\WOF\WinOF-install.bat
+ Files\Microsoft HPC Pack\Data\InstallShare\OFED) to remote node as
+ %INSTALLDRIVE%\OFED
+ - execute the DOS command: %INSTALLDRIVE%\OFED\OFA-cert-install.bat
+ - execute the DOS command: %INSTALLDRIVE%\OFED\OFED-install.bat
- Use 'cluster manager' to provision all compute nodes
@@ -765,36 +795,55 @@ Server 2008 environment.
- IPoIB supports DHCP IP address assignment for those
who choose to use it. Static IP address binding allows a direct mapping from
IP address to physical node number.
-
+
+ If you are running OpenSM somewhere other than the head node, then disregard
+ the following.
+ When running OpenSM on the head-node and using DHCP to assign IPoIB
+ interface IPv4 addresses to compute nodes, the best-known-install method is:
+
+
+
+
+
+ - install winOFED on the head-node 1st; select
+ 'start OpenSM' as an install feature to run OpenSM on the Head-node.
+ - Add 'OpenSM' as a startup dependency for
+ the DHCP server; see regedit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp\DependOnService
+ - After registry modifications a head-node reboot
+ is required.
+
+
+
+
+
- IPoIB static IPv4 address assignment points of
Interest
- When installing WinOF one must consider how the Interface name 'Local Area
+ When installing OFED one must consider how the Interface name 'Local Area
Connection {x}' is assigned to the IPoIB ports in order to correctly target
IP address assignment.
Assume the target compute node has two Ethernet port and your HCA has two IB
- ports. After the 1st WinOF installation, or node reprovisioing
+ ports. After the 1st OFED installation, or node reprovisioing
you will see the following assignments:
- Ethernet port 0 is 'Local Area Connection'
- Ethernet port 1 is 'Local Area Connection 2'
- IB port 1 is 'Local Area Connection 3'
- IB port 2 is 'Local Area Connection 4'
- A few minutes after the WinOF install completes, the
- HPC manager will rename the active IPoIB 'Local Area Connection 3' network
+ A few minutes after the OFED install completes, the HPC manager will rename the active IPoIB 'Local Area Connection 3' network
interface to the 'Application' network interface along with the active
Ethernet interface being renamed to the 'Private' network; 'Local Area
Connection' is no longer in use.
- If WinOF is uninstalled and then reinstalled without node reprovisioning,
+ If OFED is uninstalled and then reinstalled without node reprovisioning,
the active IPoIB network interface is installed as 'Local Area Connection'.
Within a few minutes, the active IPoIB network interface will again be
renamed the 'Application' network interface.
Summary:
- 1st WinOF install, an IB cable is attached to HCA port 1,
+ 1st OFED install, an IB cable is attached to HCA port 1,
IPoIB is named 'Local Area Connection 3'.
- 2nd WinOF install, IPoIB is named 'Local Area Connection' as
+ 2nd OFED install, IPoIB is named 'Local Area Connection' as
the Ethernet interface is renamed the 'Private' network.
- - At this juncture, the WinOF drivers are installed.
+ - At this juncture, the OFED drivers are installed.
Windows Deployment Manager usage for HPC compute node provisioning
@@ -803,31 +852,31 @@ cluster compute nodes; see
Microsoft HPC
installs for details.
In support of the new Microsoft WDM HPC cluster
-provisioning process, WinOF now supports an administrative install mode which is
-a method to extract WinOF files to the local filesystem without actually installing them;
-thus making WinOF files accessible to WDM provisioning.
+provisioning process, OFED now supports an administrative install mode which is
+a method to extract OFED files to the local filesystem without actually installing them;
+thus making OFED files accessible to WDM provisioning.
Disclaimer - WDM 'driver' provisioning ONLY works for
-WHQL'ed drivers; WinOF drivers are not WHQL'ed. For WinOF installs, see
+WHQL'ed drivers; OFED drivers are not WHQL'ed. For OFED installs, see
previous node template provisioning discussion.
-
msiexec /A WinOF_2-1_wlh_x64.msi TARGETDIR=dev:\path-to-extracted-files
+msiexec /A OFED_2-1_wlh_x64.msi TARGETDIR=dev:\path-to-extracted-files
# last folder in path-to-extracted-files must NOT exist.
-example: msiexec /A WinOF_2-1_wlh_x64.msi TARGETDIR=%TEMP%\WOF
-(note: TARGETDIR is case sensitive, WOF must not exist)
+example: msiexec /A OFED_2-1_wlh_x64.msi TARGETDIR=%TEMP%\OFED
+(note: TARGETDIR is case sensitive, OFED must not exist)
The above command creates the folder structure:
-%TEMP%\WOF\PFiles\WinOF\
-WinOF device driver-less installs:
-Normally WinOF device driver files are installed by processing the driver '.inf'
-files. To install the WinOF package by selecting install features without
+%TEMP%\OFED\PFiles\OFED\
+OFED device driver-less installs:
+Normally OFED device driver files are installed by processing the driver '.inf'
+files. To install the OFED package by selecting install features without
installing any device drivers [HCA, IPoIB, ND, WSD, SRP or VNIC] (assumed
reliance on WDM to install device drivers) can be accomplished with the following
interactive install command:
-start/wait msiexec /I WinOF_2-1_wlh_x64.msi NODRV=1
+start/wait msiexec /I OFED_2-1_wlh_x64.msi NODRV=1
To skip driver installation for an unattended install
- start/wait msiexec /I WinOF_2-1_wlh_x64.msi /qn /quiet NODRV=1
-Note: when uninstalling WinOF from an installation
+ start/wait msiexec /I OFED_2-1_wlh_x64.msi /qn /quiet NODRV=1
+Note: when uninstalling OFED from an installation
which was done with NODRV=1, you MUST include NODRV=1 on the uninstall
-command line; otherwise WinOF drivers will be uninstalled also.
- start/wait msiexec /X WinOF_2-1_wlh_x64.msi /qn /quiet NODRV=1
+command line; otherwise OFED drivers will be uninstalled also.
+ start/wait msiexec /X OFED_2-1_wlh_x64.msi /qn /quiet NODRV=1
See Unattended
Installations for further references.
<Return-to-Top>
@@ -842,7 +891,7 @@ If your system has two Ethernet ports, then IPoIB interfaces (HCA port 1, 2...)
will be assigned to 'Local Area Connection 3' and 'Local Area Connection 4'.
If you system has a single Ethernet port, then IPoIB interface is 'Local Area
Connection 2'.
-
For Server 2008/HPC systems, the WinOF installation follows the above
+For Server 2008/HPC systems, the OFED installation follows the above
discussion. In defining HPC network interfaces, the IPoIB network will
eventually be
identified as the 'Application' network '. A few minutes after a
@@ -863,9 +912,10 @@ reference.
-To uninstall a WinOF package from a single node
+To uninstall a OFED package from a single node
- - Start--> All Programs-> Windows OpenFabrics-> Uninstall WinOF
+ - Start--> All Programs-> Windows OpenFabrics->
+ Uninstall OFED
- Control Panel-> Add Remove Programs-> Windows OpenFabrics-> Remove
Unattended
@@ -877,18 +927,18 @@ occur after the uninstall.
/quiet
/forcerestart
- or -
- start/wait msiexec.exe /x WinOF_wlh_2-1_x64.msi /quiet /forcerestart
- # WinOF_xxxx.msi is the file used to install WinOF.
+ start/wait msiexec.exe /x OFED_wlh_2-1_x64.msi /quiet /forcerestart
+ # OFED_xxxx.msi is the file used to install OFED.
msiexec.exe /help for details.
'/log dev:path\logfilename.log' if you wish to later view the install
results.
If for some reason the Product Code {GUID} changes, the latest code can
- be located via
Programs-> Windows OpenFabrics-> Uninstall WinOF<right-click>Properties
+ be located via
Programs-> Windows OpenFabrics-> Uninstall OFED<right-click>Properties
Infrequently, the 'System Device->Infiniband Fabric' may not correctly uninstall. Make sure the Infiniband Fabric device is
completely uninstalled; use device manager for checking. The effect of a
partially uninstalled Infiniband Fabric device is IPoIB load failure
- upon the next WinOF install.
+ upon the next OFED install.
Uninstall Notes
- If the SRP (SCSI RDMA Protocol) driver has been previously installed,
@@ -914,7 +964,7 @@ occur after the uninstall.
<Return-to-Top>
+OFED install
- From a command windows type 'devmgmt.msc'. Look for
InfiniBand HCA device(s) along with Network IPoIB devices .
@@ -965,18 +1015,18 @@ commands:
If the Subnet Manager was installed as 'started' on this system, find the
InfiniBand Subnet Manager entry; entry should be automatic & started.
-A Vista WinOF installation can fail due to protection failures when
+A Vista OFED installation can fail due to protection failures when
installing the HCA driver. Vista HCA driver installation failure can be caused
by double-clicking the .msi installer
file to start the installation.
-WinOF installs for (Vista only) require the installation be started from a
+OFED installs for (Vista only) require the installation be started from a
privileged Administrator command window.
Start a privileged Administrator command window (Start->Command
Prompt->Right-click->Run as Administrator) and execute:
msiexec /I
-WinOF_xxx_yyy.msi
-To create a LOG file of your WinOF installation, execute this command:
-msiexec /I WinOF_xxx_yyy.msi /Lv %TEMP%\WOF-install.log
-View %TEMP%\WOF-install.log
+OFED_xxx_yyy.msi
+To create a LOG file of your OFED installation, execute this command: msiexec /I
+OFED_xxx_yyy.msi /Lv %TEMP%\OFED-install.log
+View %TEMP%\OFED-install.log
msiexec /? for details.
Server 2008 or Vista can also fail to install due to driver install files
left over from previously failed install attempts; see %windir%\system32\DriverStore\{Temp|FileRepository}.
@@ -1101,14 +1151,14 @@ mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">
device from 'InfiniBand Host Channel Adapters', and make sure you uninstall the system device
'InfiniBand Fabric' if it is present.
- REBOOT and retry the WinOF installation again.
+ REBOOT and retry the OFED installation again.
See
ibscan.bat and ibcleanup.bat @
-
- http://www.openfabrics.org/downloads/WinOF/etc/.
- ibscan will display WinOF files on your system.
- ibcleanup will attempt to remove all WinOF files from your syste.
- WARNING - ibcleanup is not valid as a WinOF uninstall tool!
<Return-to-Top>
+
+ http://www.openfabrics.org/downloads/windows/etc/.
+ ibscan will display OFED files on your system.
+ ibcleanup will attempt to remove all OFED files from your syste.
+ WARNING - ibcleanup is not valid as a OFED uninstall tool!
<Return-to-Top>