The Simple Way to Put the Remote in ANSYS Remote Solve Manager (RSM)

Last time I introduced you to using RSM to submit to your local machine. This probably seemed pretty similar to the normal way of solving things but you can apply the same workflow to solving to remote computers too! Recall how ergonomic it was to solve with RSM from the last post and compare to how it normally goes on a remote computer:

  • Saving/Archiving the project or drilling down in the file structure to find specific files
  • Copying the files via network share, Dropbox or similar
  • Logging into the remote machine, starting the software, possibly figuring out how to run it in batch, opening your files and starting the solution process
  • Copying the results files back to your computer, deciding how & whether to overwrite and version them
  • Load results into the software

All of these steps are handled for you with RSM. When you don’t need to have a graphics card on a compute machine you can specialize it more towards computation, as noted on our Ansys Hardware Requirements Page

Setting this up just become both more simple and more complex with the R18. The major way it became simpler is that it doesn’t require you to join a Windows Domain, at least for a simple setup that runs on one remote computer. This means that you do not need to have complicated IT infrastructure just to take advantage of your compute resources. A motivated engineer with administrative access to the compute server can set this up on their own. For more complex configurations you will want to get IT involved, such as having multiple machines in a queue or distributed solves across computers.

Here is some terminology:

  • Remote Solve Manager: Integrates directly with Ansys and provides facilities for transferring simulation data between machines and solution monitoring. Meant to be the integration layer between Ansys and existing compute infrastructure.
  • Ansys RSM Cluster (ARC): Added in R18, ARC is the Ansys provided compute infrastructure in the event that you don’t already have a commercial queuing system, such as Microsoft HPC or LSF. Needs to be present when using RSM unless it is replaced by something else.
  • Master & Compute Nodes: ARC nodes can have master or compute roles, suitable for setting up a cluster of machines for distributed runs. For the purposes of this guide, the Master & Compute Nodes will be one and the same.
  • RSM Queue vs ARC Queue: Unfortunately, you will have to set up queues for both your queuing system, such as ARC, AND in RSM. This process is described as mapping cluster queues to RSM queues.
  • Cluster: For the purposes of this guide, each “Cluster” is a single machine. We’re punting on all the more complex setups!

Remote Machine Setup

You will only need to do this once. Afterwards, everyone who wants to submit to this machine just needs to follow the Local Machine Setup instructions further down.

Start an admin prompt

A lot of this will need to be done in the command line. Right click Start Menu -> Command Prompt and select Run As Administrator

For Linux, you will need to make sure to use the sudo command or login as root or a sufficiently privileged account.

Enable the RSM service

Type in the command prompt:


You should see a lot of text go by in the console and no error messages.

For Linux you should be able to replace the enclosing % with a leading $ and the .exe with a .sh

Add ARC tools to the path

ARC is mostly setup via the command line. There are a number of command line utilities that we want to add to the `PATH` so that we don’t have to prefix the entire directory each time:

set PATH=%PATH%;"%Ansys180_DIR\RSM\ARC\tools\%Ansys_SYSDIR%\"

If you did this incorrectly, you’ll get a “___ is not recognized as an internal or external command” message in the subsequent steps.

For Linux, used export and switch out the % variable substitutions as above.

Switch ARC to advanced mode and install the master & node services

In order to do anything with ARC beyond what the Ansys install process does for you automatically, you need to switch it to advanced mode:

arcswitchmode -advanced

This computer will both receive and run jobs so the master and node services need to be enabled:

installservice -arcmaster
installservice -arcnode

If you are so inclined, you can set limits on the number of cores and disk space. Run the following command to see the help for the command on how to do so:

arcconfig node modify

Add ALL THE THINGS to the firewall

You’ll need to use the Advanced Windows Firewall and set filtering rules with port numbers, which is a bit oldschool. To get to the advanced firewall program, I usually press the Start Menu button, type in firewall and select Windows Firewall With Advanced Security.

Once you have it open:

  1. Click Inbound Rules on the left pane
  2. Click New Rule on the right pane
  3. Select Port and click Next
  4. Keep TCP selected and for the port numbers enter `11180,12180,13180,40000-59999`
  5. Select Next three times
  6. Enter a name for the rule (I like to use `RSM/ARC Ports`)
  7. Select Finish

For Linux users, I would recommend to try to use Uncomplicated Firewall (ufw) or get some help from IT here.

Cache the credentials:

You may also cache your password, just to be safe.

And enter your password at the command prompt.

Create a staging folder that is shared

The last thing that you need to do is create a Staging folder somewhere for remote computers to upload analysis files to:

  1. Create a folder named `Staging` (or whatever you would like)
  2. Right click on it and select Share With -> Specific People
  3. In the window that pops up, you can just specify the current user

You should have an address for the folder that looks something like \\computer\Staging

Save this for later.

For Linux, you should look into NFS or SMB.

Local Machine Setup

Compared to the remote machine setup, the local machine is a breeze. Everything is done through the GUI of the new RSM Configuration Utility
There is a new program that you use to add things you can submit to. In the Start Menu, go to `Ansys 18.0 -> Remote Solve Manager -> RSM Configuration`

Once here, follow these steps:

  1. Press the Add Cluster button or right click and select Add Cluster in the tree
  2. Name the cluster (this is what will show up in Workbench/Mechanical)
  3. Enter the hostname on the network in Submit Host and select the operating system
  4. Leave the Cluster type as ARC
  5. Select Apply and then select the File Management tab
  6. Select RSM internal file transfer mechanism (ideally you are on a fast local network)
  7. Enter the staging folder path that you setup a few steps ago
  8. Select Apply and then select the Queues tab
  9. Click the Import/Refresh Cluster Queues button
  10. Enter the credentials (machine\username :: password) like you are logging onto the remote computer and select Ok
  11. If successful the RSM queues will be populated with queues from the cluster. Make sure that the default queue is enabled
  12. Select Apply
  13. Test the queue by pressing the Test button

Your test should be successful after a few moments. Congrats, your new RSM queue is ready to be used!

Keep up to date on hardware and Ansys simulation news and tips by subscribing to our newsletter:


Subscribe to Newsletter

  • This field is for validation purposes and should be left unchanged.

Register to Attend the ANSYS R18 Webinar on 1/31


Taming Product Complexity with Pervasive Engineering Simulation

Manufacturing is undergoing the most fundamental transformation since the introduction of the assembly line. Trends like the Internet of Things, additive manufacturing and machine learning are merging the physical and digital worlds, resulting in products that defy imagination. But this new opportunity brings considerable complexity — complexity that can be tamed with pervasive engineering simulation. Pervasive simulation expands simulation’s traditional boundaries, broadening the use of these tools upstream to product design and downstream to operations through the use of digital twins.

Join the new CEO of ANSYS, Ajei Gopal, and visionary customers Cummins, Nebia, Oticon, Metso, GE Digital as they demonstrate the power of pervasive simulation. You’ll also hear directly from the ANSYS development teams that have worked tirelessly to produce the latest version of our industry-leading solutions. They’ll discuss how ANSYS 18 deepens and strengthens the ANSYS engineering simulation platform — and how it supports new applications.

Attend this webinar to learn:

  • How you can use digital exploration to quickly evaluate changes in design, reducing development costs and preventing late-stage design changes
  • How digital prototyping enables you to provide insights into real-world product performance, test “what-if” scenarios and ensure optimal designs
  • How simulation is moving downstream of the product lifecycle through the use of digital twins to increase efficiency and to decrease unplanned downtime
Register to attend this interactive webinar on the future of pervasive engineering simulation

January 31, 2017
8:00AM – 10:00AM PST


First Name:

Last Name:

Email Address:


Meet our ANSYS Speakers:
Ajei Gopal Andre Bakker Dale Ostergaard Larry Williams Sergey Polstyanko Eric Bantegnie
Ajei Gopal

President and CEO

Andre Bakker

Senior Director Fluids Development

Dale Ostergaard

Senior Director Software Development

Larry Williams

Senior Director Electronics Products

Sergey Polstyanko

Senior Director, Research and Development

Eric Bantegnie

Vice President and GM, Systems Business Unit

Tech Tip – R17.2 HFSS Update: Automatic Touchstone File Export



ANSYS provides some new features in HFSS R17.2. Automatic Touchstone File Export is a new feature in HFSS that makes your engineering simulation life much easier and happier :-).

Dynamic Link workflow links the S-parameter solutions from EM simulators like HFSS designs to circuit simulator for linear circuit analysis. For example, in Antenna design, you can export S-parameter from HFSS design into a circuit simulation to match the antenna.

The new feature automatically exports the touchstone files to a user selected directory. You just need to set it in HFSS Design Setting:
  • Launching ANSYS Electronics Desktop 2016.2 HFSS
  • HFSS – Design Setting
    • Export S Parameters tab

Mehrnoosh Image 1 -September 2016 Newsletter

The default directory for saving the touchstone files is in same location as results directory.

  • <projectname>. Aedtexport
    • <Designname > folder
      • <solutionname > + time stamp + date stamp folder >
    • Touchstone file name = _< sweepname > + solution data base stamp
    • Also included in same directory is index.csv file.
      • Maps values of parameters to touchstone file names in directory.

Mehrnoosh Image 2 - September Newsletter

By Mehrnoosh Khabiri
Tips & Tricks - CFD-Post

Tech Tip – Transient Animation Improvements in CFD-Post

ANSYS CFD-Post is a state-of-the-art postprocessing tool used to visualize and quantify results from CFD simulations. At R17, transient flow variations are easier to animate using the new “Timestep Animation” option. This new capability uses ‘music-player’ style controls to play back transient results.

CFD-Post Animation graphical user interface

CFD-Post Animation graphical user interface

Some new user-interface options for Timestep Animation:

  • ‘Specify Range For Animation’ allows to trim the start/stop at specific timesteps instead of playing the entire animation.
  • ‘Advanced Frame Selection Controls’ allows to skip timesteps during the animation. This option is useful for speeding-up creation of animations from large results files.








Subscribe to Newsletter

  • This field is for validation purposes and should be left unchanged.

Tech Tip – Reverse Engineering Your Deformed Results in ANSYS

kaan-80x80The deformed geometry capability in ANSYS R17 is one of the most powerful and easy to use new features in the latest release of ANSYS. In addition to the new workflows that it enables, you can also easily reverse engineer your deformed results using ANSYS SpaceClaim. In this post I’ll show how to take your deformed geometry to another ANSYS analysis. Then I’ll show how you can use the powerful reverse engineering features in SpaceClaim to make your deformed results into a geometry again.

Deformed Geometry – Analysis to Analysis

Where previously you needed to create named selections and use scripts with intermediate MAPDL and FEModeler systems, now you can just drag and drop connections on the Workbench schematic:


A couple of notes:

  • For dynamic analysis that use the Linear Perturbation method, this happens behind the scenes on the mesh already. No need to apply this for the standard harmonic analysis.
  • If you want to use this parametrically, you will need to apply loads on the downstream analysis with APDL or loads that are compatible with nodal named selections. All other named selections and loads will be lost/unassigned when the deformed geometry is updated.
  • The shape but not any stress states are transferred. If stress states are desired, the INISTATE APDL command will be necessary.

Deformed Geometry – Analysis to Geometry

You are not limited to just sending deformed geometry to another analysis, you can also send it back to a geometry using tools that you probably already have. Here we will work with a metal forming test case, done with ANSYS Autodyn. See this workflow in the video below.


The first step is to right click on the desired geometry result and select Export -> STL


The STL format is a faceted data format, which is not strictly compatible with the types of geometry that ANSYS and most CAD systems expect. You can think of it as a surface mesh of triangles around the geometry. It is not explicitly associated with a volume and if the quality of the STL file is poor, filling the mesh can be problematic. An STL surface mesh simply converted into a volume is a relatively inefficient way to represent geometry for ANSYS. Luckily we can do some reverse engineering in ANSYS SpaceClaim, a tool which you may already have.

Notice that our shell elements from ANSYS are represented as 3D in the exported deformed geometry. The STL file is brought in as a mesh body type. ANSYS SpaceClaim is used extensively in reverse engineering. We can see that we have a few options in the Insert -> Reverse Engineering section of the ribbon interface.


We will be using the Skin Surface tool. This allows us to define surface bounds and control points to create a surface corresponding to a surface mesh region. The initial attempt is fairly imprecise:


What happened here is that the surface mesh fitted to both the top AND bottom sides of the thin body. The primary way to deal with this is to sample smaller, less complex areas of the surface. The Skin surface tool lends itself naturally to this workflow of creating patches of several different surfaces.


See this video for more information on the reverse engineering features can capabilities of SpaceClaim.

Optionally we can also improve the quality of the mesh to better resolve the curvature using the Facets tab, enabled by an add-on license to SpaceClaim. It is used commonly in 3D printing applications and it has tools for working with dirtier meshes than what we will generally export from ANSYS.


Once we have all of the surfaces fitted and created, ideally it will turn into a solid automatically. There will typically be precision issues, though, that keep the surfaces from forming an airtight volume. The Repair -> Solidify section has tools to help with this. After fixing some small gaps we have a solid geometry.


Afterwards it is good practice to check the Deviation of how well the geometry matches the source mesh. We can do this in the Measure -> Deviation tool. Notice how the carefully created top surface patches have better deviation than the quick and dirty bottom surface patches.


Hopefully you’ve found that helpful!

If this was useful to you and you’d like to hear other ways to speed up your simulations contact us or subscribe to our newsletter below:


Subscribe to Newsletter

  • This field is for validation purposes and should be left unchanged.