Eclipse Instal Guide

ECLIPSE Suite
Installation Guide
2008.1
www.cadfamily.com EMail:cadserv21@hotmail.com The document is for study only,if tort to your rights,please inform us,we will delete
Proprietary Notice
Copyright 1982- 2008 Schlumberger. All rights reserved. No part of this document may be reproduced, stored in a retrieval system, or translated in any form or by any means, electronic or mechanical, including photocopying and recording, without the prior written permission of Schlumberger. Use of this product is governed by the License Agreement. Schlumberger makes no warranties, express, implied, or statutory, with respect to the product described herein and disclaims without limitation any warranties of merchantability or fitness for a particular purpose.
Patent information
Schlumberger ECLIPSE reservoir simulation software is protected by US Patents 6,018,497, 6,078,869 and 6,106,561, and UK Patents GB 2,326,747 B and GB 2,336,008 B. Patents pending. Schlumberger FrontSim reservoir simulation software is protected by US Patent 2004/0015295A1.
Service mark information

The following are all service marks of Schlumberger: The Calculator, Charisma, ConPac, ECLIPSE 100, ECLIPSE 200, ECLIPSE 300, ECLIPSE 500, ECLIPSE Office, EDIT, Extract, Fill, Finder, FloGeo, FloGrid, FloViz, FrontSim, GeoFrame, GRAF, GRID, GridSim, Nodal, NWM, Open-ECLIPSE, PetraGrid, PIPESIM, PIPESIM FPT, PIPESIM GOAL, PlanOpt, Prodman, Pseudo, PVTi, RTView, SCAL, Schedule, SimOpt, VFPi, Weltest 200.
Trademark information
Silicon Graphics and IRIX are registered trademarks of Silicon Graphics, Inc. OpenGL and the oval logo are trademarks or registered trademarks of Silicon Graphics, Inc. in the United States and/or other countries worldwide. OpenInventor and WebSpace are trademarks of Silicon Graphics, Inc. IBM, AIX are registered trademarks of International Business Machines Corporation. Sun, SPARC, Solaris, Ultra and UltraSPARC are trademarks or registered trademarks of Sun Microsystems, Inc. Macintosh is a registered trademark of Apple Computer, Inc. UNIX is a registered trademark of UNIX System Laboratories. Motif is a registered trademark of the Open Software Foundation, Inc. The X Window System and X11 are registered trademarks of the Massachusetts Institute of Technology. PostScript and Encapsulated PostScript are registered trademarks of Adobe Systems, Inc. OpenWorks and VIP are registered trademarks of Landmark Graphics Corporation. Lotus, 1-2-3 and Symphony are registered trademarks of Lotus Development Corporation. Microsoft, Windows, Windows NT, Windows 95, Windows 98, Windows 2000, Windows XP, Internet Explorer, Intellimouse and PowerPoint are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Netscape is a registered trademark of Netscape Communications Corporation. AVS is a registered trademark of AVS Inc. ZEH is a registered trademark of ZEH Graphics Systems. Ghostscript and GSview are Copyright of Aladdin Enterprises, CA. GNU Ghostscript is Copyright of the Free Software Foundation, Inc. Linux is Copyright of the Free Software Foundation, Inc. IRAP is Copyright of Roxar Technologies. LSF is a registered trademark of Platform Computing Corporation, Canada. VISAGE is a registered trademark of VIPS Ltd. Cosmo is a trademark and PLATINUM technology is a registered trademark of PLATINUM technology, inc. PEBI is a trademark of Veritas DGC Inc./HOT Engineering GmbH. Stratamodel is a trademark of Landmark Graphics Corporation. GLOBEtrotter, FLEXlm and SAMreport are registered trademarks of GLOBEtrotter Software, Inc. CrystalEyes is a trademark of StereoGraphics Corporation. Tektronix is a registered trade mark of Tektronix, Inc. GOCAD and JACTA are trademarks of T-Surf. Myrinet is a trade name of Myricom, Inc. This product may include software developed by the Apache Software Foundation (http://www.apache.org). Copyright (c) 1999-2001 The Apache Software Foundation. All rights reserved. MPI/Pro is a registered trademark of MPI Software Technology, Inc. The TGS logo is a trademark of TGS, Inc. POSC, the POSC logo and Epicentre are registered trademarks of Petrotechnical Open Standards Consortium, Inc. Red Hat is a registered trademeak of Red Hat, Inc. This product may include software developed using LAPACK (http://www.netlib.org/lapack/), which is copyright of its authors. Scali is a trademark of Scali Inc.
www.cadfamily.com EMail:cadserv21@hotmail.com The document is for study only,if tort to your rights,please inform us,we will delete
Preface
Conventions
Data file, and directory names are shown in Courier, a fixed spaced font, for clarity. On some operating systems the file system is case sensitive for example UNIX. Be aware of this and that the files may not appear as written on your computer. We also use the forward slash / as a directory delimiter. This is the standard for UNIX; on PCs it should be replaced by the backslash \. The convention for batch files containing groups of operating system commands is also machine dependent. On PCs batch files will start with the character $, while UNIX we uses @.
Typefaces used
All regular text is in Palatino font, and headlines at different levels are in different levels of Helvetica Bold. Equation variables in text are in Times font as is used in formatted equations.
Italic, for example e = mc2. This is the same
Links and cross-references to other pages in this manual or others are highlighted in bright blue. Keywords and other program code items are represented in Courier, a fixedspace font similar to that seen on DOS and UNIX screens. Menu items are distinguished from surrounding text by being in Helvetica similar to settings often found on interactive program screens. Program variables are in Courier like the keywords.
Standard buttons in interactive programs

Unless specifically stated in the manual the listed buttons perform the following standard operations:
Apply
Applies the changes you have made in the dialog or panel. The dialog box or panel remains open.
OK
Applies the changes you have made in the dialog box or panel and closes it.
Close
Closes the dialog box or panel.
Cancel
Closes the dialog box or panel without applying any changes.
ECLIPSE Suite EMail:cadserv21@hotmail.com www.cadfamily.com Installation Guide The document is for study only,if tort to your rights,please inform us,we will delete
Help
Opens the help page for the screen, dialog box or panel.
In case of problems
Should you find an error, an omission, or something that is not clear, or you simply wish to make a comment about any part of the documentation, we will be pleased to learn about it so that we can improve our product. Please send the details in an email to: documentation@abingdon.oilfield.slb.com giving full details, or contact your local Support Team who will be pleased to help.
ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 4 The document is for study only,if tort to your rights,please inform us,we will delete
Table of Contents
List of Figures ..... ...................................................................................................................................................................6 List of Tables ...... ...................................................................................................................................................................7
Chapter 1 - 2008.1 Simulation Software System Requirements ................................................... 8

Platform Availability ................................................................................................................................................................8 General requirements .............................................................................................................................................................9
Chapter 2 - 2008.1 Simulation Software installation.................................................................... 12

Preparing to install 2008.1 Simulation Software ...................................................................................................................12 DVD/CD Organization...........................................................................................................................................................14 Installing PC software from DVD ..........................................................................................................................................15 Directory Structure................................................................................................................................................................20 Installing Linux software from CD/DVD ................................................................................................................................21 Directory Structure................................................................................................................................................................31
Chapter 3 - Licensing ..................................................................................................................... 33

Installing Schlumberger Licensing ........................................................................................................................................33
Chapter 4 - Running the software ................................................................................................. 35

UNIX systems - macros and scripts......................................................................................................................................35 PC systems - macros and launcher......................................................................................................................................39 ECLIPSE 100 and ECLIPSE 300 .........................................................................................................................................42 Parallel ECLIPSE on UNIX and Linux ..................................................................................................................................43 Parallel ECLIPSE on PC ......................................................................................................................................................56 3D Stereo options .................................................................................................................................................................57 Solaris graphics configuration options ..................................................................................................................................58
Chapter 5 - Microsoft CSS Installation ......................................................................................... 59

Installation .......... .................................................................................................................................................................59
Appendix A - Non-PVM remote and external job options ........................................................... 67

Using the Non-PVM remote option .......................................................................................................................................67 Using the external job option..............................................................................................................................................70 Running from a PC to a UNIX machine ................................................................................................................................71
Appendix B - R2SL.......................................................................................................................... 75
PC Configuration .................................................................................................................................................................75
Appendix C - Upgrading a license................................................................................................. 79

Upgrading a license for ECLIPSE (2000A-2005A_1) to 2006.1 and later version................................................................79
Appendix D - Installing OFED drivers ........................................................................................... 87

Installation Guide .................................................................................................................................................................87
Appendix E - Index.......................................................................................................................... 97
ECLIPSE Suite EMail:cadserv21@hotmail.com www.cadfamily.com Installation Guide Table of Contents The document is for study only,if tort to your rights,please inform us,we will delete
List of Figures
Figure 4.1 Figure 4.2 Figure 5.1 Figure 5.2 Figure 5.3 Figure 5.4 Figure 5.5 Figure 5.6 ........... ........... ........... ........... ........... ........... ........... ........... LSF Batch console display......................................................................................................................53 LSF - xlsmon, View | Detailed Load ........................................................................................................54 CSS Installation Type .............................................................................................................................60 Required components ............................................................................................................................61 The Job Queue Window .........................................................................................................................62 Tasks pane .............................................................................................................................................63 Task Properties .......................................................................................................................................65 Job Queue ..............................................................................................................................................66
ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 6 List of Figures The document is for study only,if tort to your rights,please inform us,we will delete
List of Tables
Table 1.1 Table 1.2 Table C.1 Supported operating systems and compilers.............................................................................................9 Third party tools and applications ............................................................................................................10 Common errors and solutions..................................................................................................................85
ECLIPSE Suite EMail:cadserv21@hotmail.com www.cadfamily.com Installation Guide List of Tables The document is for study only,if tort to your rights,please inform us,we will delete
2008.1 Simulation Software System Requirements
Chapter 1
Platform Availability
Schlumberger advises clients that it is its intention to cease supporting the interactive products (ECLIPSE Office, Near Wellbore Modeling, PlanOpt, SimOpt, Schedule, ECLIPSE FloGrid, FloViz, Grid, GRAF, SCAL, PVTi and VFPi) on the traditional UNIX platforms, as follows: SUN SOLARIS: last release version 2007.1 These applications are available under Linux for Intel EMT64bit and AMD Opteron 64-bit platforms on versions from 2006.1, and Windows XP64 on versions from 2006.2. The Simulators will cease to be supported on UNIX platforms as follows: SUN SOLARIS: last release version 2008.1
ECLIPSE Suite EMail:cadserv21@hotmail.com 2008.1 Simulation Software System Requirements www.cadfamily.com Installation Guide Platform Availability The document is for study only,if tort to your rights,please inform us,we will delete
General requirements
Software products and supported platforms
These requirements are specific for the 2008.1 release of ECLIPSE suite. These products are released in a 1 DVD and 1 CD set for the platforms and operating systems as listed in the table below. Parallel ECLIPSE 100 and Parallel ECLIPSE 300 are also included in this set.
Linux
On Linux, ECLIPSE 100, ECLIPSE 300 and FrontSim are released. ECLIPSE 100, ECLIPSE 300 are in serial and parallel versions, but FrontSim is only in serial version. The following pre and post processor products are also released on Linux: ECLIPSE Office, FloGrid, FloViz, GRAF, GRID, Schedule and SimOpt.
.
Table 1.1 Machine

Sun (last release version 2008.1)
Supported operating systems and compilers Operating System

Solaris 8/Solaris 10
Required Software
OpenGL 1.3.2 or later
Notes
For Parallel ECLIPSE 100 and Parallel ECLIPSE 300 Sun HPC version 4.0 is required, and HPC 5 is recommended. For the 64 bit versions Sun dev studio 8 must be installed to get the run time libraries. The compilers are not needed. Minimum screen resolution for PC systems is 1024x768. Internet Explorer 6 is mandatory for Microsoft .NET components and for running MPI/Pro, which is used by Parallel ECLIPSE.
PC
Windows XP plus Service Pack 2 is required.
Minimum screen resolution for PC systems is 1024x768. Internet Explorer 6 is mandatory for Microsoft .NET components and for running MPI/Pro, which is used by Parallel ECLIPSE. Minimum screen resolution for PC systems is 1024x768. Internet Explorer 6 is mandatory for Microsoft .NET components and for running MPI/Pro, which is used by Parallel ECLIPSE.
Windows XP64
ECLIPSE Suite EMail:cadserv21@hotmail.com 2008.1 Simulation Software System Requirements www.cadfamily.com Installation Guide General requirements The document is for study only,if tort to your rights,please inform us,we will delete
Table 1.1 Machine
Supported operating systems and compilers (Continued) Operating System

Vista 64
Required Software
Notes
Minimum screen resolution for PC systems is 1024x768. Note that MPIPro does not with SP1 See "Microsoft CSS Installation" on page 59 for full details.
Windows CCS
Windows Server 2003r2 x64 CCS SP1 Red Hat 4.0 update 6 Red Hat 4.0 update 6 or SuSE SLES 10 SP1
Linux 32-bit Linux x86_64
This is the 64-bit version for the AMD Opteron and Intel EM64T chips
Linux 64-bit (Itanium 2) SGI Altix
Red Hat 4.0 update 6 SGI ProPack 5
See "Installing Myrinet drivers for Linux" on page 23. For parallel, special Altix execs are provided, and are automatically selected.
Table 1.2 Software

LSF
Third party tools and applications Version Notes
We recommend LSF version 7.0, Platform Computing can add an update 2 MPC version. LSF SIS integration kit to augment resource checking in the simulator macros by including license checking. For further details contact Platform Computing www.platform.com 11.3 8.0 (PC Windows) 8.0 (Linux) 1.2b145 2.080 (SGI) Used for License Manager configuration. Used for manuals. On-line help uses HTML. Used by FloGrid.
FLEXlm Adobe Acrobat Carnac
2008.1 EMail:cadserv21@hotmail.com ECLIPSE Suite Installation Guide www.cadfamily.com Simulation Software System Requirements 10 General requirements The document is for study only,if tort to your rights,please inform us,we will delete
Table 1.2 Software

MPI
Third party tools and applications (Continued) Version

1.7 Internet Explorer 6 or greater, Firefox 2.0 or greater, or equivalent.
Notes
See "Installing MPI/Pro" on page 17. Used by on-line help. IE6, not lower, is used by MPI. Used by Linux simulators for interconnecting independent MPI.
Web/HTML browser
Scali MPI
5.6.1
Notes
2008.1 is not supported on Windows NT Server., Vista 32 and Windows Server 2003/2008 32 bit. For more details on requirements for Parallel ECLIPSE 100 and ECLIPSE 300, see "Parallel ECLIPSE on UNIX and Linux" on page 43 and "Parallel ECLIPSE on PC" on page 56. Simulations are only supported on Windows 2003 Server. Pre and post processing software is not supported.
Sun
On Solaris systems, it is necessary to reconfigure shared memory to use the software. This requires modifying the file /etc/system and adding the following lines:
shmsys:shminfo_shmmax=65536000 shmsys:shminfo_shmmin=1 shmsys:shminfo_shmmni=100 shmsys:shminfo_shmseg=32
set set set set
The system must be rebooted to make the changes take effect.
Networked PCs
Exceed 8.0 3D or later is recommended.
Linux (32 and 64 bit) executables for parallel

Executables are available on DVD 1 for the following: Ethernet (also works with Gigabit). Note that Itanium2 and x86_64 executables are not limited to 2GB memory addressing per process. SGI Altix. Altix uses the SGI NUMAlink. Executables are automatically selected. Scali will automatically choose the high-speed interconnect if available.
ECLIPSE Suite EMail:cadserv21@hotmail.com 2008.1 Simulation Software System Requirements www.cadfamily.com Installation Guide General requirements The document is for study only,if tort to your rights,please inform us,we will delete
11
2008.1 Simulation Software installation
Chapter 2
Preparing to install 2008.1 Simulation Software

2008.1 is a major release and can be installed independently of previous major or incremental releases. It can be installed over existing installations. Users with existing ECLIPSE installations should always ensure that the macros directory is backed up before proceeding with the software installation. 1 The recommended way to do this is to copy the macros directory to macros.old. This is because the macros directory contains vital information about the existing software installation - including the passwords to run existing installed pre-98A software if any (in CONFIG.ECL). It is also recommended that the tools directory is moved to tools.old. The tools.old directory may later be removed when the new installation is working satisfactorily. It is imperative that the previous versions of reservoir simulation software are installed before installing the current version. Do not install the current version followed by an older version.
Note
For all applications the manuals are available in PDF (Portable Document Format) that can be browsed and printed with Adobe Acrobat Reader. Note It is assumed in this chapter that the software is installed on a default path /ecl.
ECLIPSE and Scali

ECLIPSE 2008.1 has been linked with Scali 5.6.1. This means that if you want to use the functionality provided with Scali 5.6.1 you must install it from DVD 1
ECLIPSE Suite EMail:cadserv21@hotmail.com 2008.1 Simulation Software installation www.cadfamily.com Installation Guide Preparing to install 2008.1 Simulation Software The document is for study only,if tort to your rights,please inform us,we will delete
12
There is however a caveat to this. If you install Scali 5.6.1 earlier versions of ECLIPSE (2005A) will not run as the in built Scali license is not valid for that version. There are two solutions to this. If you are not on a Dual socket dual core system then the advantages to Scali 5 will not be very great, so you can run ECLIPSE 2008.1 with the previous version of Scali (4.4.2). Alternatively, contact your SIS account manager to obtain a separate license for Scali 5 to run on your system.
ECLIPSE Suite EMail:cadserv21@hotmail.com 2008.1 Simulation Software installation www.cadfamily.com Installation Guide Preparing to install 2008.1 Simulation Software The document is for study only,if tort to your rights,please inform us,we will delete
13
DVD/CD Organization
2008.1 software is distributed in a set of 1 DVD and 2CDs.
DVD 1
DVD 1 contains software for PC (Windows 2000 and XP). This includes: 2008.1 installation with all documentation, data and tutorials MPI/Pro 1.7 Runtime installation Acrobat application for PC Documentation in Acrobat format (PDF) for PC Dongle drivers. The 32-bit simulators and pre-/post- processors compiled for Red Hat 4.0 update 5 The simulators and pre-/post-processors for all x86 64-bit Linux architectures compiled for Red Hat 4.0 and SuSE Linux Enterprise 10. Simulator executables for Linux Utility resources. It contains: Benchmarks PC resources Full documentation (manuals and on-line help), data and tutorials for UNIX Sales presentations UNIX resources LINUX resources (Scali, MPI, LSF Integration Kit etc.).
Cougar for PC (Windows 2000 and XP) Merak PEEP is no longer distributed with ECLIPSE software.
Note
Note
For installation on a PC, continue from "Installing PC software from DVD" on page 15. For installation on UNIX or Linux systems, continue from "Installing Linux software from CD/DVD" on page 21.
CD2
Software for Sun. Includes reference manuals and data for Simulators. Pre and post processing applications are no longer supplied.
2008.1 EMail:cadserv21@hotmail.com ECLIPSE Suite Installation Guide www.cadfamily.com Simulation Software installation 14 DVD/CD Organization The document is for study only,if tort to your rights,please inform us,we will delete
Installing PC software from DVD

1 2 3 Insert DVD 1 in the DVD drive. The Schlumberger installation panel should appear; if not, then using the File Browser to access the DVD, run the script D:\PC\install\installer.exe. Click on Install ECLIPSE Software 2008.1. This will install the 2008.1 programs.
Notes
We recommend installing in a directory path that has no spaces in the path name, not for example in C:\Program Files\ecl. We assume \ecl as the root in the text that follows. Occasionally, for large disks, the installation program will calculate the space available incorrectly; as long as sufficient space is available, this should not cause any problems and the installation should go through correctly. If insufficient disk space is available to complete the installation a blank message box will appear. Also, the installation procedure assumes that the Windows directory is C:\WINDOWS. 4 We recommend you disable your virus checker temporarily during the installation process. You can choose between a standalone installation and a network installation. For standalone, choose the Standalone option. For a network installation, choose the Server option to install on the network server, then reinstall on each client machine choosing the Client option. DVD 1 contains directories \3rdparty\pc\resource and /3rdparty/UNIX/resource. The PC directory contains the following: adobe_acrobat ataman 6 contains Adobe Acrobat Reader 8.0 contains Ataman software
To view the on-line manuals you will need to install Acrobat Reader. For on-line help, except for GRID, and for GridSim which requires Acrobat, an HTML browser is required. Acrobat Reader is installed automatically; however, the relevant directory may need to be added to the path (see below). a Installing Acrobat Reader Acrobat Reader for both PC and UNIX is included on installation DVD 1 in the PC\resource\3rdparty\acrobat and UNIX/3rdparty/acrobat subdirectories respectively. On the DVDROM (DVD 1 mounted as /DVDROM in the example below)
PC\3rdParty\resource\acrobat\ AdbeRdr810_en_us.exe
ECLIPSE Suite EMail:cadserv21@hotmail.com 2008.1 Simulation Software installation www.cadfamily.com Installation Guide Installing PC software from DVD The document is for study only,if tort to your rights,please inform us,we will delete
15
Hint
The latest version of the Adobe Acrobat Reader for your platform can be downloaded from the Adobe website, at: http://www.adobe.com/products/acrobat/readstep.html. Selection of Include option for searching PDF files, is very highly recommended. See the Adobe Acrobat Reader On-Line Help for more information on the search function.
User Manuals
For 2008.1 the user manuals in PDF format are installed by default. From the launcher, click on the manuals button and a bookshelf appears. This is a PDF document. You may access manuals from previous versions (99B, for example) from the 2008.1 bookshelf, if they are installed.
Grid menus
These are to be found in the directory ecl\2008.1\grid\grid_charts. They are named PRIMARY_MENU_STRUCTURE.PDF and DISPLAY_MENU_STRUCTURE.PDF.
Configuring PC software
General notes
Paths and environmental variables in XP machines are set in the user environment. Two main directories need to be on the path: ECL\HOME and ECL\MACROS. In the case of a standalone installation, both of these will reside on the same (local) disk; however in the case of a client/server installation, the ECL\HOME directory will reside on the client (local) disk, while the ECL\MACROS directory will reside on the server disk. The next example command is for a XP PC with Adobe Acrobat Reader and the ECLIPSE software suite and guide files installed on the C:\ drive. It is entered on the Guide Setup panel in GridSim. C:\program files\adobe\acrobat 8.0\reader\acrord32 C:\ecl\gridsim\data\gridsim_ug.pdf Or more generally, enter: $ADOBEPATH\acrobat 8.0\reader\acrord32 $GUIDE_PATH\gridsim_ug.pdf where $ADOBEPATH and $GUIDE_PATH are specific to your machine. Hint $ADOBEPATH is the path to where your copy of Adobe Acrobat is stored. $GUIDE_PATH is the path to where your copy of gridsim_ug.pdf is stored.
If you want the GridSim guide to be available each time you start the program, edit the $ADOBEPATH and $GUIDE_PATH in your GRIDSIM.INI file to your machine settings.
2008.1 EMail:cadserv21@hotmail.com ECLIPSE Suite Installation Guide www.cadfamily.com Simulation Software installation 16 Installing PC software from DVD The document is for study only,if tort to your rights,please inform us,we will delete
$ADOBEPATH\acrobat 8.0\reader\acrord32 $GUIDE_PATH\gridsim_ug.pdf
Standalone installation on Windows XP

Having installed the software from the DVD, check the environment in Start | Settings | Control Panel | System | Advanced | Environment Variables The User variables path should include the ECL\HOME and ECL\MACROS directories, in that order.
Client/server installation on Windows XP

During the server installation, you will have been prompted to specify a path for installing the software on the server. During the client installation, you will again be prompted to specify the path to the installation on the server. Note If the drive is mapped, the drive letter on the client PC may well be different from the drive letter on the server PC, depending on the drive letter chosen to map the servers disk.
In the same way as for the standalone installation (see above paragraph), check the environment in Start | Settings | Control Panel | System | Advanced | Environment Variables The User variables path should be picking up the ECL\HOME directory from the client and the ECL\MACROS directory from the server, in that order, for example: ...C:\ECL\HOME; I:\APPS\ECL\MACROS;... Note The client installation requires write access to the directory containing the server installation. This permission is no longer needed after the client installation is completed, and may be removed for security purposes.
Installing MPI/Pro
To run Parallel ECLIPSE 100 or Parallel ECLIPSE 300 and R2Sl (see) it is necessary to install and configure MPI/Pro. To do this: 1 First because of potential conflicts it is recommended that you remove all versions of MPI/Pro and the Microsoft .NET framework from your systems by going to Control Panel | Settings | Add/Remove Programs and then removing Microsoft .NET Framework 1.0, Microsoft .NET Framework 1.1 and MPI/Pro 1.6.4 if any of these exist already Insert DVD1 in the DVD drive The Schlumberger installation panel should appear as before. Click on Install MPI Software Technologies MPIPro to install.
2 3
17
When given the option to choose a location either let the default stand or choose your own location. Take the typical install option unless you feel brave. The license key will be found under \PC\install\3rdParty\MpiPro1.7\licensekey.txt Click on Start | Programs | Verrari Systems| MPIPro | Password registration.
and enter your PC login password. It is possible that MPI Software Technology may not appear in Start | Programs, for instance if it has already been installed by another user. In this case, run C:\Program Files\MPIPro\bin\MPIPasswd.exe. The installation of MPI/Pro will also automatically install Microsoft .Net Framework. If it is necessary to re-install MPI/Pro, then both MPI/Pro and Microsoft .Net Framework must first both be uninstalled. Note We have also seen problems where MPI/Pro is being updated. In these cases you may need to delete the .mpipass file from your system (usually found in the directory that you login to, try opening a command shell and it is that directory).
Note
The password that is entered is the same password you use to log in to the machine itself. If you change your login password after the initial installation of MPI/Pro then you will need to re-register your password by running mpipasswd from either the Start menu ->Programs-Verrari Systems->MPIPro-> password registration or by running it from a command prompt. If your login password is changed, you will need to re-register it.
Problems installing MPI/Pro

There have been several problems noted with passwords and MPI/Pro as it requires that a password file be written. There may be cases where the users login directory is not writable. In these cases it is necessary to do the following. 1 2 3 4 5 Open a command prompt Window and go to the %MPI_HOME%\bin directory Run MPIPasswd.exe -pw new password file (note this is the complete path including file name not just a directory). Go to the %ECL_HOME% directory Edit the files $mpieclipse.bat and $mpie300.bat and add the switch -pw (password) to the line containing mpirun. You should now be able to run Parallel ECLIPSE and Parallel E300 from the command line. Unfortunately the launcher generates its own run scripts on the fly and these cannot be modified so using the launcher is not possible in these circumstances.
Note
Another issue that has arisen is MPI/Pro using passwords from the environment in preference to the one from @eclrc. In these cases the LM_LICENSE_FILE variable must be modified or deleted to include the path to the ECLIPSE license file server. The machine must then be rebooted, as MPI/Pro retains a memory of its startup environment in order to pick up any changes. The other option is to go to SERVICES and stop and restart the MPI/Pro service (MPI/Pro Startup Service).
2008.1 EMail:cadserv21@hotmail.com ECLIPSE Suite Installation Guide www.cadfamily.com Simulation Software installation 18 Installing PC software from DVD The document is for study only,if tort to your rights,please inform us,we will delete
We have observed problems installing MPI/Pro on some machines. In this case, uninstall both MPI/Pro and Microsoft .Net and try reinstalling MPI/Pro. If problems persist, the reason may be that the MPI startup service has not been uninstalled. To do this manually: 1 2 3 Open a command prompt window and go to the %MPI_HOME%\bin directory. Make sure MPIStartupServer.exe file is there. Now go to "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322" (This path may slightly vary depending on your OS. The above assumes Windows XP Professional.) 4 5 6 7 Make sure there is installutil.exe in this directory. You can add this directory to your path. set PATH=%PATH%;C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322; Now go back to the %MPI_HOME%\bin directory. and enter the following command: >installutil.exe /u MPIStartupServer.exe This should uninstall the service. You can now try reinstalling MPI/Pro MPI/Pro requires Internet Explorer 6 or later
Note
Note
With Windows XP Service pack 2, the Windows fire wall will initially block MPIrun from working. Normally you get the chance to unblock it but it will put up a screen every time the program runs. This can be turned off through Control Panel | Windows Security Centre and then choose not to generate the message.
We have also seen issues where MPI/Pro complains that there is no license available. This is normally caused by an incompatible version of the Microsoft .NET 1.1 Framework installed. The solution here appears to be to uninstall the existing .NET from Settings -> Control Panel -> Add/Remove programs and then reinstall the .NET provided with MPI/Pro.
The PC launcher
The installation process creates a program group containing the ECLIPSE Launcher. A shortcut to this launcher is also placed on the desktop of the PC.
19
Directory Structure
At the top level this looks like ecl\home ecl\macros ecl\tools ecl\2008.1 The home directory contains: the macro $eclrc.bat ($eclrc for UNIX) files responsible for the functioning of the launcher, for example launcher.bat, launcher.ini log files, such as flex.log, the FLEXlm log file additional resource files. macros for running the programs and utilities, for example $eclipse.bat, $flogrid.bat macros called by the program, and utility macros (see "Running the software" on page 35) specific files used for configuration purposes; in particular $eclrc.bat and CONFIG.ECL files used for monitoring license usage, for example flex.log. a number of subdirectories corresponding to various utilities such as convert and expand directories containing the FLEXlm utilities. directories containing FrameViewer and Acrobat. a bin\pc directory containing executables. a number of program directories corresponding to the various programs, such as eclipse, flogrid, etc. manuals - contains the manuals bookshelf rele_nt - contains the release notes the resource directory that contains resources shared by several programs. a data directory containing sample datasets one or more manual directories, such as eclipse\ecl_rm, flogrid\flog_ug, etc. a tutorials directory containing data for one or more tutorials, for example flogrid\tutorials a help directory containing on-line help.
The macros directory:
The tools directory contains a pc subdirectory which contains:
The 2008.1 directory contains:
A number of directories containing utilities and building blocks, for example
Each program directory (within the2008.1 directory) contains some of the following:
2008.1 EMail:cadserv21@hotmail.com ECLIPSE Suite Installation Guide www.cadfamily.com Simulation Software installation 20 Directory Structure The document is for study only,if tort to your rights,please inform us,we will delete
Installing Linux software from CD/DVD

1 2 To install, insert the relevant CD/DVD in the DVD drive. Mount the CD/DVD as a file system. a On Linux systems: In the default configuration of a Linux system the CD/DVD is automatically mounted as /mnt/cdrom or /media/cd.... in SUSE. Note To unmount the CD/DVD use the command: umount -k /cdrom. The CD/DVD can be ejected using the eject command.
When the CD/DVD is successfully mounted run the auto install C-shell script which is supplied on the CD/DVD: /cdrom/ECLIPSE/install/cdinst.csh
ECLIPSE Suite EMail:cadserv21@hotmail.com 2008.1 Simulation Software installation www.cadfamily.com Installation Guide Installing Linux software from CD/DVD The document is for study only,if tort to your rights,please inform us,we will delete
21
The autoinstall procedure prompts with the following information.

SIS For installation instructions, please refer to the file README.TXT, at the top level of this DVD (ie. if the DVD is mounted as /DVDrom, refer to /DVDrom/README.TXT). For more details, see the Release Notes, which are available in HTML or Acrobat PDF format. The PDF files may be accessed by typing the command "@pdf". The README.TXT is a text file. However, to read the Release Notes, you will need to have FrameViewer or Acrobat Reader installed on your system. Installation kits for these are included on CD 8. Instructions for installing these are included in the README.TXT. Available programs for 2008.1 week 20 1) E300 2) Eclipse 3) Convertgrid 4) Extract 5) Fill 6) FloGrid 7) FloViz 8) FrontSim 9) GRAF 10) GRID 11) GridReceive 12) GridSim 13) Office 14) PVTi 15) ParallelE300 16) ParallelEclipse 17) Pseudo 18) SCAL 19) Schedule 20) SimOpt 21) VFPi 22) tools Select A - Install all programs N - Install none of these S - Select a subset Please enter choice : a Enter proposed location for installation (default /ecl) :
The software then autoinstalls. 4 Once the software has completed its installation process you are prompted with the following question:
Do you want to install macros ? [default n]
Enter "y" when you are ready to overwrite the contents of macros.
2008.1 EMail:cadserv21@hotmail.com ECLIPSE Suite Installation Guide www.cadfamily.com Simulation Software installation 22 Installing Linux software from CD/DVD The document is for study only,if tort to your rights,please inform us,we will delete
Note
You should be prepared to answer "y" to install macros, since this contains important files for 2008.1. The script uses a default answer "n" to prevent accidental overwriting of existing files.
Note 5
Installing Tools also installs Acrobat.
Ensure the macros directory is placed on the default search path. To do this, edit the file .cshrc in the login directory and append the following:
set path=($path /ecl/macros)
On Sun Solaris systems, the location of the X11 runtime library must also be included in LD_LIBRARY_PATH. To do this append this line to the .cshrc file:
setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH:/usr/openwin/lib
Installing Linux from another machine

When installing on Linux 32-bit systems, the following file gets created
tools/linux/mpich/share/machines.LINUX
containing the hostname of the machine on which the install was run. If the Linux install was run on an SGI, for example, this file contains the hostname of that SGI. In this case, when you run @mpieclipse, you will get a message similar to incorrect architecture. This is because that machine is interrogated for its architecture by the Linux machine on which @mpieclipse is being run. The file should contain the name of ANY Linux machine, which is available on the network. Alternatively you can override interrogation of this machine using:
@mpieclipse -hostfile hostfile PARALLEL
Note
This is not an issue when running with LSF. Note also that MPICH will automatically use the machine the job is submitted from as one of the hosts. To override this, use: @mpieclipse -hostfile hostfile -nolocal PARALLEL This will then run only on the hosts specified in the hostfile.
Similarly, the 64-bit installation involves several "makes", which need to be run on a Linux machine.
Installing Myrinet drivers for Linux

Note We assume that if Myrinet cards are present, the driver software is already installed. If this is the case and users wish to use the Myrinet cards they need to interface to the drivers through the Scali MPI software which is provided on DVD 1.
DVD1/3rdparty/LINUX/resource contains the following directories:
23
Myrinet
The Myrinet directory contains the Myrinet driver installation, which can alternatively be downloaded from www.myrinet.com. The file gm-2.0.26_Linux.tar.gz can extracted and installed following the Myrinet installation procedure. Note that GNU C version 3 is required to complete a successful installation of the Myrinet driver.
Myrinet_x86_64
Note To compile the Myrinet drivers for x86_64 platforms you need to run ./configure --enable-32b --enable-64b to allow the code to access either the 64 bit or 32 bit drivers.
Myrinet_ia64
The GM drivers need to be installed the same way and from the same directory as for the Myrinet_ia32 drivers.
Installing Scali drivers for Linux

Note See also the Known Issues chapter in the Release Notes.
In order to use R2SL or the fast interconnects under Linux it is also necessary to install the Scali drivers. These can be used on either Gigabit, Infiniband or the Myrinet modes of transport. The Scali MPI works generically without Myrinet and should give speed-ups over normal ethernet connections. Note that the examples here are for gm 2.0.19. We have tested the Scali interface up to gm 2.0.28. The base software resides on DVD1 under LINUX/resource/Scali.
Installing Scali software

1 To install Scali tar the following file: tar -zxvf Scali_MPI_Connect-5.6.1-58818.tar Note that all versions are contained in the one command file, including SLES, x86_64, IA32 and IA64. 2 cd to the Scali_MPI_Connect--5.6.1-58818 directory. To install for Ethernet only: run ./smcinstall -ato To install the Myrinet version you need to add the -m option, for example ./smcinstall -a -m -o to install the Infiniband version you need the -b option, for example ./smcinstall -a -b -o
Note
If Myrinet does not work it is normally caused by the fact that the interconnect libraries are not in /etc/ld.so.conf. It is necessary to add lines of the form /opt/interconnect/gm-2.0.26/lib /opt/interconnect/gm-2.0.26/lib64 to this file on all the nodes and then run /sbin/ldconfig. Prior to the gm-2.0.26 level of the Myrinet drivers all the libraries were in the lib directory. After gm-2.0.26 they are separate.
Tuning Scali
Scali may need to be tuned to run optimally. On Myrinet-based systems you can edit the /opt/scali/ScaMPI.conf file and add the parameters eager_size=128k eager_threshold=256k eager_count=8 eager_factor=8 For Silverstorm IB-based systems we have found that setting channel_size=256k channel_inline_threshold=16k transporter_size=0 transporter_count=0 pool_size=64M eager_count=8 eager_factor=8 in the ScaMPI.conf file improves performance. You also need to add the networks line networks=smp,ib0(1),tcp In general on most systems we have found that adding the line networks=smp,gm0,ib0,tcp covers all bases. However, on some systems (IBM OpenPower is an example) this is not possible as there is no support for IB. Note /opt/scali/etc/ScaMPI.conf is the global config. file, valid for all users. Alternatively each user can set their own parameters in a ScaMPI.conf in their home directory. This could be necessary for instance for clients running with the Infiniband interconnect as they will need to set the networks parameter to networks=smp,ib0,tcp instead of the default networks=smp,gm0,tcp. For Infiniband systems use networks=smp,ib0,tcp. The user can also have a ScaMPI.conf file in the directory from which they are running the software. The precedence in the files being picked up is (1) local directory, (2) users home directory and then /opt/scali/etc.
On Gigabit-based systems it may be worth setting the environment variables SCAFUN_TCP_RXBUFSZ=131072
25
and SCAFUN_TCP_TXBUFSZ=131072 in the ecl/macros/@eclrc file Caution Although these switches have been tested in Abingdon and do improve the performance for all the runs we have done, they may not improve the performance of all runs.
More Scali tuning

There are several other variables that can be useful when working with Scali setenv SCALI_NETWORKS_VERBOSE 2 will help you diagnose which method of communication that Scali uses to communicate between processes. Can be useful when debugging interconnects setenv SCAMPI_WORKING_DIRECTORY can be used if the compute nodes do not have the same directory mount points as the submitting node.
Sometimes Scali runs out of shared memory space. The following has been shown to work at one client site.
HP server (Itanium processor) Setting environment variable P4_GLOBMEMSIZE to 200000000 Kernel shared memory Setting shmmax kernel parameter to 4GB (Must be larger than P4_GLOBMEMSIZE) Setting shmall kernel parameter to 4194304 * Made the changes permanent by adding to sysctl.conf
RSH tuning
By default the MPICH MPI uses RSH for communication. Some clients will not allow this and require the use of SSH. To set MPI to use this use the command
setenv P4_RSHCOMMAND /usr/bin/ssh
Also on some systems we find that rsh is not installed by default but the code asks for the Kerberos version. To solve this either install the Kerberos version or create a directory /usr/kerberos and within that create a link ln -s /usr/bin/rsh rsh on all nodes.
Installing Infiniband drivers

We recommend that you install the OFED drivers, see "Installing OFED drivers" on page 87.
General Infiniband notes

When plugging Infiniband cables into the PCI-X/E cards, note that Scali uses device names IB0 and IB1. The ports are usually labelled Port 1 and 2.
If the ECLIPSE/Scali fails to work as expected it may be that the cable is plugged into the incorrect port. It is useful to set the SCALI_NETWORKS_VERBOSE environment variable mentioned in the previous section. This shows if the Infiniband is working properly. See the top of the <datasetname>.LOG file if running via LSF or in the background, or the start of the ECLIPSE output. It can help troubleshooting to configure IP over IB. This allows you to "ping" the other computers via the IB interface. If the ping succeeds then you know all the hardware is physically connected properly. In addition see the specific Voltaire and Silverstorm sections that follow.
Voltaire Infiniband
Follow the install instructions from the Infiniband supplier. However, the following additional steps may be necessary. A good indication is when IP over IB is working properly, but ECLIPSE/Scali is not. For Redhat 4.0 or a newer kernel, edit the file /etc/security/limits.conf and add the following two lines: soft memlock <number> hard memlock <number> The <number> value denotes the number of kilobytes that may be locked by a process. The file above contains further documentation. For SuSE SLES 9, add the following line to the file /etc/sysctl.conf: vm.disable_cap_mlock=1 Or, run sysctl -w vm.disable_cap_mlock=1 on the local machine. Note The steps described above will allow any user in the system to lock as much as the whole memory set in the configuration files.
Silverstorm Infiniband
Follow the install instructions from the Infiniband supplier. If possible, try to install from a .RPM. If you are compiling from source, however, please check that you have all the development packages installed. These must include the following: X11 development libs Readline Gcc G++ F77 Kernel Source X Windows Development. Please also check that the date and time are set correctly on your system; the make script fails if the date and time on some files are later than the computers time.
27
User Manuals and On-line Help

User manuals are provided in PDF format. On-line help is provided in HTML 3.2. For 2008.1 the user manuals are installed by default as part of the installation on PC, and from DVD 1 for UNIX. (See "DVD/CD Organization" on page 14 for more information.) The on-line help is provided by default as part of the installation with the associated program, on each platform. Since the manuals form part of the on-line help in many instances, they are also provided in HTML format. The PDF format has been tested on all the platforms we support with the most recent version of Acrobat Reader for the platform. All PDF files are designed for compatibility with Acrobat Reader 4.0.5 or higher. The HTML has been tested for viewing with Netscape 7.x (tested on PC and UNIX), Internet Explorer 6.x, Mozilla Firefox and Opera 6.x browsers (tested on PC only) or higher.
Printing manuals
To print a manual or part of a manual: Open the PDF in Acrobat and print the pages you require. You may find that selecting the Fit to Page option gives you better page appearance.
Printing manuals from the HTML files is not recommended.
Installing Acrobat Reader

To access the PDF versions of the manuals, Acrobat Reader needs to be installed and added to the search path. It is installed automatically by the ECLIPSE installation process; however, it may be necessary to add the Acrobat directory (ecl/tools/<machinetype>/acroread/bin) to the path. If you are installing a machine version from a machine with a different operating system (such as installing ECLIPSE for a Sun using a CD-ROM on an IBM machine) you will need to install Acrobat separately. Caution A security flaw in some commonly-distributed file viewing programs may make it possible for attackers to use PDF and PostScript files to run malicious code on machines using the UNIX or Linux operating systems, according to an advisory released by technology security company iDefense Inc. Installation of the Adobe Acrobat Reader for reading and printing PDF is strongly recommended to avoid this flaw.
The Acrobat Reader for UNIX is included on installation DVD 1 in the unix/resource/adobe_acrobat subdirectory. The Acrobat file locations for the supported UNIX Operating Systems are listed below. On the DVD ROM (mounted as /cdrom in the examples below) /cdrom/cdrom0/UNIX/resource/adobe_acrobat/ADOBEREADER_enu_8.1. 1-1.SPARC.tar.gz is the Sun Solaris version of Adobe Acrobat Reader /mnt/cdrom/LINUX/resource/Acrobat/AdobeReader_enu-8.1.11.i386.rpm for Linux.
The relevant file needs to be copied from the CD to your disk and then gunzipped, for example:
gunzip ADOBEREADER_enu_8.1.1-1.SPARC.tar.gz Then untar it, for example: tar xvf ADOBEREADER_enu_8.1.1-1.SPARC.tar.gz and then install it by running the INSTALL script, for example: cd SSOLRS.install ./INSTALL For Solaris 8, Adobe Acrobat Reader is installed in $ECLPATH/tools/<machinetype>/acroread. For AIX: Adobe Acrobat Reader is installed in $ECLPATH/tools/<machinetype>/acroread. For Linux this is supplied as an rpm as root type rpm -i AdobeReader_enu-8.1.11.i386.rpm for Linux. Note Ensure that the path to the acroread executable is in the search path.
The next command is for a UNIX platform with Adobe Acrobat Reader and the ECLIPSE software suite and guide files installed. In GridSim, the command is entered on the Guide Setup panel, as follows: $ECLPATH/tools/<machinetype>/acroread $GUIDE_PATH/gridsim_ug.pdf where $GUIDE_PATH is specific to your machine. Hint $GUIDE_PATH is the path to where your copy of gridsim_ug.pdf is stored.
To view the manuals, run the script @pdf. This will display a bookcase from which any of the manuals may be selected for viewing. Hint The latest version of the Adobe Acrobat Reader for your platform can be downloaded from the Adobe website, at: http://www.adobe.com/products/acrobat/readstep.html. Selection of Include option for searching PDF files is very highly recommended. See the Adobe Acrobat Reader On-Line Help.
Grid menus
PDF versions of these are to be found either from the Bookshelf or in the directory ecl/2008.1/<machinetype>/grid/grid_charts. They are entitled PRIMARY_MENU_STRUCTURE.PDF and DISPLAY_MENU_STRUCTURE.PDF.
On-line help
The on-line documentation installed with 2008.1 is in HTML format and works by opening a web browser to view the HTML-formatted help files. The browser to be used is specified in the configuration file (/ecl/macros/CONFIG.ECL) in SECTION HELP. You should see that the keywords to enable the browser are set like this:
29
for example, for UNIX:

VIEWER BROWSER APPLICATION "/usr/bin/X11/netscape"
for PC:
VIEWER BROWSER APPLICATION "c:\program files\internet explorer\iexplore.exe"
The PC installation program will configure SECTION HELP according to the application associated with .html files installed on your PC. If you use Netscape on your PC the PC install program will detect this and set the APPLICATION accordingly. On UNIX it is always assumed that the application is "/usr/bin/X11/netscape". If this is not the location of the Netscape application then change the setting in the configuration file accordingly. Note Note that in the case of a heterogeneous installation, machines of different type may have Netscape installed in different locations. In this case ECL.CFA files may be used to point to the location on each machine.
Directory Structure
At the top level this looks like ecl/macros ecl/tools ecl/2008.1 The macros directory contains: macros for running the programs and utilities, for example @eclipse, @flogrid (see "Running the software" on page 35) macros called by the program, and utility macros, for example @check_chip which returns the chip type specific files used for configuration purposes; in particular @eclrc and CONFIG.ECL files used for monitoring license usage, for example flex.log.
The tools directory contains subdirectories for each machine type; each subdirectory contains: a number of subdirectories corresponding to various utilities such as convert and expand directories containing Acrobat. a bin directory containing subdirectories for each machine type; each subdirectory contains executables. a lib directory containing subdirectories for each machine type; each subdirectory contains shared objects. a number of directories corresponding to the various programs, such as eclipse, flogrid, etc., containing data, tutorials and documentation. a number of directories containing utilities and building blocks, for example manuals contains the manuals bookshelf rele_nt contains the release notes
The 2008.1 directory contains:
The resource directory which contains resources shared by several programs.
ECLIPSE Suite EMail:cadserv21@hotmail.com 2008.1 Simulation Software installation www.cadfamily.com Installation Guide Directory Structure The document is for study only,if tort to your rights,please inform us,we will delete
31
2008.1 EMail:cadserv21@hotmail.com ECLIPSE Suite Installation Guide www.cadfamily.com Simulation Software installation 32 Directory Structure The document is for study only,if tort to your rights,please inform us,we will delete
Licensing Chapter 3
Installing Schlumberger Licensing

To run ECLIPSE Suite you need a valid license configured. You can either connect to an already existing license server, or you can configure the license on your local machine either as a Standalone solution or as a license server. This section describes how you install FLEXnet 11.3 and configure your license. 1 2 First launch Schlumberger Licensing installer from the ECLIPSE DVD. Click on Install Products then Install SLB Licensing.
The Schlumberger FLEXlm installer starts. This installs all necessary utilities to configure licensing with FLEXnet 11.3, including standard FLEXnet utilities and the Schlumberger licensing tool. 3 4 Click Next to proceed. Click Change to choose another destination than the default.
If you have multiple license files that you need to run using the Schlumberger Licensing tool you should be aware of that there is a limitation in the length of the combined path to the license files. You should use a shorter installation path e.g. C:\SLBLicensing 5 Click Next and then Install to proceed For further information on the licensing utility please see the Installing Schlumberger Licensing user guide.
ECLIPSE Suite EMail:cadserv21@hotmail.com Licensing www.cadfamily.com Installation Guide Installing Schlumberger Licensing The document is for study only,if tort to your rights,please inform us,we will delete
33
Licensing ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 34 Installing Schlumberger Licensing The document is for study only,if tort to your rights,please inform us,we will delete
Running the software Chapter 4
UNIX systems - macros and scripts

For UNIX systems, the software should be run using scripts supplied in the macros directory. The following scripts are available to run the License Manager:
@flexstart @lmdown @lmhostid @lmreread @lmstat Start up the License Manager Shut down the License Manager Get FLEXlm hostid for the machine Reinitialize License Manager Check license status
The following files are also installed in the ecl/macros directory for use with the License Manager:
license.dat flex.log License file Activity log for License Manager
The following macros are available to run the principal simulator software programs (those marked * are no longer released):
@datacheck * @e300 @e500 * @eclipse @flogrid @frontsim @floviz @graf @grid @gridsim Run ECLIPSE simulator in datachecking mode only (using a datacheck license) Compositional simulator Thermal simulator Black oil simulator Automatic upscaling and grid generation Streamline simulator Visualization in 3D Post processor Gridding and mapping Visualization in 3D for streamline simulator
ECLIPSE Suite EMail:cadserv21@hotmail.com Running the software www.cadfamily.com Installation Guide UNIX systems - macros and scripts The document is for study only,if tort to your rights,please inform us,we will delete
35
@mpieclipse @mpie300 @office @pvti @r2sl @scal @schedule @simopt @vfpi @weltest*
Run ECLIPSE 100 simulator in parallel mode Run ECLIPSE 300 simulator in parallel mode ECLIPSE Office simulation pre- and post-processor PVT analysis Simulator controller Core sample analysis Well production analysis Simulator optimization of history match Interactive VFP table generation Well testing analysis.
The following macros are available to run the utility programs (those marked * are no longer released): Batch operations:
Corner point geometry generation Batch VFP table generation
@fill @vfp *
File format conversions:

Converts formatted / unformatted ECLIPSE output Converts between .GRID and .EGRID formats Converts ASCII from MS-DOS to UNIX format Create AVS file from ECLIPSE output Ghostscript: convert PostScript files to other print formats Converts Textfile to PostScript Pseudo generation Converts from older versions to RESCUE Version 19 format Convert ASCII from UNIX to MS-DOS format Create AVS file from VIP output
@convert @convertgrid @dos2unix @ecl2avs * @gs @postp @pseudo @rescueconvert @unix2dos @vip2avs *
File manipulation:
Merge INCLUDE files into master file Extract subset of data from ECLIPSE output Checks the contents of a Stratamodel binary .glk file
@expand @extract @glkread
File name changes:

Changes prefix of file name Changes suffix of file name Lowercase file name Change ECLIPSE filename case and extensions Uppercase file name
@change_prefix @change_suffix @lower @rename @upper
Configuration:
Configure Geonet to run ECLIPSE software Run and configure Parallel Virtual Machine daemon Configure a digitizer
@geonet_startup @pvm* @testdig
Running the software ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 36 UNIX systems - macros and scripts The document is for study only,if tort to your rights,please inform us,we will delete
Viewing:
Ghostview: view and navigate PostScript files via X11 interface Launches Manuals bookshelf Launches Adobe Acrobat Visualization in 3D
@gv @manuals @pdf @rtview *
Macros: command line flags

The UNIX macros are written using c-shell scripts. It is recommended that the macros directory is placed on the users path; this is not necessary, however, to ensure their successful execution. The macros will automatically detect all versions of software installed, and will invoke questions as necessary to launch the program required. The macros require little or no configuration to launch interactive products. However, it is possible to configure the macros using command line flags; this is especially useful for running the ECLIPSE simulators. The main command line flags for running the ECLIPSE 100 and ECLIPSE 300 simulators are listed below:
-data /home/user/workarea -file <filename> -help -second <Title> -fore or -foreground or -fg -back or -batch -priority -ver or -vers or -version -proc or -procs or -processors -local to set default working directory, or other directory. to define a dataset file name. to obtain a list of available flags with brief description. to define a secondary run title. <Title> should be enclosed in quotes. defines a foreground run (the default) defines a background (queued) run defines priority of a background run defines version of software to run, for example: -ver 2005a _1 -file TESTCASE defines number of processors for a Parallel run. uses the local configuration file ECL.CFG.
For Parallel ECLIPSE, namely @mpieclipse, @mpie300 the following special options are available:
-hostfile hosts.txt -machinefile hosts.txt -lsf Configuration file for Parallel run (same as -machinefile) Configuration file for Parallel run (same as -hostfile) For runs using LSF.
See "Using LSF with the simulator macros" on page 50.

-gigabit -scali Option for processing parallel jobs using Ethernet Gigabit. Option for processing parallel jobs using Scali.
If -procs is not set, the macro will attempt to read the PARALLEL keyword in the dataset to get the number of processors.
-sp2switch Specify type of SP2 switch
ECLIPSE Suite EMail:cadserv21@hotmail.com Running the software www.cadfamily.com Installation Guide UNIX systems - macros and scripts The document is for study only,if tort to your rights,please inform us,we will delete
37
IBM systems only. Default is us, alternative is ip.

-nolocal Do not run on front end
Examples
@eclipse -version 2008.1 -local -lsf TESTCASE @mpie300 -lsf -lsfqueue normal -version 2008.1 -local TESTCASE
Submitting batch jobs

The ECLIPSE simulators are batch programs, and for many users it is desirable to use a batch queuing system to submit jobs. The following describes how batch queues may be invoked using the macros. Table 4.1 User Scenario
Single user, single license, single CPU
Invoking batch queues using macros Batch Submission

Sequence batch jobs in foreground using a script to control process order. For example, create a script as follows: #!/bin/sh @eclipse -file CASE1 > CASE1.LOG 2> CASE1.ERR @eclipse -file CASE2 > CASE2.LOG 2> CASE2.ERR @eclipse -file CASE3 > CASE3.LOG 2> CASE3.ERR ...
1-3 users, multiple licenses, Submit jobs in background. Modify @check_args and set ECLNJOBS software installed on a to maximum number of eclipse licenses available. single system which may be shared across network Multiple users, multiple licenses, software installed on multiple CPUs across network System using job queues Submit jobs in background. Modify @check_args and set ECLNJOBS to maximum number of eclipse licenses available. Also modify launch macros (@eclipse, @e300) and set flex_queues=TRUE. Submit jobs in background. Modify @check_args and set ECLNJOBS to maximum number of eclipse licenses available. Modify launch macros (@eclipse, @e300) and set use_queues=TRUE.
Running the software ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 38 UNIX systems - macros and scripts The document is for study only,if tort to your rights,please inform us,we will delete
PC systems - macros and launcher

For PC systems, the software can be launched using the ECLIPSE launcher which is installed as a program folder. It is possible to run the software by opening a command prompt and running the appropriate script from the list below.
The following macros are available to run the principal simulator software programs (those marked * are no longer released):
$datacheck * $e300 $eclipse $flogrid $frontsim $floviz $graf $grid $gridsim $mpieclipse $mpie300 $office $pvti @r2sl $scal $schedule $simopt $vfpi $weltest* Run ECLIPSE simulator in data checking mode only (using a datacheck license) Compositional simulator Black oil simulator Automatic upscaling and grid generation Streamline simulator Visualization in 3D Post processor Gridding and mapping Visualization in 3D for streamline simulator Run ECLIPSE 100 simulator in parallel mode Run ECLIPSE 300 simulator in parallel mode ECLIPSE Office simulation pre- and post-processor PVT analysis Simulator controller Core sample analysis Well production analysis Simulator optimization of history match Interactive VFP table generation Well testing analysis.
The following macros are available to run the utility programs:

$convert $convertgrid $expand $extract $fill $glkread $postp $pseudo $pvm* $rescueconvert Converts formatted / unformatted ECLIPSE output Converts between .GRID and .EGRID formats Merge INCLUDE files into master file Extract subset of data from ECLIPSE output Corner point geometry generation Checks the contents of a Stratamodel binary .glk file Converts Textfile to PostScript Pseudo generation Run and configure Parallel Virtual Machine daemon Converts from older versions to RESCUE version 19 format.
ECLIPSE Suite EMail:cadserv21@hotmail.com Running the software www.cadfamily.com Installation Guide PC systems - macros and launcher The document is for study only,if tort to your rights,please inform us,we will delete
39
It is advisable to call the help file before running a macro for the first time. All principal simulator software program macros (except for $flogrid) have arguments, at least
C:\>$<program> -help Syntax: $<program> [arguments...] where arguments are any of the following: -data directory directory containing data -help displays this information -local use config file in directory -over use master config file -second identifier run identifier -ver version run requested version of <program>
Simulators run the dataset named on the command line, for example: $eclipse TESTCASE or $eclipse -file TESTCASE Other useful options for submitting Simulation jobs:
-data /home/user/workarea -lsf -lsfqueue -local -override Set default working directory Submit job via LSF Default LSF queue (requires -lsf flag) Use a Local Config file, or copy this only if it does not exist Always copy the Config file
The arguments -version, -vers and -ver are interchangeable for simulators: -version 2008.1 -vers 2008.1 -ver 2008.1 to set version; for example, the syntax: $eclipse -ver 2008.1 -file TESTCASE runs ECLIPSE release 2008.1 on datafile TESTCASE. For Parallel ECLIPSE, $mpieclipse and $mpie300, there are further options:
C:\>$mpieclipse -help Syntax: $mpieclipse [arguments...] where arguments are any of the following: -data directory directory containing data -drive driveletter: drive to change to (eg F:) -file file_name i/p data file name -help displays this information -local use config file in directory -over use master config file -second identifier run identifier -ver version run requested version of Eclipse -procs NN set number of processors to NN -hostfile hosts.txt Set hostfile for MPIRUN (Needs full path)
Running the software ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 40 PC systems - macros and launcher The document is for study only,if tort to your rights,please inform us,we will delete
For FrontSim the arguments are:

C:\>$frontsim -help Syntax: $frontsim [arguments...] where arguments are any of the following: -data directory directory containing data -drive driveletter: drive to change to (eg F:) -file filename i/p data file name -fs_convert filenew convert old-syle filename to new-style filenew -help displays this information -local use config file in directory -over use master config file -ver version run requested version
Running ECLIPSE 100 or ECLIPSE 300 in batch on a PC

There are no provisions within the ECLIPSE launcher or the macros to set ECLIPSE to run in batch mode on a PC. To run ECLIPSE in batch on a PC, use Notepad or similar text-only editor to create a batch file, a file with extension .BAT, in the directory containing your datasets. For instance, if you want to run a number of ECLIPSE 100 datasets in batch, create a file called RUN.BAT containing the commands
CALL $eclipse -file CASE1 -ver 2008.1 CALL $eclipse -file CASE2 -ver 2008.1 CALL $eclipse -file CASE3 -ver 2008.1 etc
RUN.BAT should be in the same directory as CASE1.DATA, CASE2.DATA and CASE3.DATA. To start the runs, double-click on the file RUN.BAT in Windows Explorer.
ECLIPSE Suite EMail:cadserv21@hotmail.com Running the software www.cadfamily.com Installation Guide PC systems - macros and launcher The document is for study only,if tort to your rights,please inform us,we will delete
41
ECLIPSE 100 and ECLIPSE 300

Large models
Note On Sun machines there is usually a default shell limit of 2GB; to access more than 2GB the command unlimit must be used. On IBM machines we limit the allocatable memory using the bmaxdata link argument; this is set to 2 000 000 000 bytes which is slightly below 2 GB.
Reservoir Coupling and PVM

PVM is not available for Linux 64-bit. To run Reservoir Coupling with PVM on these platforms, force the use of 32-bit executables by setting
on Linux setenv CHIPLINUX xeon
Reservoir Coupling and MPI

From ECLIPSE version 2004A, it is possible to run Reservoir Coupling using MPI for message passing instead of PVM, assuming that MPI is installed. The dataset and keyword format are identical to PVM runs. Run ECLIPSE using @mpieclipse and give the number of processors required (1 for the master +1 for each extra slave process). A hostfile is also required. For example, @mpieclipse -procs 4 -hostfile host.txt RCMASTER runs the standard 3-slave RCMASTER.DATA.
Running the software ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 42 ECLIPSE 100 and ECLIPSE 300 The document is for study only,if tort to your rights,please inform us,we will delete
Parallel ECLIPSE on UNIX and Linux

Installing and configuring Parallel ECLIPSE
MPI versions of Parallel ECLIPSE 100 and ECLIPSE 300 are supplied for Sun, SGI, Linux, and XP.
Software requirements
The following software must be installed prior to installing Parallel ECLIPSE.
Software requirements for SUN

Operating system Solaris 8 or 10 is required To run Parallel ECLIPSE 100 and ECLIPSE 300 on Sun systems the Sun HPC software must also be installed. At least version 4 is required for Solaris. Version 5 of HCPC also works. This is licensed software and requires a FLEXlm license to run. Note this only works on Solaris 8. HPC does not install on Solaris 10. For Solaris executables you need to have Sun Studio 11 installed, or at least the runtime component. See www.sun.com. The following parameters may need to be set in the /etc/systems file in order to run the shared memory code:
shmsys:shminfo_shmmax=268435456 shmsys:shminfo_shmmin=200 shmsys:shminfo_shmmni=200 shmsys:shminfo_shmseg=200 lwp_default_stksize=16384
set set set set set
After setting these parameters the machine should be rebooted with the -r option, for example by using the command reboot -- -r Once the license is there it may be necessary to start the cre daemons with:
/etc/init.d/sunhpc.cre-master start /etc/init.d/sunhpc.cre-node start
The path to the TM commands is not normally set. You should include /opt/SUNWhpc/ bin and /opt/SUNWhpc/etc in your path. If error messages about no pools appear when using tmrun then run the following script. Having done that, stop the cre daemons in the order node - master (/etc/init.d/cre.node stop, /etc/init.d/sunhpc.cre-master stop) then restart them in reverse order (/etc/init.d/sunhpc.cre-master start,
ECLIPSE Suite EMail:cadserv21@hotmail.com Running the software www.cadfamily.com Installation Guide Parallel ECLIPSE on UNIX and Linux The document is for study only,if tort to your rights,please inform us,we will delete
43
/etc/init.d/sunhpc.cre.node start).
#!/usr/bin/csh #setenv PATH /opt/SUNWhpc/bin:/opt/SUNWhpc/etc:$PATH set nodes=mpinfo -N | awk {if($1!="NAME" && $1 != "sample@node") print $1;} echo $nodes mpadmin -c "partition create all" mpadmin -c "all set enabled" foreach i ($nodes) mpadmin -c "all set nodes + $i" end mpadmin -c "all queue create q1" mpadmin -c "all queue q1 set enabled" mpadmin -c "all queue q1 set running" mpadmin -c "all set default_queue = q1" mpadmin -c "all set batch_procs = 4" mpadmin -c "set default_interactive_partition = all"
Software requirements for Linux

Red Hat Enterprise Linux 4.0 Update 3 or later is required. MPI software is supplied with the ECLIPSE installation. This will be invoked by the ECLIPSE macros in preference to any native version of MPI. This is entirely transparent to the user and will not interfere with other versions of MPI.
Installation procedure
See "Installing Linux software from CD/DVD" on page 21.
Notes on setting up the OS for Parallel ECLIPSE

Sun
To install and set up HPC, please contact your Sun representative. The software (HPC 5) can be downloaded from http://www.sun.com/servers/hpc/software/tryandbuy.html if you are a registered SunSolve member For ECLIPSE on Sun, the following environmental parameters may be useful but are not generally recommended: - MPI_SHORTMSGSIZE 8000 - MPI_GLOBMEMSIZE - set according to problem size; this controls the size of the shared memory buffer
IBM Power 5 Linux based systems

For IBM Power5, to obtain maximum performance disable SMT. Edit /etc/yaboot.conf and add smt-enabled=off to the append keyword. See example below. Running the software ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 44 Parallel ECLIPSE on UNIX and Linux The document is for study only,if tort to your rights,please inform us,we will delete
root:/etc> cat yaboot.conf partition = 3 timeout = 100 default = linux image = /boot/vmlinux label = linux append = "root=/dev/sdf3 selinux=0 elevator=cfq smtenabled=off" initrd = /boot/initrd
Linux
MPI is set up automatically during the installation process as long as the installation is run on a Linux machine. If the Linux installation is run from another platform with cross-mounted disks the MPI setup will fail.
Notes on running Parallel ECLIPSE

Running Parallel ECLIPSE on Sun
To run ECLIPSE 100 and ECLIPSE 300 use the commands @mpieclipse and @mpie300 respectively.
Running Parallel ECLIPSE on Linux with MPICH

Note The following section is not required if you use the -scali option when running Parallel ECLIPSE.
In order to successfully run parallel ECLIPSE and ECLIPSE 300 on Linux, the .cshrc and .rhosts files will need alteration as below. Add the following to your .cshrc file in your home directory:
if(ùname` == "Linux") then # Set F_UFMTENDIAN=big for Big Endian file IO setenv F_UFMTENDIAN big if (! $?LD_LIBRARY_PATH ) then setenv LD_LIBRARY_PATH $ECLARCH/2008.1/lib/linux else setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH\:$ECLARCH/2008.1/lib/linux endif endif
Note that this is version-dependent; 2004A used $ECLARCH/2004a/lib/linux, which contains different libraries. It is not possible to run both parallel versions from the same setup.
45
You will need a .rhosts file in your home directory. This must mention each and every node of the Linux cluster explicitly as in the example below. You will need to add node names even if you already have the "catch all" entry of "+ +". The last entry is the front end machine of the Linux cluster. (You will need to change hkw to your own login id, and alter the last line to suit your local installation)
comp00.geoquest hkw comp01.geoquest hkw comp02.geoquest hkw comp03.geoquest hkw comp04.geoquest hkw comp05.geoquest hkw comp06.geoquest hkw comp07.geoquest hkw comp08.geoquest hkw comp09.geoquest hkw comp10.geoquest hkw comp11.geoquest hkw comp12.geoquest hkw comp13.geoquest hkw comp14.geoquest hkw comp15.geoquest hkw linux-cluster.abingdon.oilfield.slb.com
hkw
The .rhosts file should have +w access to you only, that is ls -l .rhosts should show permissions of -rw-r--r-- ; if it does not you can correct it with the command chmod 644 .rhosts.
Gigabit parallel on x86_64 systems

A further problem has been noted with the MPICH builds for x86_64 builds in that the Gigabit builds are trying to communicate between nodes using the Kerberos rsh (normally found in / usr/kerberos/bin/rsh). In many of the cases we have tried, particularly under SuSE, this directory or file does not exist or is not installed by default. The easiest solution here is to create the directory (mkdir -p /usr/kerberos/bin) and then create a link between rsh in that directory and the standard one (ln -s /usr/bin/rsh /usr/kerberos/bin/ rsh). This will have to be done as root on all nodes on the system.
Myrinet executables for Linux (32- and 64-bit)

Note This section only applies to 2004A and earlier versions.
On Linux, the parallel executables for Myrinet may be used if a Myrinet switch is available. See "Installing Myrinet drivers for Linux" on page 23. For running 64-bit Myrinet execs, the environmental variable ECL_MYRINET_LOC must be set to point to the Myrinet installation.
Running the software ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 46 Parallel ECLIPSE on UNIX and Linux The document is for study only,if tort to your rights,please inform us,we will delete
To run, use the -myrinet argument when running @mpieclipse or @mpie300; for example: @mpieclipse -myrinet PARALLEL to run the dataset PARALLEL.DATA. Alternatively, the environmental variable ECL_MYRINET may be set to TRUE in the user's environment: setenv ECL_MYRINET TRUE and run without the -myrinet argument, thus: @mpieclipse PARALLEL Note Sometimes you can get an error message when trying to run a job on a single node saying that there are not enough processors for machine type Linux. If this happens it is because the hostname of the machine is defined as fully qualified and the login within the mpirun command does not associate the short version of the hostname (without the domain name attached) with the full name. Currently the only known solution here is to change the machine name so as not to include the domain name.
SGI Altix executables for Linux 64-bit

If the macros detect that you are running on SGI Altix they will use the executable specifically optimized for that system. If the array software is not running on an Altix the macro will run the Ethernet version instead. Note With SGI Altix systems running ProPack 3 in order to run earlier releases of the software than 2004A, you may need to set the variable LD_PRELOAD to the value "/ usr/lib/sgi-compat-preload.so" using export or setenv depending on your default shell. This could also be set in @eclrc
Starting the array software

To switch on array services, if the array software is not already started it can be started using:
/sbin/chkconfig --list | grep array
If the array does not appear at all, do the following (ignore this step if the array is configured but not on):
more /etc/init.d/array
The top of file gives instructions:

/sbin/chkconfig --add array vi /etc/services add sgi-arrayd 5434/tcp /sbin/chkconfig --level 2345 array on /etc/init.d/array start
Special considerations for HP Itanium2 clusters

It may be necessary to increase P4_GLOBMEMSIZE, as follows:
setenv P4_GLOBMEMSIZE 200000000
47
Another setting you might want concerns shared memory (details below are supplied by HP). For the shared memory there are two parameters that control the size. These parameters can be modified without rebooting the machine: For example, for 4GB: echo 4194304 > /proc/sys/kernel/shmall echo 4194304000 > /proc/sys/kernel/shmmax These settings can also be made in the /etc/sysctl.conf file in order to make them available after a reboot. The following may also be required: $ more /etc/sysctl.conf # Disables packet forwarding net.ipv4.ip_forward = 0 # Enables source route verification net.ipv4.conf.default.rp_filter = 1 # Disables the magic-sysrq key kernel.sysrq = 0 kernel.shmmax=134000000 kernel.shmall=134000000
Increasing size of MPI memory Buffers

Occasionally ECLIPSE or ECLIPSE 300 can exceed the size of the default memory set in the MPI messaging, particularly with large problems. In order to increase this it is possible to use the PARAOPTS keyword in ECLIPSE, which should be set to:
PARAOPTS 2 * 100 /
The NSTACK parameter should also be set to a reasonable number (DEFAULT: 10).
Fast Restarts with Parallel ECLIPSE 100

ECLIPSE 100 supports fast restarts for parallel runs with the following precautions: 1 2 The restart run must use the same number of processors and the same domain split as the base run The @mpieclipse macro requires that the number of processors be specified explicitly on the command line using the -processors flag, for example: @mpieclipse -procs 2 RESTARTFILENAME ECLIPSE 300 does not support fast restarts in parallel.
Running Parallel ECLIPSE with queueing systems

It is generally advised to run both ECLIPSE and Parallel ECLIPSE using a commercial queuing system. Only where one user is using a machine is it possible to adequately use the machine in a profitable way. The main advantage of using Parallel ECLIPSE, which is speed, is lost if a machine is overloaded, as all parallel tasks will slow down. This usually results in run times longer than for serial ECLIPSE. Queuing systems will allow greater throughput of jobs by using the available resources more efficiently. Support for a commercial queuing system is available in the @eclipse, @e300, @mpieclipse and @mpie300 macros. The queuing systems is: LSF from Platform Computing - http://www.platform.com The support in the macro provides for a limited number of the total available options for this platform, allowing queuing for jobs that specify only the number of processors for each job submitted. Additional support is provided in this queuing system for supporting memory requirements, later start dates, specifying groups of machines to execute on, etc. However, the macros provide a common route to queuing on these systems.
Running ECLIPSE Software with LSF

ECLIPSE 100, ECLIPSE 300, Parallel ECLIPSE, Parallel ECLIPSE 300, ECLIPSE Office and FrontSim may all be run with LSF, using the standard simulator macros.
Mixed UNIX and Windows network

LSF 7 or later is recommended. LSF requires that the file name space is uniform across all machines. LSF requires that uniform name spaces and ID spaces exist on all hosts; that is, a job submitted by a given user will run under the same user's account on the execution host. For situations where non-uniform user ID/user name space exists, account mapping must be used to determine the account used to run a job. On PCs, UNC (Uniform/Universal Naming Convention) paths must be used. For example:
\\nt-eclipse3\F\vanilla\2006.2\eclipse\source\eclipse.exe
It is recommended that disks containing ECLIPSE software and data be cross-mounted on all machines in the LSF cluster.
LSF SIS Integration kit

This kit: requires on-site configuration of LSF - refer to the integration kit documentation. provides a dynamic method of license checking against the Resource requirement. FLEXlm is queried for licenses using an elim (External Load Information Manager), provided by Platform. The integration kit can be found on DVD 1 under the 3rdparty\LSF\resources directory.
If the resources can be met, the job runs; otherwise, LSF monitors the resources until they are met. ECLIPSE Suite EMail:cadserv21@hotmail.com Running the software www.cadfamily.com Installation Guide Parallel ECLIPSE on UNIX and Linux The document is for study only,if tort to your rights,please inform us,we will delete
49
Setup
The following environmental variables must be set: ECL_LSF set true if LSF is installed If this and ECL_LSF are set to TRUE then jobs are submitted using LSF without the need for the -lsf flag. For compatibility with ECLIPSE Office the -nolsf flag has been added as a new option to stop nested bsub commands. ECL_LSF_PARALLELQ defines the default queues for parallel jobs ECL_LSF_SERIALQ defines the default queues for serial jobs ECL_MYRINET (Linux only) defines Myrinet executables as the default. This was only a requirement until 2004A. The default is now defined as Myrinet by default without ECL_MYRINET being set. ECL_LSF_LICCHECK set if LSF is to control FLEXlm licensing and the LSF-SIS integration kit has been installed (contact Platform Computing www.platform.com for details). In addition, the following must be added to the user's .cshrc file: if (-d /lsf/conf) then source /lsf/conf/cshrc.lsf endif This assumes that LSF has been installed in directory /lsf; otherwise, amend as appropriate.
ECL_LSF_BYDEFAULT
Using LSF with the simulator macros

The use of LSF is triggered by adding the flag -lsf. This is ignored unless ECL_LSF is true.
Examples
for serial jobs: @eclipse -lsf SPE9 @e300 -lsf CASE1 @frontsim -lsf ECL_SAMPLE01 for parallel jobs @mpieclipse -lsf 50X50X6 @mpie300 -lsf 20X20X6 The macros create a temporary job file ecl.tmp.<datestamp> that is used by LSF's bsub. The appropriate "resources" are generated by LSF.
Myrinet parallel executables (Linux)

On Linux prior to 2004A_1 the parallel executables for Myrinet may be used. Either set the environmental variable ECL_MYRINET to TRUE and run as above, or use the -myrinet flag.
Examples
with ECL_MYRINET set to TRUE @mpieclipse -lsf 50X50X6 @mpie300 -lsf 20X20X6 without ECL_MYRINET set @mpieclipse -lsf -myrinet 50X50X6 @mpie300 -lsf -myrinet 20X20X6
Scali parallel executables (Linux)

On Linux, the parallel executables for Scali may be used. Post 2004A_1 the use of the Scali MPI is the only way to access the fast interconnects (Myrinet/Infniband) To use Scali, if Scali is not installed in the default location (/opt/scali), you need to set the environment variable ECL_SCALI_LOC to the location where Scali is installed. To run using scali use the -scali flag. @mpieclipse -lsf -scali 50X50X6 @mpie300 -lsf -scali 20X20X6
LSF Queues
If no queue is defined, a list is presented to the user, unless default queues are defined with ECL_LSF_SERIALQ or ECL_LSF_PARALLELQ. A queue can be defined with @eclipse -lsf lsfqueue <qname> If no queue is defined, the user is asked which to use. LSF queues are defined in lsb.queues.
51
Example
Running Parallel ECLIPSE 100 on a Machine type linux Local config file ECL.CFG exists. OK to use ('n' deletes local file) (Y/n)?: number of processors required is = 2 using LSF queuing Available lsf queues are: 1) night 2) normal 3) parallel Please select queue 1 - 3 : 3 Job <4112> is submitted to queue <parallel>. linux-cluster{hkw}[257]: bjobs JOBID USER STAT QUEUE FROM_HOST EXEC_HOST 4112 hkw PEND parallel linux-clust
JOB_NAME SUBMIT_TIME *_2.225609 May 28 13:58
Example queue
Begin Queue QUEUE_NAME PRIORITY NICE QJOB_LIMIT RERUNNABLE REQUEUE_EXIT_VALUES HOSTS End Queue = = = = = = = eclipse_parallel 30 # 100 is highest 0 # UNIX nice command 1 # 1 job at a time yes # automatic re-queue if job fails 3 # log file shows values comp00 comp01 comp02 comp03 comp04 comp05
Checking a job's progress with bjobs

The command bjobs can be used to show the status of all the user's jobs. bjob <jobID> shows the status of a specific job, for example: PEND, RUN, SUSPENDED, FAILED, DONE bjobs communicates with the LSF daemons, so if it is overused it can slow the system down. bhist -l <jobID> as it reports from the event queue.
It is better to use
Checking a jobs progress

linux-cluster{hkw}[204]: bjobs 3408 JOBID USER STAT QUEUE FROM_HOST 3408 saf RUN normal linux-clust linux-cluster{hkw}[205]: bjobs 3414 JOBID USER STAT QUEUE FROM_HOST 3414 grb RUN parallel linux-clust EXEC_HOST JOB_NAME SUBMIT_TIME comp00.geoq *K2.175640 May 22 08:59 comp05.geoquest EXEC_HOST JOB_NAME comp06.geoq T comp09.geoquest comp02.geoquest comp01.geoquest SUBMIT_TIME May 22 13:51
linux-cluster{hkw}[206]:
xlsbatch can be used to show a summary of all jobs running through the queues:
Figure 4.1 LSF Batch console display
8 hosts
2 hosts 1 host 4 hosts
Total = 15 hosts
3 Queues
xlsmon can be used to show the performance of the LSF cluster:
53
Figure 4.2 LSF - xlsmon, View | Detailed Load
Notes
1 Some clusters will run a process on the front-end machine by default. To avoid this, use the -nolocal argument, for example @mpieclipse -nolocal -hostfile host.txt SPE9 2 There is also a -local argument which means use the local configuration file ECL.CFG. It is not the opposite of -nolocal. Thus, @mpieclipse -local -nolocal -hostfile host.txt SPE9 is quite valid and makes sense. 3 IBM machines without a fast switch (non-SP machines) may need to use IP (Internet Protocol) instead of US (User Space). To specify IP, use the -sp2switch argument: @mpieclipse -sp2switch ip -hostfile host.txt SPE9 4 Hostfile formats. The standard hostfile format is of the form Node01 Node02
Node03 Node04 This will run a process on each node in turn. In the case of nodes with twin CPUs, to specify that a process is to be run on each CPU, use a hostfile of the form Node01 Node01 Node02 Node02
55
Parallel ECLIPSE on PC
Parallel ECLIPSE should be executed from the ECLIPSE Launcher. Click on the Parallel ECLIPSE (or Parallel E300) button to open the Parallel ECLIPSE (or Parallel E300) launcher. This is similar to the serial ECLIPSE launcher but has two extra boxes for detailing the number of processors and the nodes to run on. Click on the dropdown in the Processors box to select the number of processors; this must be identical to the number of processors set in the dataset. A list of nodes must be provided; click on the Edit with notepad button in the Nodes box and enter the nodes you wish to run on. Save the file. This need only be done at the start. Select the dataset to be run and click on the run button.
Notes
Refer to "Installing MPI/Pro" on page 17. For distributed PCs, the software installation must be located on the same path for each PC (including the drive letter). The remote PCs need to have their disks shared to the controlling PC. The LM_LICENSE_FILE variable must be set in the users environment. Ensure the configuration file is copied to the working directory on the controlling PC before submitting the run. Parallel ECLIPSE on distributed PCs has been successfully tested on machines all running either Windows 2000 or Windows XP. There is a major caveat here though, in that although it is technically possible to run ECLIPSE/ECLIPSE 300 in parallel on a PC cluster this is not recommended in a production environment because of stability issues with Windows. For Windows CSS see "Microsoft CSS Installation" on page 59.
Running the software ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 56 Parallel ECLIPSE on PC The document is for study only,if tort to your rights,please inform us,we will delete
3D Stereo options
From 2004A the ECLIPSE software suite changed from using from using AVS to using OpenInventor to implement the 3D windows. OpenInventor uses different ways of implementing stereo compared to AVS. In order to use the stereo option the following environmental variable must be set. In most cases this will be the RAW option. Note In UNIX this should be set in the @eclrc macro using setenv. On the PC it is probably best set as a system environment variable.
Setting the desired stereo mode

Various different stereo modes exist to suit the available hardware. To define the stereo mode, set the OIV_STEREO_TYPE environment variable. Each view is rendered using the given colors. Note that these modes require red/green glasses. ANAGLYPH_RED_CYAN (default) ANAGLYPH_GREEN_MAGENTA ANAGLYPH_BLUE_YELLOW
These modes are for systems employing mirror glasses (that show one half of the screen to one eye and the other half to the other eye) HALF_SCREEN_OVERUNDER_FILL HALF_SCREEN_OVERUNDER HALF_SCREEN_SIDEBYSIDE_FILL HALF_SCREEN_SIDEBYSIDE INTERLACED_HORIZONTAL_BEST INTERLACED_VERTICAL_BEST INTERLACED_HORIZONTAL_FAST INTERLACED_VERTICAL_FAST RAW Note that RAW uses OpenGL stereo, and requires your graphics card to support quad buffered stereo.
For systems using light polarizing glasses:
Note
ECLIPSE Suite EMail:cadserv21@hotmail.com Running the software www.cadfamily.com Installation Guide 3D Stereo options The document is for study only,if tort to your rights,please inform us,we will delete
57
Solaris graphics configuration options

There have been some issues with running the 2006.1 interactive pre/post products on Sun Solaris-based systems. These appear to be due to the color depth settings. They can be configured in the /etc/dt/config/Xservers file. (Note that this file may also be in / usr/dt/config but it is suggested that it is moved to the above directory before modifying.) An example of what the file should look like is:
:0 Local local_uid@console root /usr/openwin/bin/X -dev /dev/fbs/ifb0 defdepth 24 -dev /dev/fbs/ffb0 defdepth 24
Note that this is for a dual-screen system with an Expert3D card and a Creator3D card.
Running the software ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 58 Solaris graphics configuration options The document is for study only,if tort to your rights,please inform us,we will delete
Microsoft CSS Installation Chapter 5
Installation
This document assumes that you have access to an existing fully operational and correctly configured Microsoft Windows Compute Cluster Server 2003 SP1 environment. Warning This document is intended as a guide only. Always refer to the comprehensive documentation and release notes supplied with your Microsoft Windows Compute Cluster Server 2003 installation disks to help you to properly install and use this product.
To submit jobs remotely to the cluster from your PC running Windows XP Professional, you must first install the Microsoft Windows Compute Cluster Server 2003 Job Manager Client utility. 1 2 Insert the Compute Cluster Pack x64 CD. If it does not auto-run then launch setup.exe. Accept the licensing agreement, then click Next and choose the Install client utilities only option from the following screen.
ECLIPSE Suite EMail:cadserv21@hotmail.com Microsoft CSS Installation www.cadfamily.com Installation Guide Installation The document is for study only,if tort to your rights,please inform us,we will delete
59
Figure 5.1 CSS Installation Type
Click Next, and either: accept the default installation path, or change it to one of your choice.
You will then see the following screen:
Microsoft CSS Installation ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 60 Installation The document is for study only,if tort to your rights,please inform us,we will delete
Figure 5.2 Required components
During setup, additional components will need to be installed before the Compute Cluster pack is installed. They are: Microsoft .NET Framework 2.0 MMC 3.0
The installation binaries for .NET Framework 2.0 are included on the installation CD. All you need do is highlight Microsoft .NET Framework and click the Install button. When finished, the installation will automatically reboot your machine without prompting; you will therefore need to ensure you have no unsaved files, and you must then run setup again to download and install the MMC 3.0 component.
Note
Microsoft Management Console installation

The Microsoft Management Console (MMC 3.0) installation requires you to be connected to the internet in order to install it. 1 Clicking on the Install button should automatically launch your browser and connect you to the Microsoft website, from where you will need to download and then run the MMC 3.0 WindowsServer2003-KB907265-x86-ENU.exe package. Once these installations are complete, highlight Microsoft Compute Cluster Pack then click the Install button.
61
Finally, click Finish.
Creating the CCP Scheduler

1 Before launching the Job Manager, create a new system environment variable called CCP_SCHEDULER by opening Control Panel > System > Advanced > Environment Variables. The value will be the server name of your Windows cluster head node. After the installation has finished, launch the Job Manager using Start > Programs > Microsoft Compute Cluster Pack > 3 . You will be prompted for the name of the cluster that you wish to connect to. Select Another computer and insert the server name of your Windows cluster head node. The Job Queue window will then open.
Figure 5.3 The Job Queue Window
Note
The supported Microsoft method for job submission is to use the Job Manager. It is also possible to submit jobs via the command line using the command line interface (CLI), which is not covered here. The templates are based upon XML script.
Submitting jobs
1 To use an existing template, select File > Submit Job with Template and browse to the location of your templates. You can set a default location for your templates directory by selecting File > Options and insert a UNC path to their location if they are on a remote server, for example: \\servername\sharename\templates. Mapped drives can also be used, and providing your templates are in that location the job manager will automatically load the templates from the location you have specified.
Note
You can modify existing templates to create your own custom templates; example templates are included with the ECLIPSE 2006.2 installation disks on CD 9\PC\resource\CCS_templates. Unzip Eclipse_job_templates.zip to the templates folder that you have chosen.
2 3 4
To create your own template, click File > Submit Job. Specify values such as Job and Project name. Also set the job priority if required in the General tab. The Processors tab is where you set the minimum and maximum number of processors you will need to run your job. You can also set an estimated run time for this job and force your job to run until the end of time or until cancelled. In practice you probably will not need to do this.
Figure 5.4 Tasks pane
The Tasks tab allows you to specify the command arguments that will be used to run your job. Ignore the Licenses tab as it does not work with FlexLM licensing.
Warning
63
Use the Advanced tab to choose specific nodes on which to run your job. Setting default value Use any available nodes allows the Job Manager to automatically assign compute nodes to the job. Click the Tasks tab and build your command string in the Command Line field, then click Add.
An example of an ECLIPSE 100 command string can be: mpiexec -env F_UFMTENDIAN big -env LM_License_File 1700@license_server eclipse_msmpi parallel where: mpiexec is the Microsoft MPI executable -env is used to define environment variables and their corresponding values F_UFMTENDIAN is an environment variable big is the value of the environment variable eclipse_msmpi is the 64 bit parallel ECLIPSE 100 executable parallel is the name of your dataset and is usually of the form filename.dat. You do not need to specify file extensions for executables or datasets. You will need to specify the F_UFMTENDIAN variable with a value of big, otherwise the job will not run.
Note
As you will have already specified the number of processors required in the Processors tab, ensure the Use jobs allocated processors box is checked so that you do not have to specify the number of processors again.
Task properties
1 2 3 Once you have added your command string and arguments, click the Edit button. Open the Task Properties window where you define Standard Output file, Standard Error file and Work Directory. Here you must specify the directory locations as an explicit UNC path, not mapped drives.
Figure 5.5 Task Properties
A successful run will write output to the Standard Output file you define. Any errors will be written to the Standard Error file as defined in your template. The Work directory will contain your datasets and all output files generated during the ECLIPSE run. Note You can keep the ECLIPSE executables in a directory outside the specified work directory, but it must be defined by a UNC path in the command string and not a mapped drive, as shown by this example:
mpiexec -env F_UFMTENDIAN big -env LM_License_File 1700@license_server \\servername\ecl\executables\eclipse_msmpi DATA

4 5 Click OK to exit from the Task Properties windows. Click the Save As Template... button to save it to your preferred template directory.
Submitting a job
When your template is finished, run your job by clicking the Submit button. You will be prompted for a domain username and password, which you will need to enter before your job will run. You will then see the status of the job in the job queue window.
65
Figure 5.6 Job Queue
The queuing window does not tell you which nodes have been assigned to run your job. You can, however, find this out by opening a command window and issuing the following commands: job list: displays all running jobs and their job IDs job view XX (where XX is the job ID number): displays information about a job with ID XX; for example allocated nodes, status (Running, Finished or Failed), etc. The installation procedure outlined in this guide must be conducted using an account with local administrative privileges. You will also need permission to able to submit jobs to the cluster, and your systems administrator should be able to help with this. If you are the systems administrator, add domain user accounts to the cluster using the Compute Cluster Admin tool.
Note
Additional information
The following website links may also be of interest: http://windowshpc.net/ http://technet2.microsoft.com/WindowsServer/en/library/4fb21c96-759c-493a-bb29f14bd491160d1033.mspx?mfr=true
Non-PVM remote and external job options
Appendix A
Using the Non-PVM remote option

The Non-PVM (Parallel Virtual Machine) remote option for running the simulators from ECLIPSE Office and SimOpt now allows the user to submit jobs from a PC (Windows NT, 2000 or XP) to the local network environment. The requirements for getting such submissions to work are detailed below.
Running from a PC to a UNIX machine using NonPVM remote

Configuration
There are several things that must be done to ensure that the ECLIPSE simulator can be run on a remote host.
On the remote host:

1 2 3 Check that your login shell is a C-shell. Check that you can execute ECLIPSE on the remote host by typing the @eclipse command. Create or update the .rhosts file in your home directory. Either add + + to allow access to all machines on the local network or insert your login and the name of the specific machine you wish to allow access. Make sure that no version of PVM is running on the remote machine.
ECLIPSE Suite EMail:cadserv21@hotmail.com Non-PVM remote and external job options www.cadfamily.com Installation Guide Using the Non-PVM remote option The document is for study only,if tort to your rights,please inform us,we will delete
67
On the local host:

1 It is strongly recommended that the user have the same logon on both the local and remote machines. However, if the user has a different logon on the remote host the following changes must be made to the Win.ini file:
[RCMD] User=test [RCP] User=test
If this appeared in Win.ini, the local user name would be test and WinsockRCP and WinsockRCMD will use this name at the remote host. Caution Making these changes on Windows 98 machines may cause serious problems and is therefore not encouraged.
The user no longer needs an office.ini file on the local machine.
Using the non-PVM remote option in ECLIPSE Office

In order to use the Non-PVM remote option in ECLIPSE Office: 1 2 3 Open the Run Manager Select NON-PVM REMOTE from the list of possible Environments Choose Options | Run Environment and specify the name of the remote host, the temporary host path, any additional simulation parameters (for example, -ver 2006.1), and whether you wish to remove files from the remote host The temporary host path is the name of the directory where ECLIPSE Office will copy all the data necessary for the simulation run. The user must have write permission in this directory. If Remove remote host files is chosen then all the data and results for the simulation will be deleted from the remote host after the transfer back to the local machine.
Note
Choose Submit | Runs to set the simulation running on the remote machine
Using the Non-PVM remote option in SimOpt

1 2 Choose Options | Simulation from the main SimOpt panel. In the Simulation Options panel, a b c d 3 Select NON-PVM REMOTE from the list of possible environments Enter the name of the remote host Specify the version of ECLIPSE to run on the remote machine in the simulation parameters box. (for example, add -ver 2006.1) Make sure the temporary host path is set correctly and that the user has the necessary permission in this directory
Apply the changes in the Simulation Options panel.
Non-PVM remote and external job options ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 68 Using the Non-PVM remote option The document is for study only,if tort to your rights,please inform us,we will delete
Choose Match | Simulate and the new run environment options should be reflected in the Simulation Control panel.
Limitations
In the current release the following limitation has been noted: 1 It is not possible to use run-time monitoring with the Non-PVM remote option.
ECLIPSE Suite EMail:cadserv21@hotmail.com Non-PVM remote and external job options www.cadfamily.com Installation Guide Using the Non-PVM remote option The document is for study only,if tort to your rights,please inform us,we will delete
69
Using the external job option

The external job option for running the simulators from ECLIPSE Office and SimOpt provides open access to tailor the submitted job to the local network environment. This document provides example scenarios for typical environments. It is important to remember that local conditions must be taken into consideration when setting up such jobs.
Non-PVM remote and external job options ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 70 Using the external job option The document is for study only,if tort to your rights,please inform us,we will delete
Running from a PC to a UNIX machine

This section describes a set-up for running the pre- and post- processors on a PC and submitting the ECLIPSE 100 jobs to a UNIX machine using NFS drives and dos2unix.
Requirements
1 The directory on the UNIX machine must be mapped to an NFS network drive on the PC, so that the same physical disk space is used by both the PC applications and the UNIX simulators. The PC must have rsh.exe.
Method
Writing a DOS *.bat file
The next step is to write a DOS *.bat file to handle the arguments that ECLIPSE Office or SimOpt sends to it. As default, the following command is sent by ECLIPSE Office or SimOpt: batch_file.bat -data \\full\path\on\PC -file PROJECTNAME_E100 Where: \\full\path\on\PC is the full path to the working directory on the PC. PROJECTNAME_E100 is the name of the ECLIPSE 100 data-set to be run.
In this example it is assumed that the working directory is shared as an NFS network drive, so the -path parameter can be discarded. However, the script will need to know the name of the machine, so a -machine parameter must be recognized. The following PC *.bat file parses the values ECLIPSE Office sends and generates the correct remote shell (rsh) command to execute the run:
@echo off REM REM NAME: REM $jobonunix.bat REM REM PURPOSE: REM Submits jobs to UNIX machine from a PC running Office REM via the "External Job" option REM
ECLIPSE Suite EMail:cadserv21@hotmail.com Non-PVM remote and external job options www.cadfamily.com Installation Guide Running from a PC to a UNIX machine The document is for study only,if tort to your rights,please inform us,we will delete
71
REM HOW TO RUN: REM Set the run-type to "External Job" and use the -machine REM parameter to give the machine name REM Set-up the UNIX filespace as an NFS drive on the PC REM Write the Eclipse files to the UNIX filespace REM NOTE: This script requires the presence of dos2unix REM on the UNIX machine REM REM FLAGS: REM The following flags are accepted as arguments: REM -file the Eclipse data file REM -ver the version of Eclipse (e.g. 99a_1) REM -machine the UNIX machine name REM NOTE: All other flags are read but then ignored REM NOTE: Office writes out -ver and -file as default REM so you only need to add -machine REM REM STRUCTURE: REM This script is effectively composed of 2 parts: REM 1. SWITCH statement block - this performs an equivalent REM job to "switch" in C or Java. It parses the command REM line arguments. REM 2. execution block - this submits the job on the REM UNIX machine REM (after converting the files using dos2unix) REM ===================================== REM Start of SWITCH block REM ===================================== REM Loop around all passed arguments :ChkArgs if "%1"=="" goto AllChkd REM check for -machine if "%1"=="-machine" goto Machine if "%1"=="-MACHINE" goto Machine goto NotMachine :Machine shift if NOT "%1"=="" set machine=%1 shift goto ChkArgs :NotMachine REM check for -ver if "%1"=="-ver" goto Version if "%1"=="-VER" goto Version goto NotVersion :Version shift if NOT "%1"=="" set version=%1 shift goto ChkArgs :NotVersion REM check for -file if "%1"=="-file" goto File
Non-PVM remote and external job options ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 72 Running from a PC to a UNIX machine The document is for study only,if tort to your rights,please inform us,we will delete
if "%1"=="-FILE" goto File goto NotFile :File shift if NOT "%1"=="" set file=%1 shift goto ChkArgs :NotFile REM Cover ourselves by handling any unexpected arguments REM by ignoring them - they are put to into the ignore variable set ignore=%1 shift goto ChkArgs REM REM All arguments handled REM :AllChkd REM ===================================== REM End of SWITCH block REM ===================================== REM ===================================== REM Start of execution block REM ===================================== rsh %machine% @eclipse -ver %version% %file% exit REM ======= ============================== REM End of execution block REM =====================================
Running the job

The final step is to set up ECLIPSE Office or SimOpt to run the job.
ECLIPSE Office
The following steps will set the Run Manager in ECLIPSE Office to execute the script: 1 2 3 4 5 In the Run Manager set the Environment to External Job Run Manager: Options | Run Environment... Set the Executable to your script name (for example $jobonunix.bat) Set the Simulator Parameters to the include the machine name and the version (for example -machine myunixbox -ver 2006.1). Now run simulations as usual.
SimOpt
The following steps will set allow SimOpt to execute the script: 1 2 3 SimOpt: Options | Simulation... In the Simulation Options Panel set the Environment to EXTERNAL JOB. Set the Simulator to execute to the name of the script (for example $jobonunix.bat).
ECLIPSE Suite EMail:cadserv21@hotmail.com Non-PVM remote and external job options www.cadfamily.com Installation Guide Running from a PC to a UNIX machine The document is for study only,if tort to your rights,please inform us,we will delete
73
4 5 6
Set the Simulator Parameters to include the machine name and the version (for example -machine myunixbox -ver 2006.1). Click OK in the Simulation Options Panel. Now run simulations from the Simulation Control Panel as usual. If you run with non-unified output, ECLIPSE Office and SimOpt can provide run-time monitoring via the summary vectors.
Hint
Non-PVM remote and external job options ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 74 Running from a PC to a UNIX machine The document is for study only,if tort to your rights,please inform us,we will delete
R2SL Appendix B
PC Configuration
This appendix contains useful troubleshooting information for running R2SL on PC. 1 In order to run R2SL, your machine should have the following installed and properly licensed: a b c d 2 R2SL 2008.1 or higher ECLIPSE 100, ECLIPSE 300 PIPESIM 2008.1 or higher MPIpro 1.7 (see "Problems installing MPI/Pro" on page 18)
If you are going to run a R2SL model with PIPESIM you need to edit the $eclrc.bat file in the HOME directory where the ECLIPSE installation takes place. Edit the file and specify the path of the PIPESIM installation engine in the SET PIPESIM_LOC variable. For example for PIPESIM 2003 SP3 or higher use:
SET PIPESIM_LOC=C:\Program Files\Schlumberger\PIPESIM\programs\pnengine.exe
If you are using the new componentized version of PIPESIM 2006 you need to set
SET PIPESIM_LOC=C:\Program Files\Schlumberger\PIPESIM\programs\pnetstub.exe
It is good practice, if you have an internal FLEXlm license for PIPESIM, to append this one to the ECLIPSE license.dat and point the LM_LICENSE_FILE environment variable to that location. Right click over My Computer | Properties |Advanced | Environment Variables | System Variables.
Hint
ECLIPSE Suite EMail:cadserv21@hotmail.com R2SL www.cadfamily.com Installation Guide PC Configuration The document is for study only,if tort to your rights,please inform us,we will delete
75
For example:
LM_LICENSE_FILE = d:\ecl\macros\license.dat
Check the HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager LM_LICENSE_FILE in the Windows registry (Start | Run | Regedit) is directed to the common license file. This prevents the following error:
@--Message from R2SL at time 0.0 days @ Waiting for the initial response from task RES. @--Message @ @--Message @ @-@ @-@ Error from R2SL at time 0.0 days Waiting for the initial response from task RES. from R2SL at time 0.0 days Waiting for the initial response from task RES. from task RES at time 0.0 days LICENSE FAILURE: ERROR NUMBER IS -5 from task RES at time 0.0 days Task RES stopped due to errors.
0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0: 0:
Error
When running coupled simulations with PIPESIM it is best to run from the ECLIPSE launcher in interactive mode. In this way the PIPESIM Net solver is displayed for net debugging purposes. You should also check the SLAVE.DBG file, which is created in the network directory. Note the Keyword NETDEBUG governs this file. Another useful keyword WRITEDBG in the R2SL file. We recommend that you activate features such as mapping and netbal. It is also good practice to keep track of the memory performance in the Windows Task Manager. If the memory usage drops suddenly it usually because the network has stopped running. If the network fails check the SLAVE.DBG file.
7 8 9
R2SL ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 76 PC Configuration The document is for study only,if tort to your rights,please inform us,we will delete
Known Issues
1 Do not place the data files for R2SL in a windows directory path longer than 72 characters. R2SL will fail with the following error:
********* RUNSPEC Section READING RUNMODE @-Error from d:\apps\geoquest\eclipse\2006.2\bin\pc\r2sl_mpi.exe at time 0.0 days @ Keyword TASKSPEC @ encountered while reading section/record 1 @ of keyword TASKSPEC @ Usually caused by missing slash ( / )
2 3
Do not place more than one PIPESIM network in a directory. The PIPESIM engine creates non-unique files hence a conflict will occur. If you are copying the data files from a CD make sure you disable the read-only attribute given by Windows when you do it. Right click over the folder | properties and un-check the read-only option; and apply it to all the sub-folders and files. Make sure that your MPI password is updated. You can do this typing in the command prompt mpipasswd. Alternatively go to Programs | MPI Software Technologies | MPIpro | Password registration and you will get the next prompt:
The password that you have to type here is the one that you use to log in as the current user to the machine.
ECLIPSE Suite EMail:cadserv21@hotmail.com R2SL www.cadfamily.com Installation Guide PC Configuration The document is for study only,if tort to your rights,please inform us,we will delete
77
Sometimes your MPI service is not activated automatically and you get the next error:
In this case right-click over My Computer in the desktop and select Manage then click on Services & Applications | Services and check if the MPI/Pro service is up.
Hint 6
To start the service click on the play button on the task bar.
In some instances PIPESIM 2008.1 will hang once it has been initialized (R2SL will halt reading the SUMMARY section). This is due to MPI 1.6.4 not being un-installed prior to MPI version 1.7 being installed and a mismatch of the MPIPro.DLL has occurred. The obvious fix is to remove both MPI 1.7 and 1.6.4 and reinstall 1.7. If this fails remove the MPIPro.dll file from the PIPESIM programs directory.
R2SL ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 78 PC Configuration The document is for study only,if tort to your rights,please inform us,we will delete
Upgrading a license Appendix C
Upgrading a license for ECLIPSE (2000A-2005A_1) to 2006.1 and later version

The ECLIPSE 2006.1 software used a new license daemon and license file. To run 2006.1 and later versions you must upgrade both the ECLIPSE license file and the license daemon. Then stop the old license server before you start the new one. ECLIPSE software released prior to 2006.1 will still run with the new file and daemon as it is backwards compatible. This document assumes only licenses for Schlumberger software are run from the server. If other software is licensed from the same server then please seek advice before making any changes.
Editing the license file

The first step is to edit the license file. A 2006.1 license file looks like this, there are usually multiple INCREMENT or FEATURE blocks:-
SERVER this_host 0123456789 VENDOR slbfd USE_SERVER INCREMENT gasfield slbfd 2006.0 1-jun-2006 1 SUPERSEDE=gasfield \ NOTICE="0738198 A2GF-P1" START=12-jun-2006 AUTH={ slbfd=( \ SIGN="003E 9B74 A1DC 645B D177 B400 A079 E400 1D40 09BC 2C27 9800 B0AE DA4B FC48") lmgrd_slb=( LK=7689E5620621 SIGN="008D\ 3799 4265 25A4 25C5 DA12 534D A800 4331 A349 9740 7B86 36BF \ A613 FBF6" SIGN2="00F9 B765 0F28 3BEE 6179 6718 22C7 0D00 B1E0 \ 7030 1CEB B59E D3CB D5C8 E569") }
ECLIPSE Suite EMail:cadserv21@hotmail.com Upgrading a license www.cadfamily.com Installation Guide Upgrading a license for ECLIPSE (2000A-2005A_1) to 2006.1 and later version The document is for study only,if tort to your rights,please inform us,we will delete
79
For reference a 2005a_1 license file looks like this, again a typical line file consists of many FEATURE or INCREMENT blocks:-
SERVER this_host 0123456789 VENDOR lmgrd.slb INCREMENT cougar lmgrd.slb 2005.0 1-jul-2006 1 DC7B24A1DC1519A217BC \ VENDOR_STRING=cougar ck=222 SIGN="0056 1A77 5EDD 6281 295B \ C021 53FD 0E00 B128 D7B0 C15A CD5D 09AD 2D43 8EEE" SIGN2="0004 \ 7213 BE7B AD65 61C8 9431 769A 5E00 EDA7 7462 8E26 BEF1 6726 \ 353B A790"
To combine the features from 2006.1 and prior versions cut and paste the FEATURE/INCREMENT lines from the old file into the new. Warning Do not edit the lines. Use an editor such as notepad or vi. If any formatting is added (for example bold or font size) then the license will not work. Do not copy the header lines.
Using the examples above the following is the result. This step is not required if the new 2006.1 license enables everything your older license did, although it will not do any harm. This gives the result below:-
SERVER this_host 0123456789 VENDOR slbfd USE_SERVER INCREMENT gasfield slbfd 2006.0 1-jun-2006 1 SUPERSEDE=gasfield \ NOTICE="0738198 A2GF-P1" START=12-jun-2006 AUTH={ slbfd=( \ SIGN="003E 9B74 A1DC 645B D177 B400 A079 E400 1D40 09BC 2C27 9800 B0AE DA4B FC48") lmgrd_slb=( LK=7689E5620621 SIGN="008D\ 3799 4265 25A4 25C5 DA12 534D A800 4331 A349 9740 7B86 36BF \ A613 FBF6" SIGN2="00F9 B765 0F28 3BEE 6179 6718 22C7 0D00 B1E0 \ 7030 1CEB B59E D3CB D5C8 E569") } INCREMENT cougar lmgrd.slb 2005.0 1-jul-2006 1 DC7B24A1DC1519A217BC \ VENDOR_STRING=cougar ck=222 SIGN="0056 1A77 5EDD 6281 295B \ C021 53FD 0E00 B128 D7B0 C15A CD5D 09AD 2D43 8EEE" SIGN2="0004 \ 7213 BE7B AD65 61C8 9431 769A 5E00 EDA7 7462 8E26 BEF1 6726 \ 353B A790"
Checking the license file

Next check that the top Line is correct. The first word on the top line is the word SERVER; this is always the case in a SERVER license. The second word on the top line is the name of the computer that is to be the license server. On UNIX/Linux or in a Windows Command Shell type hostname. This name should be the second word. The third field is the hostid of the server machine. It can be found by typing @lmhostid on UNIX/Linux or $lmhostid in Windows after ECLIPSE has been installed. You cannot change this field. Upgrading a license ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 80 Upgrading a license for ECLIPSE (2000A-2005A_1) to 2006.1 and later version The document is for study only,if tort to your rights,please inform us,we will delete
Optionally a fourth field contains the port number that the license server will use. We suggest setting this to 1700, assuming that port is not in use by anything else.
Quorum license
A Quorum license has 3 SERVER lines. They follow the same format. 1 2 Check the next line is VENDOR slbfd The third line should be USE_SERVER
All these changes give the following file:-
SERVER server1 0123456789 1700 VENDOR slbfd USE_SERVER INCREMENT gasfield slbfd 2006.0 1-jun-2006 1 SUPERSEDE=gasfield \ NOTICE="0738198 A2GF-P1" START=12-jun-2006 AUTH={ slbfd=( \ SIGN="003E 9B74 A1DC 645B D177 B400 A079 E400 1D40 09BC 2C27 9800 B0AE DA4B FC48") lmgrd_slb=( LK=7689E5620621 SIGN="008D\ 3799 4265 25A4 25C5 DA12 534D A800 4331 A349 9740 7B86 36BF \ A613 FBF6" SIGN2="00F9 B765 0F28 3BEE 6179 6718 22C7 0D00 B1E0 \ 7030 1CEB B59E D3CB D5C8 E569") } INCREMENT cougar lmgrd.slb 2005.0 1-jul2006 1 DC7B24A1DC1519A217BC \ VENDOR_STRING=cougar ck=222 SIGN="0056 1A77 5EDD 6281 295B \ C021 53FD 0E00 B128 D7B0 C15A CD5D 09AD 2D43 8EEE" SIGN2="0004 \ 7213 BE7B AD65 61C8 9431 769A 5E00 EDA7 7462 8E26 BEF1 6726 \ 353B A790"
Save this new file on to the machine to be the license server. The exact location does not matter. Unless you have a reason not to we suggest you save the license as license.dat to the following locations (the defaults): Windows: save to c:\ecl\macros (assuming you installed ECLIPSE to C:\ecl). Linux/UNIX: save to /ecl/macros (assuming an install to /ecl) The next steps will cause any running ECLIPSE jobs to exit. All new jobs will fail to get licenses from when the old license server is stopped until the new one is working properly.
Warning
Configuring the server

Windows
The process is covered in detail in "Licensing" on page 33. Remember to stop any existing license services from the Start/Stop/Reread tab if applicable before you start to configure the new service.
81
UNIX/Linux
Complete the following steps, they are described in more detail below:1 2 3 4 Stop the existing license server. Remove/disable any startup scripts for the old license server, if they exist. Create new startup scripts. Test to see if it is working.
The following assumes that the ECLIPSE software is installed to /ecl, and the license file is stored in /ecl/macros and is called license.dat. You may need to be logged in as root for some steps. Amend the paths as appropriate for your install if you have not accepted the defaults.
Stop the existing license server

1 Run the following command ps ef | grep lmgrd this will let you know if any lmgrd processes are running. If you have a running license server the output will be something similar to below.
root 29769 1 0 Jul12 ? 00:00:00 /ecl/tools/linux/flexlm95/lmgrd -c /ecl/macros/license.dat -2 -p -l +/tmp/flex.log root 29770 29769 0 Jul12 ? 00:00:00 lmgrd.slb -T abgkickstart 9.5 3 -c /ecl/macros/license.dat -p --lmgrd_start 44b4ed38 738 28161 27876 0 19:58 ? 00:00:00 grep lmgrd
Note
The top line is the lmgrd license server, if you see more than one lmgrd running be careful to kill the correct one. Other licenses may be being served from this machine. If there is more than 1 lmgrd running, seek advice before proceeding.
2 3 4
If there is only one lmgrd you can stop it with the following command pkill lmgrd. Check with the same command ps-ef | grep lmgrd again, the lmgrd process should be gone from the output. Next check if the license is automatically being started when the machine boots. There are 2 likely ways this may be configured. There could be a line inside /etc/rc.local to start the license server, look for lmgrd in that file and put a # at the start of the line to comment it out. Alternatively there could be a startup script in one of a number of places. The likely places depend on your version of UNIX/Linux:-
RedHat 3 or 4: /etc/rc3.d and /etc/rc5.d SUSE SLES 8,9 or 10: /etc/init.d/rc3.d and /etc/init.d/rc5.d Solaris 8 or 10: /etc/rc2.d or /etc/rc3.d
There is no fixed name for the startup script, although it does usually begin with a capital S. If you are having trouble finding it try running the following command cd /etc; grep lr lmgrd *, If this command finds any scripts with the string lmgrd inside it will print their name to the screen. Once you find the script move it to /tmp with the following command, replace filename with the name of the script. mv filename /tmp.
Upgrading a license ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 82 Upgrading a license for ECLIPSE (2000A-2005A_1) to 2006.1 and later version The document is for study only,if tort to your rights,please inform us,we will delete
Now the old license server is stopped, and any startup links to it are removed we can make the new startup scripts.
Creating new startup scripts

1 2 Create a new file called eclflexstart, in /etc/init.d. Cut and paste the following lines into it.
#!/bin/sh /ecl/tools/linux/flexlm108/lmgrd -c /ecl/macros/license.dat -2 -p -l +/tmp/flex.log
Hint
D not forget to change the paths if appropriate. Replace /ecl/macros/license.dat with the path to your license file.
Replace /ecl/tools/linux/flexlm108/lmgrd with the full path to lmgrd on your system. Assuming you have installed to /ecl the possibilities are:/ecl/tools/linux/flexlm113/lmgrd /ecl/tools/linux_x86_64/flexlm113/lmgrd /ecl/tools/sun/flexlm1138/lmgrd
4 5
Next make the script executable with the following command chmod 755 /etc/init.d/eclflexstart Then create a link so the script is run at boot. The links should be in the following places:RedHat 3 or 4: in /etc/rc3.d and /etc/rc5.d SUSE SLES 8,9 or 10: in /etc/init.d/rc3.d and /etc/init.d/rc5.d Solaris 8 or 10: /etc/rc3.d
Change to the appropriate directory (/etc/rc3.d in this example) and create a link. cd /etc/rc3.d; ln s /etc/init.d/eclflexstart S99eclflexstart. Under linux it is best to repeat the process in both the rc3.d and rc5.d directories as either runlevel could be used. In Solaris just create the one link in /etc/rc3.d.
Note
Testing the server

Next test the server to see if it works properly. 1 Type /etc/init.d/eclflexstart, if all has gone well nothing will appear on the screen, and a log file will be generated called /tmp/flex.log. Any problems are output to this file.
83
A successful start should look something like this:20:41:34 (lmgrd) FLEXnet Licensing (v10.8.0.1 build 19446) started o n abg-kickstart (linux) (7/13/2006) 20:41:34 (lmgrd) Copyright (c) 19882005 Macrovision Europe Ltd. and/or Macrovision Corporation. All Rig hts Reserved. 20:41:34 (lmgrd) US Patents 5,390,297 and 5,671,412. 20:41:34 (lmgrd) World Wide Web: http://www.macrovision.com 20:41:34 (lmgrd) License file(s): /ecl/macros/license.dat 20:41:34 (lmgrd) lmgrd tcp-port 1700 20:41:34 (lmgrd) Starting vendor daemons ... 20:41:34 (lmgrd) Started slbfd (internet tcp_port 51231 pid 10394) 20:41:34 (slbfd) FLEXnet Licensing version v10.8.0.6 build 23943 20:41:34 (slbfd) Server started on abg-kickstart for: co2seq 20:41:34 (slbfd) cougar_multiresponse fs_patternbalance cougar 20:41:34 (slbfd) prodopt waterservices r2sl_gap 20:41:34 (slbfd) r2sl_tanks r2sl_lookup resopt 20:41:34 (slbfd) uncertainty multiple_realisation cbm_template 20:41:34 (slbfd) cmt_template h2o_template hf_template 20:41:34 (slbfd) coalbed compositional datacheck 20:41:34 (slbfd) eclipse eclipse4d eclipselite 20:41:34 (slbfd) flux foam friction 20:41:34 (slbfd) frontsim fs_iorscale gasfield 20:41:34 (slbfd) gaslift gasquality geomechanics 20:41:34 (slbfd) gf_fg_analysis gf_fg_openspirit gf_fg_populate 20:41:34 (slbfd) gf_flogeo gf_flogrid gf_floviz 20:41:34 (slbfd) gf_petragrid gf_scal gioption 20:41:34 (slbfd) graf grid gridsim 20:41:34 (slbfd) lgr multisegwells nearwellborem 20:41:34 (slbfd) networks office openeclipse 20:41:34 (slbfd) parallel planopt polymers 20:41:34 (slbfd) pvt rescoupling schedule 20:41:34 (slbfd) simopt simopt4d solvents 20:41:34 (slbfd) surfactant thermal tracer 20:41:34 (slbfd) unencodedhmd vfp sma 20:41:34 (slbfd) proppantflow WELLTEST weltest200 20:41:34 (slbfd) r2sl 20:41:34 (lmgrd) slbfd using TCP-port 51231 20:41:34 (slbfd) Serving features for the following vendor names: slbfd lmgrd_slb
Common errors and solutions

A lot of errors are self explanatory. However, some common error messages give errors which bear little resemblance to the real problem. Table C.1 Problem
License file not found.
Common errors and solutions Solution

Check that the path to the license file is correct, and the user starting up the license server has permission to open it.
Invalid Authorization Code or The license file has been tampered with, or is for the wrong machine. encryption code in license file is You need to obtain a correct license file. inconsistent TCP port is already in use This usually means that something is using the same port as the license server wishes to use. Often it means another license server is already running. Check with ps ef | grep lmgrd. Once you find which process is using the port, either stop it, or change the license server port (last number on the top line of the license file). Version specific signature generation failed SIGN missing from FEATURE This message means the license file has been edited, and the header lines are either incomplete or missing. You need to obtain a correct license file. The USE_SERVER line is missing from the file. Enter this, then restart the license server.
"HOSTNAME" not a valid server The computer name on the top line of the license file doesnt match hostname, exiting the machine running the license server. Edit the second word on the top line of the license file. Vendor Daemon died with status This means the vendor daemon has encountered a problem. On UNIX/Linux there can be many causes and the problem is hard to find. On Windows the problem is usually the permission of either the directory holding the lmgrd executable, or where the log file is written. Check if the path to slbfd is correct near the top of the license file.
slbfd: can't initialize: Invalid AUTH={} signature
85
A Installing OFED drivers
Appendix D
Installation Guide
Open Fabrics Enterprise Distribution (OFED) Version 1.2 Installation Guide June 2007 1 2 3 4 5 6 7 8 9 "Overview" on page 87 "OFED Package Contents" on page 88 "Hardware and Software Requirements" on page 89 "How to Download and Extract the OFED Distribution" on page 89n "Installing OFED Software" on page 90 "Building OFED RPMs" on page 92 "IP-over-IB (IPoIB) Configuration" on page 93 "Uninstalling OFED" on page 94 "Configuration" on page 94
10 "Related Documentation" on page 95
Overview
This is the OpenFabrics Enterprise Distribution (OFED) version 1.2 software package supporting InfiniBand and iWARP fabrics. It is composed of several software modules intended for use on a computer cluster constructed as an InfiniBand subnet or an iWARP network. This document describes how to install the various modules and test them in a Linux environment.
ECLIPSE Suite EMail:cadserv21@hotmail.com Installing OFED drivers www.cadfamily.com 2007.2 Installation Guide Installation Guide The document is for study only,if tort to your rights,please inform us,we will delete
87
General Notes
1 The install script removes all previously installed OFED packages and re-installs from scratch. (Note: Configuration files will not be removed). You will be prompted to acknowledge the deletion of the old packages. When installing OFED on an entire [homogeneous] cluster, a common strategy is to build the software only once (perhaps on a shared file system such as NFS). The resulting RPMs can then be installed on all nodes in the cluster using any cluster-aware tools (such as pdsh).
OFED Package Contents

The OFED Distribution package generates RPMs for installing the following:
OpenFabrics core and ULPs

HCA drivers (mthca, ipath, ehca) iWARP driver (cxgb3) core Upper Layer Protocols: IPoIB, SDP, SRP Initiator, iSER Initiator RDS, VNIC and uDAPL
OpenFabrics utilities
OpenSM: InfiniBand Subnet Manager Diagnostic tools Performance tests
MPI
OSU MVAPICH stack supporting the InfiniBand and iWARP interface Open MPI stack supporting the InfiniBand and iWARP interface OSU MVAPICH2 stack supporting the InfiniBand and iWARP interface MPI benchmark tests (OSU BW/LAT, Intel MPI Benchmark, Presta)
Extra packages
open-iscsi: open-iscsi initiator with iSER support ib-bonding: Bonding driver for IPoIB interface Sources of all software modules (under conditions mentioned in the modules' LICENSE files) Documentation
Installing OFED drivers ECLIPSE Suite 2007.2 Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 88 Installation Guide The document is for study only,if tort to your rights,please inform us,we will delete
Hardware and Software Requirements

1 Server platform with InfiniBand HCA or iWARP RNIC (see OFED Distribution Release Notes for details) 2) Linux operating system (see OFED Distribution Release Notes for details) 3) Administrator privileges on your machine(s) 4) Disk Space: a b For Build & Installation: 300MB For Installation only: 200MB
5) For the OFED Distribution to compile on your machine, some software packages of your operating system (OS) distribution are required. These are listed here. OS Distribution Required Packages General: Note Common to all gcc, glib, glib-devel, glibc, glibc-devel, glibc-devel-32bit (to build 32bit libraries on x86_86 and ppc64), zlib-devel, automake, autoconf, libtool. RedHat, Fedora kernel-devel, rpm-build SLES 9.0, kernel-source, udev, rpm SLES 10.0, kernel-source, rpm To build 32-bit libraries on x86_64 and ppc64 platforms, the 32-bit glibc-devel should be installed.
Specific Component Requirements: Note Mvapich - a Fortran Compiler (such as gcc-g77) Mvapich2 - libstdc++-devel, sysfsutils (SuSE), libsysfs-devel (RedHat5.0, Fedora C6) Open MPI - libstdc++-devel, sysfsutils (SuSE), libsysfs-devel (RedHat5.0, Fedora C6) ibutils - tcl-8.4, tcl-devel-8.4, tk, libstdc++-devel tvflash - pciutils-devel mstflint - libstdc++-devel (32-bit on ppc64) The installer will warn you if you attempt to compile any of the above packages and do not have the prerequisites installed.
How to Download and Extract the OFED Distribution

1 Download the OFED-X.X.X.tgz file to your target Linux host. If this package is to be installed on a cluster, it is recommended to download it to an NFS shared directory. Hint
89
Extract the package using: tar xzvf OFED-X.X.X.tgz
Installing OFED Software

1 2 Go to the directory into which the package was extracted: cd /..../OFED-X.X.X Installing the OFED package must be done as root. For a menu-driven first build and installation, run the installer script: ./install.sh Interactive menus will direct you through the install process. Note After the installer completes, information about the OFED installation such as the prefix, the kernel version, and installation parameters can be found by running /etc/infiniband/info.
During the interactive installation of OFED, two files are generated: ofed.conf and ofed_net.conf. ofed.conf holds the installed software modules and configuration settings chosen by the user. ofed_net.conf holds the IPoIB settings chosen by the user. If the package is installed on a cluster-shared directory, these files can then be used to perform an automatic, unattended installation of OFED on other machines in the cluster. The unattended installation will use the same choices as were selected in the interactive installation. For an automatic installation on any host, run the following: ./OFED-X.X.X/install.sh -c <path>/ofed.conf -net <path>/ofed_net.conf
Notes
1 It is possible to rename and/or edit the ofed.conf and ofed_net.conf files. Thus it is possible to change user choices (observing the original format). See examples of ofed.conf and ofed_net.conf under OFED-X.X.X/docs. To make debugging kernel issues easier, it is recommended to set the following environment variable before building OFED: export OPENIB_KERNEL_EXTRA_CFLAGS=-g This will attach debug info to generated kernel binaries without affecting their speed. 3 Important note for open-iscsi users: Installing iSER as part of the OFED installation will also install open-iscsi. Before installing OFED, please uninstall any open-iscsi version that may be installed on your machine. Installing OFED with iSER support while another open-iscsi version is already installed will cause the installation process to fail.
Install Process Results

The OFED package is installed under <prefix> directory. Default prefix is /usr
The kernel modules are installed under: - Infiniband subsystem: /lib/modules/ùname r`/updates/kernel/drivers/infiniband/ - open-iscsi /lib/modules/ùname -r`/updates/kernel/drivers/scsi/ Chelsio driver:
/lib/modules/ùname -r`/updates/kernel/drivers/net/cxgb3/cxgb3.ko RDS:
/lib/modules/ùname -r`/updates/kernel/net/rds/rds.ko The package kernel include files are placed under <prefix>/src/openib. These includes should be used when building kernel modules which use the Openfabrics stack. (Note that these includes, if needed, are "backported" to your kernel). The raw package (un-backported) source files are placed under <prefix>/src/ofa_kernel-1.2 The script "openibd" is installed under /etc/init.d/. This script can be used to load and unload the software stack. The directory /etc/infiniband is created with the files "info" and "openib.conf". The "info" script can be used to retrieve OFED installation information. The "openib.conf" file contains the list of modules that are loaded when the "openibd" script is used. The file "90-ib.rules" is installed under /etc/udev/rules.d/ man pages are installed under /usr/share/man If libibverbs-utils is installed, then ofed.sh and ofed.csh are installed under /etc/profile.d/. These automatically update the PATH environment variable with <prefix>/bin. In addition, ofed.conf is installed under /etc/ld.so.conf.d/ to update the dynamic linker's run-time search path to find the InfiniBand shared libraries. The file /etc/modprobe.conf is updated to include the following: alias ib<n> ib_ipoib for each ib<n> interface. alias net-pf-27 ib_sdp for sdp.
If opensm is installed, the daemon opensmd is installed under /etc/init.d/ and opensm.conf is installed under /etc. If IPoIB configuration files are included, ifcfg-ib<n> files will be installed at: RedHat: /etc/sysconfig/network-scripts/ SuSE: /etc/sysconfig/network/
91
If iSER is included, open-iscsi user-space files will be also installed: Configuration files will be installed at /etc/iscsi Startup script will be installed at: RedHat: /etc/init.d/iscsi SuSE: /etc/init.d/open-iscsi
Other tools (iscsiadm, iscsid, iscsi_discovery, iscsi-iname, iscsistart) will be installed under /sbin. Documentation will be installed under: RedHat: /usr/share/doc/iscsi-initiator-utils-<version number> SuSE: /usr/share/doc/packages/open-iscsi
man pages will be installed under /usr/share/man/.
Building OFED RPMs

1 Go to the directory into which the package was extracted: cd /..../OFED-X.X.X Building RPMs can be done as a non-root user. 2 For interactive build run the build.sh script: ./build.sh Interactive menus will direct you through the build process. During the manual building of OFED RPMs, ofed.conf is generated. ofed.conf holds the selected software modules and configuration settings chosen by the user. 3 For an automated build, run the following: ./OFED-X.X.X/build.sh -c <path>/ofed.conf Note It is possible to rename and/or edit the ofed.conf file. Thus it is possible to change user choices (observing the original format).
See an example of ofed.conf under OFED-X.X.X/docs.
Build Process Results

The OFED build.sh script builds OFED binary RPMs under OFED-X.X.X/RPMS; the sources are placed in OFED-X.X.X/SRPMS/. Running this script does not change any currently installed components, and the script does not change the current kernel build. Once the build process has completed, the user may run ./install.sh to install the new RPMs. This time, however, any previously installed OFED components will be uninstalled and the newly built package will be installed.
Note: Depending on your hardware, the build procedure may take 30-45 minutes. Installation, however, is a relatively short process (~5 minutes). A common strategy for OFED installation on large homogeneous clusters is to extract the tarball on a network file system (such as NFS), build OFED on NFS, and then run the installer on each node with the RPMs that were previously built.
IP-over-IB (IPoIB) Configuration

Configuring IPoIB is an optional step during the installation. During an interactive installation, the user may choose to insert the ifcfg-ib<n> files. If this option is chosen, the ifcfg-ib<n> files will be installed under: RedHat: /etc/sysconfig/network-scripts/ SuSE: /etc/sysconfig/network/
Setting IPoIB Configuration:

The default IPoIB interface configuration is based on DHCP. Note that a special patch for DHCP servers is required for supporting IPoIB clients. A patch for dhcp v3.0.4 is available under OFED-X.X.X/docs/dhcp. If you are not using DHCP to obtain IP addresses for clients using IPoIB, you must manually specify the full IP configuration during the interactive installation: IP address, network address, netmask, and broadcast address. For unattended installations, a configuration file can be provided with this information. The configuration file must specify the following information: Fixed values for each IPoIB interface Base IPoIB configuration on Ethernet configuration (may be useful for cluster configuration)
93
Here are some examples of ofed_net.conf:
# Static settings; all values provided by this file IPADDR_ib0=172.16.0.4 NETMASK_ib0=255.255.0.0 NETWORK_ib0=172.16.0.0 BROADCAST_ib0=172.16.255.255 ONBOOT_ib0=1 # Based on eth0; each '*' will be replaced with corresponding octet # from eth0. LAN_INTERFACE_ib0=eth0 IPADDR_ib0=172.16.'*'.'*' NETMASK_ib0=255.255.0.0 NETWORK_ib0=172.16.0.0 BROADCAST_ib0=172.16.255.255 ONBOOT_ib0=1 # Based on the first eth<n> interface that is found (for n=0,1,...); # each '*' will be replaced with corresponding octet from eth<n>. LAN_INTERFACE_ib0= IPADDR_ib0=172.16.'*'.'*' NETMASK_ib0=255.255.0.0 NETWORK_ib0=172.16.0.0 BROADCAST_ib0=172.16.255.255 ONBOOT_ib0=1
Uninstalling OFED
There are two ways to uninstall OFED: 1) Using the installation menu. 2) Using the script ofed_uninstall.sh. The script is part of ofed-scripts package.
Configuration
Most of the OFED components can be configured or reconfigured after the installation by modifying the relevant configuration files. The list of the modules that will be loaded automatically upon boot can be found in the /etc/infiniband/openib.conf file. Other configuration files include: SDP configuration file: /etc/libsdp.conf OpenSM configuration file: /etc/opensm.conf DAPL configuration file: /etc/dat.conf
See packages Release Notes for more details.
Note
After the installer completes, information about the OFED installation such as the prefix, kernel version, and installation parameters can be found by running /etc/infiniband/info.
Related Documentation
OFED documentation is located in the ofed-docs RPM. After installation the documents are located under the directory: /usr/share/doc/ofed-docs-1.2 for RedHat /usr/share/doc/packages/ofed-docs-1.2 for SuSE
Document list
README.txt OFED_Installation_Guide.txt MPI_README.txt
Examples of configuration files

OFED_tips.txt HOWTO.build_ofed All release notes and README files
For more information, please visit the OpenFabrics web site: http://www.openfabrics.org/ open-iscsi documentation is located at: RedHat: /usr/share/doc/iscsi-initiator-utils-<version number> SuSE: /usr/share/doc/packages/open-iscsi
For more information, please visit the open-iscsi web site: http://www.open-iscsi.org/
95
Index Appendix E
Numerics
3D Stereo options . . . . . . . 57 External Job Option . . . . . . 70 ECLIPSE Office . . . . . 73 Running. . . . . . . . . . . 73 SimOpt . . . . . . . . . . . 73 Myrinet_ia32 . . . . . . . . . . 24 Myrinet_ia64 . . . . . . . . . . 24 Myrinet_x86_64. . . . . . . . 24 Parallel ECLIPSE . . . 43 PC software . . . . . . . 15 Scali. . . . . . . . . . . . . 24 UNIX software . . . . . 21 Installing OFED drivers . . 87 Itanium2 clusters . . . . . . . 47
B
Batch jobs UNIX . . . . . . . . . . . . 38 Batch mode PC . . . . . . . . . . . . . . 41
G
Grid menus . . . . . . . . . 16, 29
H
HP Itanium2 clusters, special considerations . . . . . . 47
L
Large models . . . . . . . . . . 42 Limitations. . . . . . . . . . . . 69 Non-PVM Remote Option69 Linux. . . . . . . . . . . .9, 21, 45 Linux (32 & 64 bit) executables Parallel . . . . . . . . . . . .11 LSF Queues . . . . . . . . . . . 51 LSF SIS Integration kit . . . 49
C
CCP Scheduler . . . . . . . . . 62 Client/server installation . . 17 Windows 2000 or XP . 17 Configuring PC software . . 16
I
IBM . . . . . . . . . . . . . . . . . 44 IBM RS/6000 . . . . . . . . . . 11 software requirements . 11 Installation procedure UNIX, parallel ECLIPSE44 Installing Acrobat Reader. . . . . . 28 Linux from another machine23 MPI/Pro. . . . . . . . . . . 17 Myrinet drivers Linux . . . . . . . . . . . . . . . . 23
D
dos2unix . . . . . . . . . . . . . 71
M
Macros command line flags, UNIX37 PC systems . . . . . . . . 39 UNIX systems. . . . . . 35 Microsoft CSS . . . . . . . . . 59 Microsoft Management Console61
E
ECLIPSE Office . . . . . 68, 73
ECLIPSE Suite EMail:cadserv21@hotmail.com www.cadfamily.com Installation Guide The document is for study only,if tort to your rights,please inform us,we will delete
Index
97
MPI/Pro Problems installing . . .18 Myrinet executables for Linux .46 parallel executables (Linux)51 PC
Setting up . . . . . . . . . 44 Sun and SGI . . . . . . . 45 UNIX and Linux . . . . 43 Using Non-PVM Remote67 PC Configuration R2SL . . . . . . . . . . . . 75
UNIX systems . . . . . . 35 SGI Altix executables - Linux47 SimOpt . . . . . . . . . . . . . . . 68 External Job Option . . 73 Software products . . . . . . . . 9 Software requirements . . . . 43 Linux. . . . . . . . . . . . . 44 SGI . . . . . . . . . . . . . . 43 SUN . . . . . . . . . . . . . 43 Solaris graphics options. . . . . . . . . . . . 58 Standalone installation . . . . 17 Windows 2000 or XP . 17 Stereo mode . . . . . . . . . . . 57 SUN . . . . . . . . . . . . . . . . . 44 software requirements . 11 Supported platforms . . . . . . . 9
N
Networked PCs software requirements . 11 NFS Drivers. . . . . . . . . . . .71 Non-PVM Remote Option67 to 68 ECLIPSE Office . . . . .68 SimOpt . . . . . . . . . . .68 SimOpt, Limitations . .69
PC Launcher. . . . . . . . . . . 19 PC software . . . . . . . 15 to 16 PC systems macros and scripts . . . 39 PC to UNIX . . . . . . . . 67, 71 External Job Option . . 71 requirements . . . . . . . 71 Platform Availability . . . . . . 8 Printing manuals . . . . . . . . 28
O
On-line help. . . . . . . . . . . .29
R
Reservoir Coupling MPI . . . . . . . . . . . . . 42 PVM. . . . . . . . . . . . . 42
T
Tuning Scali . . . . . . . . . . . 25
P
Parallel ECLIPSE Installing . . . . . . . . . .43 Linux . . . . . . . . . . . . .45 PC . . . . . . . . . . . . . . .56 Running . . . . . . . . . . .45
S
Scali parallel executables (Linux)51 Scripts PC systems . . . . . . . . 39
U
UNIX systems macros and scripts . . . 35
Index ECLIPSE Suite Installation Guide www.cadfamily.com EMail:cadserv21@hotmail.com 98 The document is for study only,if tort to your rights,please inform us,we will delete

Eclipse Instal Guide

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Eclipse Instal Guide

Transféré par

Droits d'auteur :

Formats disponibles

ECLIPSE Suite

Service mark information

Italic, for example e = mc2. This is the same

Standard buttons in interactive programs

Chapter 1 - 2008.1 Simulation Software System Requirements ................................................... 8

Chapter 2 - 2008.1 Simulation Software installation.................................................................... 12

Chapter 3 - Licensing ..................................................................................................................... 33

Chapter 4 - Running the software ................................................................................................. 35

Chapter 5 - Microsoft CSS Installation ......................................................................................... 59

Appendix A - Non-PVM remote and external job options ........................................................... 67

Appendix C - Upgrading a license................................................................................................. 79

Appendix D - Installing OFED drivers ........................................................................................... 87

2008.1 Simulation Software System Requirements

Table 1.1 Machine

Supported operating systems and compilers Operating System

Windows XP plus Service Pack 2 is required.

Table 1.1 Machine

Supported operating systems and compilers (Continued) Operating System

Linux 32-bit Linux x86_64

Linux 64-bit (Itanium 2) SGI Altix

Red Hat 4.0 update 6 SGI ProPack 5

Table 1.2 Software

Third party tools and applications Version Notes

FLEXlm Adobe Acrobat Carnac

Table 1.2 Software

Third party tools and applications (Continued) Version

set set set set

The system must be rebooted to make the changes take effect.

Linux (32 and 64 bit) executables for parallel

2008.1 Simulation Software installation

Preparing to install 2008.1 Simulation Software

ECLIPSE and Scali

Installing PC software from DVD

$ADOBEPATH\acrobat 8.0\reader\acrord32 $GUIDE_PATH\gridsim_ug.pdf

Standalone installation on Windows XP

Client/server installation on Windows XP

Problems installing MPI/Pro

The macros directory:

The tools directory contains a pc subdirectory which contains:

The 2008.1 directory contains:

A number of directories containing utilities and building blocks, for example

Installing Linux software from CD/DVD

The autoinstall procedure prompts with the following information.

Do you want to install macros ? [default n]

Installing Tools also installs Acrobat.

set path=($path /ecl/macros)

setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH:/usr/openwin/lib

Installing Linux from another machine

Installing Myrinet drivers for Linux

DVD1/3rdparty/LINUX/resource contains the following directories:

Installing Scali drivers for Linux

Installing Scali software

On Gigabit-based systems it may be worth setting the environment variables SCAFUN_TCP_RXBUFSZ=131072

More Scali tuning

Installing Infiniband drivers

General Infiniband notes

User Manuals and On-line Help

Printing manuals from the HTML files is not recommended.

Installing Acrobat Reader

for example, for UNIX:

The 2008.1 directory contains:

The resource directory which contains resources shared by several programs.

Installing Schlumberger Licensing