ANSYS Remote Solve Manager Tutorials

Remote Solve Manager R16.0 Tutorials

ANSYS Release 16.0ANSYS, Inc.January 2015Southpointe

2600 ANSYS DriveCanonsburg, PA 15317 ANSYS, Inc. is

certified to ISO9001:2008.

[email protected]://www.ansys.com(T) 724-746-3304(F) 724-514-9494

Copyright and Trademark Information

2014-2015 SAS IP, Inc. All rights reserved. Unauthorized use, distribution or duplication is prohibited.

ANSYS, ANSYS Workbench, Ansoft, AUTODYN, EKM, Engineering Knowledge Manager, CFX, FLUENT, HFSS, AIMand any and all ANSYS, Inc. brand, product, service and feature names, logos and slogans are registered trademarksor trademarks of ANSYS, Inc. or its subsidiaries in the United States or other countries. ICEM CFD is a trademarkused by ANSYS, Inc. under license. CFX is a trademark of Sony Corporation in Japan. All other brand, product,service and feature names or trademarks are the property of their respective owners.

Disclaimer Notice

THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE CONFID-ENTIAL AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS SUBSIDIARIES, OR LICENSORS. The software productsand documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license agreementthat contains provisions concerning non-disclosure, copying, length and nature of use, compliance with exportinglaws, warranties, disclaimers, limitations of liability, and remedies, and other provisions. The software productsand documentation may be used, disclosed, transferred, or copied only in accordance with the terms and conditionsof that software license agreement.

ANSYS, Inc. is certified to ISO 9001:2008.

U.S. Government Rights

For U.S. Government users, except as specifically granted by the ANSYS, Inc. software license agreement, the use,duplication, or disclosure by the United States Government is subject to restrictions stated in the ANSYS, Inc.software license agreement and FAR 12.212 (for non-DOD licenses).

Third-Party Software

See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary softwareand third-party software. If you are unable to access the Legal Notice, please contact ANSYS, Inc.

Published in the U.S.A.

Table of Contents

Configuring Remote Solve Manager (RSM) to Submit Jobs to a Microsoft HPC Cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11. Installing ANSYS Products in a Microsoft HPC Cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22. Configuring RSM on the Cluster Head Node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.Troubleshooting RSM Issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.1. Gathering RSM Job Logs for Systems Support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2. Issue:My Computer Disabled in RSM Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.3. Configuring Multiple Network Cards (NIC) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.4. Disabling IPv6 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.5. Issue: Cannot resolve localhost ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.6. Disabling Microsoft User Account Control (UAC) .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.7. Common Errors Found in RSM Job Log .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring Remote Solver Manager (RSM) to Submit Jobs to a Linux LSF, PBS,Torque with Moab, or UGE(formerly SGE) Cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

1. Installing ANSYS Products in a Linux Cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.1. Exporting the /ansys_inc Directory .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2. Configuring RSM on the Cluster Head Node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.1. Creating an rsmadmins Group and User Accounts .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.1.1. About the rsmadmin Account .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.2. Using the RSM Setup Wizard to Configure RSM ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.2.1. Launching the RSM Setup Wizard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.2.2. Specifying Machine and Cluster Information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.2.3. Adding a Compute Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.2.4. Adding a Queue .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.2.5. Defining Accounts .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.2.6. Testing the Connection .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3. Starting Automatic Startup (Daemon) Services for Linux Red Hat or SuSE .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.1. Verifying that Daemon Services are Started .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4. Troubleshooting RSM ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.1. Gathering RSM Job Logs for Systems Support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.2. Issue:My Computer Disabled in RSM Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.3. Configuring Multiple Network Cards (NIC) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.4. Disabling IPv6 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.5. Cannot Resolve localhost ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.6. Common Errors Found in RSM Job Log .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.6.1. Caught exception at user logon: A required privilege is not held by the client. ... . . . . . . . . . . . . . . . . 454.6.2. Caught exception at user logon; logon failure: unknown user name or bad password. Accountpassword not provided. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.6.3. Connection Error/No connection could be made .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.6.4. Failed to create Script Task: Access to the path is denied. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.6.5. Caught exception from script: Failed to find the TCP port from TaskHost run. ... . . . . . . . . . . . . . . . . . . 464.6.6.The submission of the requested job has been cancelled because the Solve Manager .seems not fully initialized. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.6.7. Failed to create working directory on execution nodes via node share/mount .... . . . . . . . . . . . . . . . 47

Submitting CFX, Fluent and Mechanical Jobs to a Linux or Microsoft HPC Cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491. Configuring RSM on a Windows Client Machine Prior to Submitting Jobs to a Linux or WindowsCluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492. Submitting a CFX Job from Workbench to a Linux or Windows Cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513. Submitting a Fluent Job from Workbench to a Linux or Windows Cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534. Submitting a Mechanical Job from Workbench to a Linux or Windows Cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555. Troubleshooting Job Failures .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

iiiANSYS Release 16.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential inform-

ation of ANSYS, Inc. and its subsidiaries and affiliates.

Remote Solve Manager Tutorial: Configuring Custom Client-Side Cluster Integration R16.0 .... . . . . . . . . . . . . . . . . . . . . . . . 611. Before You Begin .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612. Setting Up the RSM Client and Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

2.1. Creating the RSM Compute Server for Custom Cluster Type Keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622.2. Adding a Queue for this Compute Server to Use .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

3. Setting Up Custom Code References .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.1. Making a Copy of CIS Example Files from RSM Directories .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.2. Customizing the Copied Code to Include the Desired Changes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

3.2.1. Modifying the Job Configuration File for the New Cluster Type .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.2.2. Modifying the Custom HPC Commands File to Reference Custom Scripts ... . . . . . . . . . . . . . . . . . . . . . . . 67

3.3. Modifying Scripts to Add Extra Functionality ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.3.1. Submit Example .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.3.2. Cancel Example .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.3.3.Testing the Compute Server Configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Remote Solve Manager Tutorial: Configuring Custom Server-Side Cluster Integration R16.0 .... . . . . . . . . . . . . . . . . . . . . . . 771. Before You Begin .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782. Setting Up the RSM Client and Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

2.1. Adding the Remote Manager to the Clients RSM UI ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792.2. Creating the RSM Compute Server for Custom Cluster Type Keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802.3. Adding a Queue for this Compute Server to Use .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

3. Setting Up Custom Code References .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.1. Logging On to the Remote Manager Machine (Cluster Head Node) .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.2. Making a Copy of Supported Cluster Files from RSM Directories .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.3. Customizing the Code to Include the Desired Changes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

3.3.1. Modifying the Job Configuration File for the New Cluster Type .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.3.2. Modifying the Custom HPC Commands File to Reference Custom Scripts ... . . . . . . . . . . . . . . . . . . . . . . . 85

3.4. Modifying Scripts to Add Extra Functionality ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.4.1. Submit Example .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.4.2. Cancel Example .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913.4.3.Testing the Compute Server Configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

ANSYS Release 16.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential inform-ation of ANSYS, Inc. and its subsidiaries and affiliates.iv

Remote Solve Manager R16.0 Tutorials

Configuring Remote Solve Manager (RSM) to Submit Jobs to aMicrosoft HPC Cluster

Introduction

This tutorial steps you through the configuration of ANSYS Remote Solve Manager (RSM), Solvers, andWorkbench so that solve jobs can be submitted to a Microsoft HPC 2008 or 2012 Server cluster via RSM.

In this tutorial, RSM is configured using the Remote Solve Manager Setup Wizard. For a quick-startguide on using the wizard, select Start > All Programs > ANSYS 16.0 > Remote Solve Manager >Readme - RSM Setup Wizard 16.0.

If you wish to set up RSM manually, refer to the RSM documentation.

Assumptions

These instructions assume the following:

You have installed and configured a Microsoft HPC Server, and the compute nodes can access the clusterhead node. If Microsoft HPC is not configured properly, contact Microsoft for support before you attemptto install ANSYS applications.

You can access a Getting Started Guide for Windows HPC Server at the following locations:

For Windows HPC Server 2008: http://technet.microsoft.com/en-us/library/cc793950.aspx

For Windows HPC Server 2012 R2: http://msdn.microsoft.com/en-us/library/jj884144.aspx

You are a local administrator of the Microsoft HPC cluster and know how to share directories and map networkdrives. If you do not know how to perform these tasks, contact your Systems Administrator for assistance.You can also access help from the Start menu on your desktop.

You know the machine name of the head node on the Microsoft Server HPC cluster.

You are able to install and run ANSYS, Inc. products, including Licensing on Windows systems. For informationon installation and licensing, see the tutorials on the Downloads menu of the ANSYS Customer Portal.

If you have any problems with, or questions about the installation process, go to the Support page ofthe ANSYS Customer Portal and submit a support request.

This tutorial is divided into the following sections:1. Installing ANSYS Products in a Microsoft HPC Cluster2. Configuring RSM on the Cluster Head Node3.Troubleshooting RSM Issues

1ANSYS Release 16.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential inform-

http://technet.microsoft.com/en-us/library/cc793950.aspxhttp://msdn.microsoft.com/en-us/library/jj884144.aspxhttps://support.ansys.com/AnsysCustomerPortal/en_ushttps://support.ansys.com/portal/site/AnsysCustomerPortal/template.ansyssupportcontact?vgnextoid=9f3f709c3a1a6310VgnVCM10000036c9790aRCRD

1. Installing ANSYS Products in a Microsoft HPC Cluster

1. Install ANSYS Fluent, CFX or Mechanical on the head node ONLY of the Microsoft Server HPC cluster. Thedefault installation directories are as follows:

Fluent:C:\Program Files\ANSYS Inc\v160\fluent

CFX:C:\Program Files\ANSYS Inc\v160\CFX

Mechanical:C:\Program Files\ANSYS Inc\v160\ansys

It is not necessary to install the solver on the compute nodes.

2. Ensure that the Microsoft HPC user account has Read & Execute permissions for this directory. Typically,it is sufficient to add DOMAIN USERS to the list of users that have access to submit jobs to the computecluster.

When using the ANSYS installer to install a solver (Fluent, CFX, Mechanical, Polyflow), RSM and Workbenchwill be installed also.

2. Configuring RSM on the Cluster Head Node

1. Launch the RSM Setup Wizard as follows:

Go to Start > All Programs > ANSYS 16.0 > Remote Solve Manager.

Right-click on RSM Setup Wizard 16.0 and select Run as Administrator from the context menu.

2. Click Next. Complete the steps presented by the wizard, using the sections that follow as a guide.

ANSYS Release 16.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential inform-ation of ANSYS, Inc. and its subsidiaries and affiliates.2

Configuring Remote Solve Manager (RSM) to Submit Jobs to a Microsoft HPC Cluster

Specifying Machine and Cluster Information

1. On the Machine Information screen, select Yes, I am setting up a head node of a cluster as RemoteSolve Manager.

2. Set the Cluster Type to Windows HPC.

3. To allow for auto-configuration of Workbench, leave Configure ANSYS Workbench when starting RSMservices checked.

4. Click Next. If you opted to configure ANSYS Workbench when starting RSM services, the HPC SetupPrerequisites page will prompt you to cache your password with HPC:



Configuring RSM on the Cluster Head Node

Once your password has been cached, click Next.

5. On the RSM Services page, click Start Services.



Once the services have been started, click Next.

Adding a Compute Server

1. On the Define Compute Servers screen, select Yes to specify that you want to define a new ComputeServer, then click Next.




2. On the Select a Compute Server screen, select Define a New Compute Server, then click Next.

3. On the Identify Machine screen, enter a Machine Name or IP Address for the server. This must be theactual computer name or IP address of the head node. In this example well enter headnode.



4. Enter a Display Name for the server. This can be any name that makes sense for you. In this example wellenter MS Compute Server.

5. On the Set Cluster Information screen, specify whether you want to run jobs from a network share orfrom the local disk, then click Next. In this example well select Network Share.




6. On the next Set Cluster Information screen, enter the UNC path for your Shared Cluster Directory. Thisis the directory that is shared out to all the cluster nodes from the head node. In this example well usethe shared Temp directory as the shared cluster directory, so well enter \\Headnote\Temp as our path.

Click Next.

7. On the Job Submission Settings screen, specify the Maximum Number of Jobs that can run concurrentlyon this Compute Server, then click Next.

8. On the Save Compute Server Settings screen, select Yes, save all changes to save your ComputeServer settings, then click Next.



9. On the Set up Compute Server screen, specify whether you want to auto-configure Compute Serverdirectories. In this example well select Yes, automatically configure directories, then click Next.

10. On the Additional Compute Servers screen, specify whether you want to create or modify anotherCompute Server. In this example well select No, then click Next.

Adding a Queue

1. On the Define Queues screen, select Yes to define a new or modify and existing queue, then click Next.




2. On the Select Queue screen, specify whether you want to create a new queue or modify one already inlist. In this example well select Define a new Queue, then click Next.

3. On the Queue Information screen, enter a Name for the queue. In this example well enter MS ComputeCluster Queue. The Compute Server you added previously (MS Compute Server, in this example)appears in the list of Compute Servers. Select its check box to assign it to the new queue. Click Next.



4. On the Additional Queues screen, specify whether you want to define or modify another queue. In thisexample well select No, then click Next.




Defining Accounts

1. On the Define Accounts screen, specify whether or not you want to define new accounts or modifypasswords. In this example well select Yes, then click Next.

2. On the Select Account screen, select an existing account to modify or specify that you want to define anew account. In this example well select Define a new account, then click Next.



3. On the Define Account screen, enter the Username and Password that you use to log into your Windowsmachine, then confirm your password. Click Next.




4. On the Define More Accounts screen, specify if you want to define more accounts. In this example wellselect No, then click Next.

Testing the Connection

1. On the Test Compute Servers screen, click the Queues drop box and select the queue that you want totest.

2. Click Start Test.



If the test succeeds, the Test Status will be Finished. If the test fails, the Test Status will be TestFailed. Check over the steps to make sure that you followed all steps correctly. You can also checkTroubleshooting RSM Issues (p. 15) for information on adding firewall ports and so on.

3. Click Next

4. On the Setup is Complete screen, click Finish.

3. Troubleshooting RSM Issues

Refer to the following topics should you encounter any issues with RSM.3.1. Gathering RSM Job Logs for Systems Support3.2. Issue:My Computer Disabled in RSM Manager3.3. Configuring Multiple Network Cards (NIC)3.4. Disabling IPv63.5. Issue: Cannot resolve localhost3.6. Disabling Microsoft User Account Control (UAC)3.7. Common Errors Found in RSM Job Log

3.1. Gathering RSM Job Logs for Systems Support

When a job fails, the job log can provide the support staff with valuable debugging information.

1. Open up the Remote Solve Manager (RSM Admin).

2. Select the Compute Server that you set up.



Troubleshooting RSM Issues

3. Select the failed RSM job in the job list view.

4. Right-click on the log in the lower right pane and select Debug Messages.

5. Right-click on the log again and select Save Job Report.

6. Attach the saved log to your Service Request.

3.2. Issue:My Computer Disabled in RSM Manager

Description: When you start RSM Manager, a red X appears on the My Computer icon:

Solution: Make sure that the RSM services on the manager machine (in other words, the head node)were started as Administrator.

For Windows, you must either have Windows administrative privileges on the Solve Manager, have RSMadministrative privileges (as a member of the RSM Admins user group), or launch the RSM Admin byright-clicking on it and selecting Run as administrator.

1. Log in as Administrator.

2. On the machine where RSM is set up, open a Command Prompt and change the directory (cd) toC:\Program Files\Ansys Inc\v160\RSM\bin.

3. Type AnsConfigRSM.exe -mgr svr and press Enter.



Creating an RSM Admins Group

In Windows create a group called RSM Admins and add the user to the group that needs permissionsto configure RSM.

1. Right-click on Computer and select Manage.

2. In the Computer Management dialog, expand Local Users and Groups.

3. Right-click on the Groups folder and select New Group.

4. In the New Group dialog, enter RSM Admins as the Group Name and add members by clicking Add.

5. In the Select Users, Computers, Service Accounts, or Groups dialog, type a user name in the editingwindow and then click Check Names to search for a matching name in the current domain. When found,the user name will be displayed in full syntax in the editing window.

6. Click Create to create the new group.

Dealing with Firewalls

If you have a local firewall turned on for the server and/or RSM Client machines, you will need to addtwo ports to the Exceptions List for RSM:

Add port 8160 to Ans.Rsm.SHHost.exe

Add port 9160 to Ans.Rsm.JMHost.exe

Additional Things to Check

1. Make sure that you can ping all of the nodes that you want to use.

2. Make sure you have enabled file and printer sharing.

3.3. Configuring Multiple Network Cards (NIC)

If your Microsoft HPC Cluster head node is configured using multiple network cards and there is morethan one network defined, you must explicitly define the IP address of the head node. To do so, youmust edit a configuration file on the head node.

On the Client machine, ping the head node using the Fully Qualified Domain Name (FQDN). For example,open up a Command Prompt and type: ping headnode.domain.com (where headnode is theactual machine name of the head node). The ping command should return a statement similar to thefollowing:

Pinging headnode.domain.com [10.2.10.32] with 32 bytes of data:Reply from 10.2.10.32: bytes=32 time=56ms TTL=61

Note

Take note of the IP address (10.2.10.32 in the above example). You will need this address inthe steps that follow.




1. Go to the head node and navigate to C:\Program Files\Ansys Inc\v160\RSM\Config and locate theAns.Rsm.AppSettings.config file.

2. Open the file in a text editor.

3. Locate the Global appSettings section. If your text editor can show line numbers this sectionstarts on line 3.

4. On line 12, for , enter the machinescorrect IP address for the value. The correct IP address is the address seen in the output of a pingprogram from any remote machine to this machine using the Fully Qualified Domain Name.

The bolded line in the sample code below shows what the line looks like using our example IPaddress of 10.2.10.32:

Sample hosts file

# Copyright (c) 1993-2009 Microsoft Corp.## This is a sample HOSTS file used by Microsoft TCP/IP for Windows.## This file contains the mappings of IP addresses to host names. Each# entry should be kept on an individual line. The IP address should# be placed in the first column followed by the corresponding host name.# The IP address and the host name should be separated by at least one# space.## Additionally, comments (such as these) may be inserted on individual# lines or following the machine name denoted by a '#' symbol.## For example:## 102.54.94.97 rhino.acme.com # source server# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.127.0.0.1 localhost

# ::1 localhost

3.6. Disabling Microsoft User Account Control (UAC)

1. In Windows, select Control Panel > User Accounts > Change User Account Control settings.

2. To turn off UAC, move the slider to the Never notify position, and then click OK.

3.7. Common Errors Found in RSM Job Log

Exception from TaskHost: A required privilege is not held by the client

Description: The following error is reported in the RSM log file:

Compute Server running as: DOMAIN\usernameLogged on user DOMAIN\usernameException from TaskHost: A required privilege is not held by the client ["C:\Program Files\ANSYS Inc\v160\RSM\bin\Ans.Rsm.TaskHost.exe"]Caught exception from script: [0x80004005] A required privilege is not held by the client ["C:\Program Files\ANSYS Inc\v160\RSM\bin\Ans.Rsm.TaskHost.exe"]

Caught exception at user logon: A required privilege is not held by the client

Description: In the Windows Task Manager, on the Processes page, RSM is running as a user and notas SYSTEM. This is incorrect. To submit jobs to another Windows machine the processes need to berunning as SYSTEM.

Solution: Start the RSM services manually:

1. Log in as Administrator.

2. On the machine where RSM is set up, open a Command Prompt and change the directory (cd) toC:\Program Files\Ansys Inc\v160\RSM\bin.

3. Type AnsConfigRSM.exe -mgr svr and press Enter.

Caught exception at user logon; logon failure: unknown user name or bad password/ Account Password not Provided

Description: The following error is reported in the RSM log file:




Compute Server running as: DOMAIN\usernameCaught exception at user logon: A required privilege is not held by the client.OrAccount Password not Provided

Solution:: Right-click on My Computer in RSM and select Set Password.

In the Set Password dialog box, if your DOMAIN and username match the one shown simply pressEnter.

If the Windows client account is different from the HPC Windows account, you will need to set up analternate account. You can do this after you have cached your primary Windows account with RSM byselecting Set Password again, but this time enabling the This is the alternate account check box beforeentering the credentials for the HPC Windows account. You can also set up an alternate account fromthe Accounts dialog box (right-click on My Computer in RSM and select Accounts).

Error: A connection attempt failed because the connected party did not properly re-spond after a period of time. Or,

No connection could be made because the target machine actively refused it.

If you have a local firewall turned on for the server and/or RSM Client machines, you will need to addtwo ports to the Exceptions List for RSM:

Add port 8160 to Ans.Rsm.SHHost.exe

Add port 9160 to Ans.Rsm.JMHost.exe

If that is not the case, check to see if IPv6 is enabled and if it is, disable it. See Disabling IPv6 (p. 18)for details.

You can disable it partly by going to your network properties for the NIC card and unchecking the IPv6box, but you also have to further disable it in the registry.

Failed to create Script Task: Access to the path is denied.

Make sure that the directory that the error is referencing is available on all nodes, that it is shared, andthat all users have read/write access to that directory.

Caught exception from script: Failed to find the TCP port from TaskHost run.

Solution 1: Restart the RSM services.

1. Go to Control Panel > System and Security > Administrative Tools > Services.



2. Restart the ANSYS RSM JHost and ANSYS RSM ScriptHost services.

Solution 2: Check for firewalls. Refer to Dealing with Firewalls (p. 17).

The submission of the requested job has been cancelled because the Solve Manager. seems not fully initialized.

Solution: This is a dual network card issue. For instructions see Configuring Multiple Network Cards(NIC) (p. 17).

You may also want to check for multiple RSM admins of the same version running concurrently.




Configuring Remote Solver Manager (RSM) to Submit Jobs to a LinuxLSF, PBS, Torque with Moab, or UGE (formerly SGE) Cluster

Introduction

This tutorial steps you through the configuration of ANSYS Remote Solve Manager (RSM), solvers, andWorkbench so that solve jobs can be submitted to a Linux LSF, PBS, Torque with Moab, or UGE (formerlySGE) cluster via RSM.

In this tutorial, RSM is configured using the Remote Solve Manager Setup Wizard. For a quick-startguide on using the wizard, select Start > All Programs > ANSYS 16.0 > Remote Solve Manager >Readme - RSM Setup Wizard 16.0.

If you wish to set up RSM manually, refer to the RSM documentation.

Assumptions


You have installed and configured the Linux job scheduler and the compute nodes can access the clusterhead node. If your cluster is not configured properly please contact your hardware vendor or a third partyconsultant for assistance.

You have passwordless ssh set up between the head node and compute nodes. Consult an IT professionalfor assistance with setting up passwordless ssh.

You know the machine name of the head node on the Linux cluster.

You are able to install and run ANSYS, Inc. products, including Licensing on Windows systems. For informationon installation and licensing, see the tutorials on the Downloads menu of the ANSYS Customer Portal.

If you have any problems with, or questions about the installation process, go to the Support page ofthe ANSYS Customer Portal and submit a support request.

1. Installing ANSYS Products in a Linux Cluster

Install ANSYS Fluent, CFX or Mechanical on the head node only. It is not required that you install ANSYSproducts on the compute nodes, but you must export the ANSYS Inc file system so that all computenodes and client machines have access to the installation.

Note that when using the ANSYS installer to install a solver (Fluent, CFX, Mechanical, Polyflow), RSMand Workbench will be installed also.

1.1. Exporting the /ansys_inc Directory

If you are installing an ANSYS, Inc. product on a file server, you need to export the /ansys_inc dir-ectory to all client machines so that all users can access the program. You will also need to share the


https://support.ansys.com/AnsysCustomerPortal/en_ushttps://support.ansys.com/portal/site/AnsysCustomerPortal/template.ansyssupportcontact?vgnextoid=9f3f709c3a1a6310VgnVCM10000036c9790aRCRD

ANSYS directory if the machine you are installing on does not have a DVD/USB drive or an internetconnection for downloading files and you need to share files with a machine that does have a DVD/USBdrive or internet connection.

1. Export the /ansys_inc directory by adding the following line to the /etc/exports file:

/usr/ansys_inc

2. The default behavior on Linux provides read-only access from all clients. To enable read/write permissionfrom all clients, use *(rw):

/usr/ansys_inc *(rw)

Alternatively, if the installing user is root, use:

/usr/ansys_inc *(rw,no_root_squash)

3. Run:exportfs a

4. On all client computers, mount the /ansys_inc directory.

5. If you perform a network install where you want the clients to be able to modify the licensing configuration,you need to consider the NFS write options for the exported file system as shown in the above examples.You also need local permissions to the licensing directory (/shared_files/licensing/) if you wantto be able to create the install_licconfig.log that the license configuration produces.

6. If you need to transfer the files from a Windows machine with a DVD drive to a Linux machine withoutone, copy the DVD contents using a Samba mount or some other transfer method that is safe to usebetween Windows and Linux.

7. If sharing the ANSYS directory between Linux machines, you must use the same mount point for boththe client and server. For example, if you installed to a file server in a directory named /apps/ansys_incand you did not choose the symbolic link to /ansys_inc, then you must mount this directory on theclient machine using /apps/ansys_inc as the mount point. If you did choose the symbolic link to/ansys_inc during installation on the file server, you must either use /ansys_inc as the mount pointon the client or you must create a symbolic link to /ansys_inc on the client machine. (The symboliclink is created by default during installation if you installed as root.)

2. Configuring RSM on the Cluster Head Node

In this section:2.1. Creating an rsmadmins Group and User Accounts2.2. Using the RSM Setup Wizard to Configure RSM

2.1. Creating an rsmadmins Group and User Accounts

Only users in an rsmadmins group can perform RSM Admin tasks and run basic tests using the RSMSetup Wizard. There are two ways in which an rsmadmins group and user accounts can be created:

Manually:

1. Log in as ROOT (this is required initially to start the RSM daemons) and manually create a group calledrsmadmins.

2. Add users to the group who will is responsible for configuring RSM Admin.


Configuring Remote Solver Manager (RSM) to Submit Jobs to a Linux LSF, PBS,Torquewith Moab, or UGE (formerly SGE) Cluster

Automatically:

1. If you started the daemons as ROOT, log out as root. A local rsmadmin account and rsmadmins groupare automatically created when the daemons are started as ROOT.

2. If other users will be configuring RSM Admin, add their user names to the rsmadmins group (this alsorequires ROOT permission). You can log out as root now.

2.1.1. About the rsmadmin Account

Administrative privileges for RSM configuration and setup can be root or non-root. Non-root adminis-trative privileges means that the user is added to the rsmadmins user group. As a member of thisgroup, you have administrative, non-root permissions, which are necessary for certain parts of the setup.When RSM services are installed and started as daemon services by ANSYS-provided service scripts, ifthe rsmadmins user group and rsmadmin account do not already exist, the rsmadmins group isautomatically created on the RSM Manager machine and an rsmadmin account is added to the group.This account can then be used to add additional users to the group.

If the user prefers to start the non-daemon services from the RSM Setup Wizard (as opposed to installingand starting the services as daemons with a root account), then a user account from the rsmadminsuser group must be used. Note that if the RSM services are not installed as daemons, the rsmadminsuser group is not automatically created. Therefore, in order to start non-daemon services via the wizard,prior to running the wizard your IT department must:

1. Create the rsmadmins user group manually.

2. Add the users who will be running/starting non-daemon services to the rsmadmins group.

Note

If you start the services with an rsmadmins non-root user account, the service will be runby that account in non-daemon mode. Root user privileges are required for starting RSMservices as daemons. If you start RSM services as daemons, any non-daemon services will bekilled.

2.2. Using the RSM Setup Wizard to Configure RSM

Follow the steps below to launch the RSM Setup Wizard and configure RSM.2.2.1. Launching the RSM Setup Wizard2.2.2. Specifying Machine and Cluster Information2.2.3. Adding a Compute Server2.2.4. Adding a Queue2.2.5. Defining Accounts2.2.6.Testing the Connection

2.2.1. Launching the RSM Setup Wizard

1. If you logged in as ROOT to start the daemons, log out as ROOT. Log in as the user account that was addedto the rsmadmins group.

2. Open a terminal window,cd to the /ansys_inc/v160/RSM/Config/tools/linux directory andrun rsmwizard. For a quick-start guide on using the wizard, navigate to the /an-sys_inc/v160/RSM/bin directory and open rsm_wiz.pdf.




2.2.2. Specifying Machine and Cluster Information

1. On the Welcome screen, click Next.

2. On the Machine Information screen:

a. Select Yes, I am setting up a head node of a cluster as Remote Solve Manager.

b. Set Cluster Type to your Linux job scheduler.

c. Click Next.



3. On the RSM Services screen, click Start Services.

4. Click Next.




2.2.3. Adding a Compute Server

1. On the Define Compute Servers screen:

a. When asked if you want to define new or modify existing Compute Servers, select Yes.



b. Click Next.

2. On the Select a Compute Server screen:

a. Select Define a new Compute Server.




b. Click Next.

3. On the Identify Machine screen:

a. Type in a Machine Name or IP Address for the server. This must be the actual computer name orIP address of the head node. In this example, we will use:headnode

b. Type in the Display Name. This can be any name that makes sense for you.



c. Click Next.

4. On the Set Cluster Information screen:

a. Specify whether you want to run jobs from a network share or from the local disk. In this example,we will select Network Share.




b. Click Next.

5. On the second Set Cluster Information screen:

a. Enter the local path for your Shared Cluster Directory. This is the directory that is shared out andmounted to all the cluster nodes from the head node.

b. Enter the name of the network share. In this example, we will use the shared temp directory/Headnode/Temp.

c. Click Next.

6. On the Job Submission Settings screen:

a. Specify the Maximum Number of Jobs that can run concurrently on this Compute Server.



b. Click Next.

7. On the Save Compute Server Settings screen:

a. Select Yes, save all changes to Compute Server settings.

b. Click Next.

8. On the Setup Compute Server screen:




a. Specify whether you want to auto-configure Compute Server directories. In this example, we willselect Yes, automatically configure directories.

b. Click Next.

9. On the Additional Compute Servers screen:

a. Specify whether you want to create or modify another Compute Server. In this example, we will selectNo.

b. Click Next.

2.2.4. Adding a Queue

1. On the Define Queues screen:

a. Select Yes to define a new queue.



b. Click Next.

2. On the Select Queue screen:

a. Specify whether you want to create a new queue or modify one already in list. In this example, wewill select Define a new Queue.




b. Click Next.

3. On the Queue Information screen:

a. Enter a Name for the queue. In this example, we will enter Linux Cluster Queue. For yourconfiguration you can enter the actual cluster queue name that will be used to run jobs.

b. The Compute Server you added previously (Linux Cluster, in this example) appears in the listof compute servers. Select its check box to assign it to the new queue.



c. Click Next.

4. On the Additional Queues screen:

a. Specify whether you want to define or modify another queue. In this example, we will select No.




b. Click Next.

2.2.5. Defining Accounts

1. On the Define Accounts screen:

a. Select Yes to define or modify accounts.

b. Click Next.

2. On the Select Account screen:

a. Select an existing account to modify or specify that you want to define a new account. In this example,we will select Define a new account.



b. Click Next.

3. On the Define Account screen:

a. Enter the Username that you use to log into your Linux machine.

b. Enter and confirm the Password that you use to log into your Linux machine.

Note

If you are going to later run a job from Windows to this Linux cluster machine, youmay need to also create an alternate Linux account that is associated with yourprimary Windows account. For details refer to the Resolution in the troubleshootingtopic, Caught exception at user logon; logon failure: unknown user name or badpassword. Account password not provided. (p. 45)




c. Click Next.

4. On the Define More Accounts screen:

a. Specify if you want to define more accounts. In this example, we will select No.

b. Click Next.

2.2.6. Testing the Connection

On the Test Compute Servers screen:

1. In the Queues drop-down, select the queue that you want to test.

2. Click Start Test.

If the test succeeds, the Test Status will be Finished. If the test fails, the Test Status will be TestFailed. Check over the steps to make sure you followed all steps correctly. You can also checkTroubleshooting RSM (p. 41) for information on adding firewall ports, and so on.

3. Click Next.

4. On the Setup is Complete screen, click Finish.



3. Starting Automatic Startup (Daemon) Services for Linux Red Hat orSuSE

To install RSM services as daemon services, run either the rsmconfig script or the install_daemonscript, as follows:

1. Log into a Linux account with administrative privileges.

2. Ensure that Ans.Rsm.* processes are not running.

3. Open a terminal window in the RSM/Config/tools/linux directory.

4. Enter the script into the terminal window.

5. Add the appropriate command line options (-mrg,-svr, or -xmlrpc).

6. Run the command.

Examples

The two examples below show the command line used to configure the Manager and Compute Serverservice daemons via either the rsmconfig script or the install_daemon script.

tools/linux#> ./rsmconfig -mgr -svr

tools/linux#> ./install_daemon -mgr -svr

Once the daemon service is installed, the RSM service will be started automatically without rebooting.The next time when the machine is rebooted, the installed RSM service will be started automatically.

3.1. Verifying that Daemon Services are Started

To verify that the automatic boot procedure is working correctly, reboot the system and check to seethat the services are running by typing the appropriate ps command and looking for Ans.Rsm in theresulting display:

ps aux | grep Ans.Rsm

4. Troubleshooting RSM

Refer to the following topics should you encounter any issues with RSM.4.1. Gathering RSM Job Logs for Systems Support4.2. Issue:My Computer Disabled in RSM Manager4.3. Configuring Multiple Network Cards (NIC)4.4. Disabling IPv64.5. Cannot Resolve localhost4.6. Common Errors Found in RSM Job Log

4.1. Gathering RSM Job Logs for Systems Support

When a job fails, the job log can provide the support staff with valuable debugging information.

1. Open up the Remote Solve Manager (RSM Admin).

2. Select the Compute Server that you setup.



Troubleshooting RSM


4. Right-click the log in the lower right pane and choose Debug Messages.

5. Right-click the log and choose Save Job Report.

6. Attach the log to the Service Request.

4.2. Issue:My Computer Disabled in RSM Manager

Problem Description: When you start the RSM Manager, a red X appears on the My Computer icon:

Resolution 1: Make sure the RSM services were started as Administrator.

1. Log in as superuser or a member of the rsmadmins group.

2. Open a terminal window and log in to the cluster head node that is running RSM.

3. Type cd /ansys_inc/v160/RSM/Config/tools/linux

4. Type ./rsmmanager start

5. Type ./rsmserver start

Resolution 2: Check for firewalls.

If you have a local firewall turned on for the server and/or RSM Client machines, you will need to addtwo ports to the Exceptions List for RSM, as follows:



1. Add port 8160 to (Ans.Rsm.SHHost.exe).

2. Add port 9160 to (Ans.Rsm.JMHost.exe).

Other Things to Check:

1. Make sure you can ping all of the nodes you want to use.

2. Make sure you have enabled file and print sharing.

4.3. Configuring Multiple Network Cards (NIC)

If the head node is configured using multiple network cards and there is more than one network defined,you must explicitly define the IP address of the head node. To do so, you must edit a configuration fileon the head node.

On the Client machine, ping the head node using the fully qualified domain name. For example, opena Command Prompt and enter:

ping headnode.domain.com

(where headnode is the actual machine name of the head node).

The ping command should return a statement similar to the following:

Pinging headnode.domain.com [10.2.10.32] with 32 bytes of data:Reply from 10.2.10.32: bytes=32 time=56ms TTL=61

Note

Record the IP address (10.2.10.32 in the above example). You will need this address in thesteps that follow.

1. Open the file /ansys_inc/v160/RSM/Config/Ans.Rsm.AppSettings.config.

2. Locate the Global appSettings section. If your text editor can show line numbers this sectionstarts on line 3.

3. On line 12, for , enter the machinescorrect IP address for the value. The correct IP address is the address seen in the output of a pingprogram from any remote machine to this machine using the Fully Qualified Domain Name.

The bolded line in the sample code below shows what the line looks like using our example IPaddress of 10.2.10.32:

5. Restart the RSM Services: open a terminal window in the [RSMInstall]/Config/tools/linuxdirectory and run the following commands:

./rsmmanager restart

./rsmserver restart

Note

1. When the RSM services are installed and started as daemon services by ANSYS-provided servicescripts, an rsmadmins administrative user group is automatically created on the Solve Managermachine. An rsmadmin user account is created in the new user group. This account has admin-istrative, non-root privileges and can be used to perform RSM administrative and configurationtasks via the wizard on Linux.

2. On Linux, to provide additional users with RSM administrative privileges, you must add themto the rsmadmins user group.

4.4. Disabling IPv6

Contact your IT professionals and/or consult your Linux manuals or do an Internet search for instructionson how to do this based on your operating system.

4.5. Cannot Resolve localhost

In the hosts file:

1. Make sure 127.0.0.1 is not commented out with a # sign. If it is, remove the # sign.

2. If :: localhost is not commented out, comment it out with a # sign.

Sample hosts file:

# 102.54.94.97 rhino.acme.com # source server# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself. 127.0.0.1 localhost# ::1 localhost

4.6. Common Errors Found in RSM Job Log

The following sections describe common errors and how to resolve them:4.6.1. Caught exception at user logon: A required privilege is not held by the client.4.6.2. Caught exception at user logon; logon failure: unknown user name or bad password. Account passwordnot provided.4.6.3. Connection Error/No connection could be made4.6.4. Failed to create Script Task: Access to the path is denied.4.6.5. Caught exception from script: Failed to find the TCP port from TaskHost run.4.6.6.The submission of the requested job has been cancelled because the Solve Manager . seems not fullyinitialized.4.6.7. Failed to create working directory on execution nodes via node share/mount



4.6.1. Caught exception at user logon: A required privilege is not held by the client.

Resolution: Start the RSM Services manually.

1. Log in as superuser or a member of the rsmadmins group.

2. Open a terminal window and log in to the machine that is running RSM.

3. Type :cd /ansys_inc/v160/RSM/Config/tools/linux

4. Type:./rsmmanager start

5. Type:./rsmserver start

4.6.2. Caught exception at user logon; logon failure: unknown user name or badpassword. Account password not provided.

You see one of the following errors in the RSM log file:

Compute Server running as: usernameCaught exception at user logon: A required privilege is not held by the client.

or

Compute Server running as: usernameAccount Password not Provided

Resolution:

Right-click on My Computer in RSM Admin it and choose Set Password as your password is not set.

For the Set Password dialog box, if your name matches the one shown, press Enter.

If jobs will be submitted from a Windows client, and that account is different from the Linux account,you will need to set up an alternate account. You can do this after you have cached your primary Win-dows account with RSM on your Windows client by selecting Set Password again, but this time enablingthe This is the alternate account check box before entering the credentials for the Linux account. Youcan also set up an alternate account from the Accounts dialog box (right-click on My Computer inRSM and select Accounts). If running on Linux, you do not need to enter a DOMAIN, just your usernameand password.

4.6.3. Connection Error/No connection could be made

Problem: You see one of the following errors:

Connection Error A connection attempt failed because the connected party did not properly respond after a period of time.

or

No connection could be made because the target machine actively refused it.

Resolution: If you have a local firewall turned on for the server and/or RSM Client machines, you willneed to add two ports to the Exceptions List for RSM, as follows:





Troubleshooting RSM

If you do not have a local firewall turned on, check to see if IPv6 is enabled; if it is, disable it.

4.6.4. Failed to create Script Task: Access to the path is denied.

Make sure all users have read/write access to the directory that the error is referencing, that the directoryis available on all nodes, and that it is shared.

4.6.5. Caught exception from script: Failed to find the TCP port from TaskHost run.

Resolution 1: Restart the RSM services.

On Linux you can stop the RSM services manually by running the appropriate service script with thecommand line option stop. The examples below illustrate how to stop the RSM services manually:

./rsmmanager stop

./rsmserver stop

You can start the RSM services manually by running the appropriate service script with the commandline option start. The examples below illustrate how to start each of the RSM services manually:

./rsmmanager start

./rsmserver start

Resolution 2: Check for Firewalls.

If you have a local firewall turned on for the server and/or RSM Client machines, you will need to attachtwo ports to the Exceptions List for RSM, as follows:



Try flushing iptables. Consult your MAN pages for instructions on how to do this.

Resolution 3: Check the permissions on the RSM scratch directory.

Check the permissions on the RSM scratch directory and ensure that all users have write access to it.



4.6.6. The submission of the requested job has been cancelled because the SolveManager . seems not fully initialized.

Resolution:

This may be a dual NIC issue. Also check for multiple RSM admins of the same version running concur-rently. See the section Multiple Network Interface Cards (NIC) Issues in the Remote Solve Manager (RSM)documentation for instructions.

4.6.7. Failed to create working directory on execution nodes via node share/mount

This is probably a case of attempting to use RSH for scratch creation when the cluster is not set up forit; use SSH instead.

In the RSM Properties, General tab, check the box Use SSH protocol for inter and intra-node com-munication (Linux only) and that should resolve the issue.



Troubleshooting RSM

Submitting CFX, Fluent and Mechanical Jobs to a Linux or MicrosoftHPC Cluster

This tutorial shows you how to configure Workbench to submit solve jobs via RSM, and provides instruc-tions on submitting CFX, Fluent and Mechanical jobs from Workbench to a Linux or Windows cluster.

In this tutorial:1. Configuring RSM on a Windows Client Machine Prior to Submitting Jobs to a Linux or Windows Cluster2. Submitting a CFX Job from Workbench to a Linux or Windows Cluster3. Submitting a Fluent Job from Workbench to a Linux or Windows Cluster4. Submitting a Mechanical Job from Workbench to a Linux or Windows Cluster5.Troubleshooting Job Failures

1. Configuring RSM on a Windows Client Machine Prior to SubmittingJobs to a Linux or Windows Cluster

Follow the steps below to register your RSM credentials in Workbench.

1. Install ANSYS, Inc. products on each Client machine that will be submitting RSM jobs the cluster.

2. On the Client machine, open ANSYS Workbench (Start Menu All Programs ANSYS 16.0 Work-bench 16.0).

3. Choose Tools Enter Credentials for Remote Solve Manager.



4. Enter your password in the Set Password dialog box.

If you are submitting a job to a Linux manager or compute server where the Windows client logoncredentials (user name or password) are different than the credentials used to log on to the Linuxmanager or compute server, you will need to set up an alternate account.

To do this after you have cached your primary Windows account with RSM:

a. Open the Set Password dialog box again.

b. Enable the This is the alternate account check box.

c. Enter the user name and password for your alternate account to log on to the remote manager orcompute server, then click OK. This launches the Alternate Account Settings dialog box:


Submitting CFX, Fluent and Mechanical Jobs to a Linux or Microsoft HPC Cluster

d. Select the manager or compute server that you want to apply the alternate account to, then clickDone.

Proceed to the sections that follow to learn how to send your job to your Linux or Windows cluster.

2. Submitting a CFX Job from Workbench to a Linux or Windows Cluster

1. Open ANSYS Workbench (Start Menu All Programs ANSYS 16.0 Workbench 16.0).

2. Open your CFX project.

3. In the CFX system, right-click the Solution cell and select Properties.



Submitting a CFX Job from Workbench to a Linux or Windows Cluster

4. In the Solution Properties view, set Solution Process properties as follows:

a. Set Update Option to Remote Solve Manager.

b. For Solve Manager, type the name of the Manager that will be used. (If you do not know the nameof the Solve Manager, contact your System Administrator for this information.)

c. For Queue, enter the name of the queue that will be used. (If you do not know the name of theQueue, contact your System Administrator for this information.)

d. For automatic downloading of progress information, verify that Download Progress Informationis set to Always Download.

e. Leave the Download Progress Information at the default of 120 seconds (or a different value de-pending on how frequently you would like the solver to query RSM for output files in order to displayprogress). Note that if the job finishes before the first interval is reached, you will not see progressresults until the end of the job.

f. Set Execution Mode to Parallel.

5. For Number of Processes, specify the number of processes to be used.



6. Right-click the Solution cell and select Update.

3. Submitting a Fluent Job from Workbench to a Linux or Windows Cluster


2. Open your Fluent project.

3. In the Fluent system, right-click the Solution cell and select Properties.



Submitting a Fluent Job from Workbench to a Linux or Windows Cluster

4. In the Solution Properties view, set Solution Process properties as follows:

a. Clear Use Setup Launcher Settings.

b. Set Update Option to Remote Solve Manager.

c. For Solve Manager, type the name of the Manager that will be used. (If you do not know the nameof the Solve Manager, contact your System Administrator for this information.)

d. For Queue, enter the name of the queue that will be used. (If you do not know the name of theQueue, contact your System Administrator for this information.)

e. Verify that Download Progress Information is selected.

f. Set the Progress Download Interval to the default of 120 seconds (or a different value dependingon how frequently you would like the solver to query RSM for output files in order to display progress).Note that if the job finishes before the first download interval is reached, you will not see progressresults until the end of the job.

g. Set Execution Mode to Parallel.

h. For Number of Processes, specify the number of processes to be used.



5. Right-click the Solution cell and select Update.

4. Submitting a Mechanical Job from Workbench to a Linux or WindowsCluster


2. Add a Mechanical system and assign a geometry, establish all necessary loads, and so on.

3. On the analysis system on the Project Schematic, double-click either the Model or the Setup cell to launchMechanical.

4. In the Mechanical window, select Tools Solve Process Settings.



Submitting a Mechanical Job from Workbench to a Linux or Windows Cluster

5. In the Solve Process Settings dialog box, click Add Remote.

6. In the Rename Solve Process Settings dialog box that opens:

a. Enter a Solve Process Setting Name of your choosing.

b. Click OK. The Rename Solve Process Settings dialog box closes.

7. In the Solve Process Settings dialog box:

a. Select the solve process setting you just specified from the list on the left.

b. Under Computer Settings, enter the machine name of the Solve Manager. (If you do not know thename of the Solve Manager, contact your System Administrator for this information.)



c. For Queue, enter the name of the queue that will be used. (If you do not know the name of theQueue, contact your System Administrator for this information.)

d. Click Advanced.

8. On the Advanced Properties dialog box:

a. Select the Distribute Solution (if possible) option.

b. Specify the number of processors.

c. Click OK. The Advanced Properties dialog box closes.

9. In the Solve Process Settings dialog box, click OK. The dialog box closes and the solve process setup iscomplete.



Submitting a Mechanical Job from Workbench to a Linux or Windows Cluster

10. In Mechanical, finish setting up your analysis. When the model is set up and ready to solve, open/launchMechanical and select the Solve toolbar button drop-down arrow. You will see the solve process nameyou just defined (in this example, Cluster). Select that process.

11. The solve commences. When the solution has completed, the Solution branch and the items underneathit in the project tree will each have a down-arrow next to them.

12. Right-click Solution and select Get Results to bring the solution items to the local machine.



5. Troubleshooting Job Failures

If your job fails for any reason check the RSM logs and send the failed job log to ANSYS Support. Attachthe log to your Service Request as follows:

1. Open the Remote Solve Manager (RSM Admin):

a. Choose Start Menu All Programs ANSYS 16.0 Remote Solve Manager RSM 16.0, thenright-click the shortcut and choose Run as Administrator.

b. From the Tools menu choose Options. In the Name field type the name of the Solve Manager. (Ifyou do not know the name of the Solve Manager, contact your System Administrator for this inform-ation.)

c. Click Add, then click OK.


3. Right-click on the log in the lower right pane and select Debug Messages.

4. Right-click the log and choose Save Job Report.

5. Attach the log to your Service Request.



Troubleshooting Job Failures

Remote Solve Manager Tutorial: Configuring Custom Client-SideCluster Integration R16.0

This tutorial walks you through process of configuring Remote Solve Manager (RSM) to use a CustomLinux Cluster using the Client-Side Integration technique. This should be used only if your environ-ment:

has special File Transfer requirements that RSM standard file transfer methods dont meet, such as usingHTTP file transfers that you want to integrate into RSM (or)

has restrictions on the installation of RSM services and is also an unsupported cluster type (that is, nota standard LSF/PBS/UGE/MS HPC cluster type).

If you have similar, but less restrictive, setups to the following, use the other simpler setupmethods listed for each case below:

You can install RSM services and file transfers can use RSM native or network file shares like Linux Sambaor Windows shares on your unsupported cluster type (server-side integration).

You cannot install RSM services but you are using a supported Linux cluster type (standard SSH setup).

The only special requirement for file transfers is SSH/SCP transfers to a supported Linux cluster type(standard SSH setup).

For more information on server-side integration, see Customizing Server-Side Integration in the RemoteSolve Manager User's Guide and/or review Remote Solve Manager Tutorial: Configuring Custom Server-Side Cluster Integration R160.

For more information on standard SSH setups, see Appendix B. Integrating Windows with Linux usingSSH/SCP in the Remote Solve Manager User's Guide.

This tutorial is not meant to replace the users guide; for more information on custom integration, seeCustom Cluster Integration Setup in Remote Solve Manager User's Guide.

If this scenario does not suit your needs, see the other tutorials available on the Tutorials and TrainingMaterials page of the ANSYS Customer Portal. For further information about tutorials and documentationon the ANSYS Customer Portal, go to http://support.ansys.com/docinfo.

You can follow this tutorial while actually configuring RSM. To do so, simply make the selections thatare pertinent to you or insert your specific information where noted.

Once youve tested your configuration, you can submit a Fluent, CFX, or Mechanical job to RSM.

1. Before You Begin


Both the Windows and the Linux machines are set up correctly on the network.


http://support.ansys.com/docinfo\h

You have properly set up passwordless SSH from the Client to the Linux cluster.

For help with setting up SSH, see Appendix B: Integrating Windows with Linux using SSH/SCPin the Remote Solve Manager User's Guide for instructions.

Both ANSYS Workbench and RSM have been installed on the Windows Client machine.

You are able run ANSYS, Inc. products on the Linux cluster by submitting a command line (i.e. the ANSYSinstall on the cluster has been verified).

For information on product and licensing installations, see the RSM tutorials on the Downloads pageof the ANSYS Customer Portal.

If you have any problems with, or questions about, the installation process, go to the Support page ofthe ANSYS Customer Portal and submit an online support request.

For further information about tutorials and documentation on the ANSYS Customer Portal, go to http://support.ansys.com/docinfo.

2. Setting Up the RSM Client and Manager

To set up the RSM, you will perform the following steps:2.1. Creating the RSM Compute Server for Custom Cluster Type Keyword2.2. Adding a Queue for this Compute Server to Use

2.1. Creating the RSM Compute Server for Custom Cluster Type Keyword

Perform the following steps on your Windows RSM Client machine to configure RSM to use a customclient-side integrated cluster. In this section, we are adding a Custom Linux cluster as the ComputeServer which can have user-programmed inputs.

1. Underneath the local Manager (My Computer) in the RSM tree view, right-click the Compute Serversfolder and select Add.

The Compute Server Properties dialog box is displayed.

2. On the General tab of the Compute Server Properties dialog box, set properties as follows:

a. For the Display Name property, enter a descriptive name for the Linux machine being defined as aCompute Server. This example will use Client Side Integration Example.

b. In this example, the Compute Server services will be on the same machine as the Manager. Both ofthem will run on your Client machine (My Computer), so we will set Machine Name to localhost.

c. Enable the This Compute Server is integrating with an HPC cluster check box.

d. Select Uses non-RSM communication to a remote cluster node (such as SSH).

e. Click the More >> button to view more options.


Remote Solve Manager Tutorial: Configuring Custom Client-Side Cluster IntegrationR16.0
http://support.ansys.com/docinfohttp://support.ansys.com/docinfo

f. If you do not have RSH enabled on the cluster, then check Use SSH protocol for intra node commu-nication. This means that the remote scripts will use SSH to contact other machines in the cluster.

g. (Optional) Increase the Maximum Number of Jobs to 5 or more.

3. On the Cluster tab, set properties as follows:

a. Set up the Cluster Node and Account Name in order to access the Remote Linux Cluster.

b. Set the Cluster Type property. In this example, well select CUSTOM.

c. For the Custom Cluster Type property, enter a short, descriptive name. This is your keyword and willneed to be appended to some filenames later, so try to keep it simple; for ease of use, it should notcontain spaces. For this example, well use CUS_CLIENT.



Setting Up the RSM Client and Manager

4. On the File Management tab, set properties as shown below. For more information on file managementand directory handling, see Compute Server Properties Dialog: File Management Tab in the Remote SolveManager User's Guide.

a. For the Remote Shared Cluster Directory property, enter the path to your central cluster file-stagingdirectory. This should be a directory that the cluster execution nodes share and all have mounted sothat every execution node can access the input files once they are moved there.

The Shared Cluster Directory is typically located on the machine defined on the General tab.However, in this example, the General tab specifies localhost. Since we have set up and aremodifying the remote Manager from the Client machine, the directory reference here will be tothe remote machine. The RSM job needs to find this shared directory on the remote machine.In this example, /path/to/shared/cluster/directory is a network share that all of thecluster nodes have mounted.

b. Select Transferred by an external mechanism (e.g. SSH).


Remote Solve Manager Tutorial: Configuring C

ANSYS Remote Solve Manager Tutorials

Documents

Transcript of ANSYS Remote Solve Manager Tutorials