Академический Документы
Профессиональный Документы
Культура Документы
ANSYS, ANSYS Workbench, AUTODYN, CFX, FLUENT and any and all ANSYS, Inc. brand, product, service and feature
names, logos and slogans are registered trademarks or trademarks of ANSYS, Inc. or its subsidiaries located in the
United States or other countries. ICEM CFD is a trademark used 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. FLEXlm and FLEXnet are trademarks of Flexera Software LLC.
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 products
and documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license agreement
that contains provisions concerning non-disclosure, copying, length and nature of use, compliance with exporting
laws, warranties, disclaimers, limitations of liability, and remedies, and other provisions. The software products
and documentation may be used, disclosed, transferred, or copied only in accordance with the terms and conditions
of that software license agreement.
ANSYS, Inc. and ANSYS Europe, Ltd. are UL registered ISO 9001: 2015 companies.
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 software
and third-party software. If you are unable to access the Legal Notice, contact ANSYS, Inc.
Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. iii
Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
iv of ANSYS, Inc. and its subsidiaries and affiliates.
Using Remote Display Technology with ANSYS® Workbench™
Products
This document explains how to use Remote Display technology with ANSYS Workbench products.
Document Contents:
1. General Information
2. Vendor-Specific Information
1. General Information
Section Contents:
1.1. Server-Side Rendering
1.2. Graphics Card Hardware and Drivers
A remote display device is a software product that allows a user to run an application such as ANSYS
on a remote machine (the server), while displaying the graphical interface on their local machine (the
client). The following Remote Display products have been tested and are certified for use with ANSYS
products:
• NICE Desktop Cloud Visualization (DCV) 2017.4 (Remote Server: Windows® or Linux®)
• Citrix® XenDesktop™ 7 1909 for Citrix Windows®Virtual Machine (via Citrix Workspace™ 1909)
• Citrix® Hypervisor® 8.0 for Citrix Linux® Virtual Machines (using NICE DCV connection)
• VMWare vSphere ESXi™ 6.5 U2 Linux® Virtual Machines (using NICE DCV connection)
• VMWare® Horizon View™ 7.9 for VMWare vSphere ESXi™ 6.5 U2 Windows® Virtual Machine
Remote Display technologies can be a useful tool for accessing desktop applications on remote or
centralized computing resources, where low-latency network connections exist. However, users of Remote
Display technologies can expect to encounter some performance degradation and minor display issues
compared to direct desktop display.
Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 1
Using Remote Display Technology with ANSYS® Workbench™ Products
The use of server-side rendering generally requires additional configuration and command-line exe-
cution arguments (such as ssrrun on EOD, ETX and vglrun on VNC Connect). Follow vendor in-
structions for the configuration of server-side rendering and ensure that standard 3D test applications
(such as glxgears or SPECviewperf®) execute with acceptable performance before running ANSYS
applications.
The stability of Remote Display systems depends strongly on the graphics card driver being used.
Before installing any Remote Display software, you should install the latest graphics card drivers
available directly from the vendor. Note that Automatic Updates for many operating systems do not
provide the latest drivers, so direct contact with your graphics card vendor is recommended. The
latest graphics cards Nvidia Quadro, K, P, M, Grid Tesla P40, P4, M60, V100 and AMD WX series have
been tested successfully with ANSYS products.
Contact Technical Support for the most recently-tested Cards and Driver versions or refer to ANSYS
Platform-Support.
2. Vendor-Specific Information
Section Contents:
2.1. NICE Desktop Cloud Visualization 2017.4
2.2. Citrix XenDesktop 7 1909 for Citrix Virtual Machines (via Citrix Workspace 1909)
2.3. Citrix Hypervisor 8.0 for Citrix Virtual Machines (via NICE DCV 2017.4)
2.4. VMware vSphere ESXi Virtual Machines (via NICE DCV 2017.4)
2.5. VMware Horizon View 7.9 for VMware vSphere ESXi Virtual Machines
2.6. OpenText Exceed onDemand 8 SP11
2.7. VNC Connect 6.5 with VirtualGL 2.6
2.8. Microsoft Windows Remote Desktop
2.9. OpenText Exceed TurboX 12.0
Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
2 of ANSYS, Inc. and its subsidiaries and affiliates.
Vendor-Specific Information
For more information and assistance with the installation of DCV, contact NICE Support at support@nice-
software.com.
– If WorkBench has not yet launched, define the following environment (assuming csh):
– If WorkBench is launched, but Fluent has not yet launched, define the following in the Fluent launcher
window:
– If both WorkBench and Fluent have been launched, use the Fluent command window to change display
settings (you will need to close the existing graphics sub-window in Fluent and open a new one to
make it effective):
/display/set/rendering-options/driver opengl
– In all of the above cases, you can verify display info by selecting Display>Options>Info in the menu,
or by issuing following command in Fluent text window:
/display/set/rendering-options/device-info
• If there are configuration issues, an OpenGL® application on Linux may not start and you may see the
following error:
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
DCV RVN: error, cannot init local display.
DCV uses a 3D hardware accelerated X11 display, the "3D rendering display", to render OpenGL
accelerated graphics. Usually the 3D rendering display is the first display, : 0, but it may change
for different reasons. An example is a case in which multiple 3D video cards are installed.
1. The OpenGL application must know the 3D rendering display to connect to. By default, DCV
will use the first :0.0 display as 3D rendering display. In case the 3D rendering display is dif-
ferent it is possible to explicitly specify the display to use. To specify the 3D rendering display
to use:
Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 3
Using Remote Display Technology with ANSYS® Workbench™ Products
– You can permanently configure the display in the dcv.conf file (see Appendix A, dcv.conf ).
– Alternatively, if you want to change the display just for the execution of an application, you
can use the RVN_LOCAL_DISPLAY environment variable. For example, to make the DCV
Test application use the second screen on the first display, use the following line:
RVN_LOCAL_DISPLAY=:0.1 dcvtest
2. The 3D rendering display must grant X connections from the local machine to any user; you
must grant local connections to the 3D rendering display. To let the 3D rendering display accept
X connections on a production system, we suggest that you start the system at runlevel 5
(graphics mode with GDM or other Display Manager for login).
In the GDM startup script, add the following command at the beginning:
/usr/bin/xhost +local: # Enable local Unix Domain Sockets connections
# (Check xhost path on your distribution)
The appropriate script location may change depending on the Linux distribution or the installed
Display Manager.
For additional detail on this error and its resolution, refer to the "Cannot Init Local Display" section
of the NICE DCV Installation and User Guide.
2.2. Citrix XenDesktop 7 1909 for Citrix Virtual Machines (via Citrix Workspace
1909)
2.3. Citrix Hypervisor 8.0 for Citrix Virtual Machines (via NICE DCV 2017.4)
2.4. VMware vSphere ESXi Virtual Machines (via NICE DCV 2017.4)
For information on vSphere ESXi 6.5 U2, refer to the vSphere Hypervisor ESXi Support Center at https://
www.vmware.com/support/vsphere-hypervisor.html.
Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
4 of ANSYS, Inc. and its subsidiaries and affiliates.
Vendor-Specific Information
2.5. VMware Horizon View 7.9 for VMware vSphere ESXi Virtual Machines
For information on vSphere ESXi 6.5 U2, refer to the vSphere Hypervisor ESXi Support Center at https://
www.vmware.com/support/vsphere-hypervisor.html.
Installation videos and discussion of server-side rendering with Exceed onDemand are also available
through the OpenText YouTube channel at http://www.youtube.com/user/opentextcorp?feature=watch.
To achieve server-side rendering for accelerated graphics performance, ANSYS applications must be
executed using the EOD ssrrun command, or by selecting "Use Direct Server-Side Rendering" in
the OpenGL Server Host Application settings in the Xstart configuration.
– If WorkBench has not yet been launched, define the following environment (assuming bash, tcsh):
– If WorkBench has been launched but Fluent has not yet been launched, define the following in the
Fluent launcher window:
Note that VirtualGL is required to support server-side rendering with VNC Connect, and must be in-
stalled prior to installing VNC Connect. VirtualGL is available from http://www.virtualgl.org/.
Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 5
Using Remote Display Technology with ANSYS® Workbench™ Products
The On Red hat7+ and CentOS 7 servers, users may encounter a hang or grey screen. In such cases,
refer to the link below vnc documentation to modify xstartup file; https://support.realvnc.com/
knowledgebase/article/View/345/5/vnc-server-in-virtual-mode-appears-to-hang-or-you-see-a-grey-
screen-because-a-desktop-environment-cannot-be-loaded
To achieve server-side rendering for accelerated graphics performance, ANSYS applications must be
executed using the VirtualGL vglrun command.
• Launching polydata, polymat, polystat, or polyman via (vglrun) Virtual GL and VNC Connect on some remote
Linux platforms may throw a [VGL] error message. Since these products do not actually benefit from Vir-
tualGL, the workaround is simply to avoid using VirtualGL and to launch the executable normally (BUG
84767).
• To achieve server-side rendering when using Fluent from Workbench, the additional configuration steps
below will be necessary in addition to the above described command or GUI based methods:
– If WorkBench has not yet been launched, define the following environment (assuming bash, tcsh):
– If WorkBench has been launched but Fluent has not yet been launched, define the following in the
Fluent launcher window:
• For RH 7.x and CentOS 7, Xstartup file must be updated with correct kde session.
To achieve server-side rendering for accelerated graphics performance, the hardware acceleration in
Xterm should be configured as ON.
Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
6 of ANSYS, Inc. and its subsidiaries and affiliates.
Vendor-Specific Information
To achieve server-side rendering for accelerated graphics performance, ANSYS applications must be
executed using the ETX ssrrun command.
• To achieve server-side rendering when using Fluent from Workbench, the following additional configuration
steps are necessary in addition to the above described command or GUI based methods:
– If WorkBench has not yet been launched, define the following environment (assuming bash, tcsh):
– If WorkBench has been launched but Fluent has not yet been launched, define the following in the
Fluent launcher window:
Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 7
Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
8 of ANSYS, Inc. and its subsidiaries and affiliates.