(Click to open topic with navigation)

You are here: RPM Installation > Upgrading > Upgrading Remote Visualization (RPM)

3.31 Upgrading Remote Visualization (RPM)

If using Remote Visualization with Viewpoint Server 9.1.0, your Remote Visualization installation must use FastX 2.2.

In this topic:

3.31.1 Confirm if an Upgrade is Needed

Run the following command to determine your current version of FastX.

[root]# rpm -q StarNetFastX2

If the version reported is less than 2.2, continue with the section to Upgrade Remote Visualization later in this topic.

3.31.2 Upgrade Remote Visualization

If you determined that you need to upgrade Remote Visualization, you will need to upgrade the gateway server and all the session servers (Torque MOM Hosts).

In this section:

3.31.2.A Upgrade the Gateway Server

Do the following:

  1. Make sure that your DNS server is configured for reverse lookups. Without reverse DNS, Session Servers will fail to register with your Gateway Server. As a result, authentication requests to the Gateway Server will fail because the Gateway Server will not be able to connect to any Session Servers.
  2. On the Remote Visualization Gateway Server Host, do the following
    1. If you installed Remote Visualization Gateway Server on its own host or if Remote Visualization Gateway Server is the first component being upgraded on a host with other RPM installations, complete the steps to prepare the host. See 3.19 Preparing for RPM Upgrades for more information.

    2. Install or update FastX and all of its dependencies.

      [root]# yum install ImageMagick-perl perl-Crypt-SSLeay perl-Net-SSLeay perl-X11-Protocol StarNetFastX2

      If installing on RHEL, some packages may not be found in the standard RHEL distribution repositories. You will need to install the missing dependencies from EPEL or other reputable repositories.

      [root]# rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
[root]# yum install yum-utils
[root]# yum-config-manager --disable epel
[root]# yum install --enablerepo=epel,rhel-6-server-eus-optional-rpms ImageMagick-perl perl-Crypt-SSLeay perl-Net-SSLeay perl-X11-Protocol StarNetFastX2
    3. Confirm the config directory is owned by root; if it is, chown it to "fastx".
      [root]# ls -ld /usr/lib/fastx2/config
drwxr-xr-x 2 root root 4096 Jun  6 11:11 /usr/lib/fastx2/config

[root]# chown fastx. /usr/lib/fastx2/config/ -R
    4. Remove the existing gateway-server.json file.
      [root]# rm /usr/lib/fastx2/config/gateway-server.json
    5. Restart the FastX service. 
      [root]# service fastx restart

3.31.2.B Configure the Gateway Server

Do the following:

  1. Using a web browser, navigate to your secure Remote Visualization Gateway Server instance. (https://<gateway_host>:3443; where <gateway_host> is the IP address or name of the Gateway Server Host).

    The Log In page displays. For example:

    Click to enlarge

  2. Log in as the FastX admin user. Do one of the following:

    • If your authentication method is password-based, do the following:
      1. Enter the user name (default is "ace").
      2. Enter the password (default is "ace").
      3. Make sure the "Use Public Key Authentication" checkbox is cleared.
      4. Click Log In.
    • If your authentication method is key-based, do the following:
      1. Enter the user name (default is "ace").
      2. Select the "Use Public Key Authentication" checkbox.
      3. A prompt will display asking for you to load your private key file.
        1. Click Upload Private Key File and navigate to your stored key file.

          When your key file has uploaded it will be displayed in the prompt. For example:

          Click to enlarge

        2. Click Close. The prompt closes.
      4. Click Log In.

  3. Click the icon for Admin\System Configuration. The icon is circled in the example to assist in finding its location.

    Click to enlarge

  4. Select the Network tab. If it is not already selected, select the Configuration sub-tab to display the FastX Network Configuration page.

    Click to enlarge
  5. Do the following:
    1. In the Secret Key field, remove the auto-generated key and enter the secret key name referenced by the current (non-upgraded) Session Servers. Record this secret key (e.g. copy to your clipboard) because you will need it when configuring the Session servers later in this topic.
    2. Enable the connection to accept data from cluster member.
    3. In the box to specify the log in method, select "Sessions - log in to the system running the fewest sessions".
    4. Disable the Gateway Server from sending data to cluster members.

    The following image is an example of the completed FastX Network Configuration page for the Gateway Server.

    Click to enlarge

  6. Click Save to submit your changes.

3.31.2.C Upgrade the Session Servers

These instructions assume you installed the Remote Visualization Session Servers on the same hosts on where the Torque MOM Hosts (compute nodes) were installed and that you have prepared those hosts for RPM upgrades.

Do the following:

  1. Make sure that your DNS server is configured for reverse lookups. Without reverse DNS, Session Servers will fail to register with your Gateway Server. As a result, authentication requests to the Gateway Server will fail because the Gateway Server will not be able to connect to any Session Servers.
  2. On the each Session Server host, do the following:
    1. Install or update FastX and all of its dependencies.
      [root]# yum install ImageMagick-perl perl-Crypt-SSLeay perl-Net-SSLeay perl-X11-Protocol StarNetFastX2

      If installing on RHEL, some packages may not be found in the standard RHEL distribution repositories. You will need to install the missing dependencies from EPEL or other reputable repositories.

      [root]# rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
[root]# yum install yum-utils
[root]# yum-config-manager --disable epel
[root]# yum install --enablerepo=epel,rhel-6-server-eus-optional-rpms ImageMagick-perl perl-Crypt-SSLeay perl-Net-SSLeay perl-X11-Protocol StarNetFastX2
    2. Confirm the config directory is owned by root; if it is, chown it to "fastx".
      [root]# ls -ld /usr/lib/fastx2/config
drwxr-xr-x 2 root root 4096 Jun  6 11:11 /usr/lib/fastx2/config

[root]# chown fastx. /usr/lib/fastx2/config/ -R
    3. Remove the existing gateway-server.json file.
      [root]# rm /usr/lib/fastx2/config/gateway-server.json
    4. Restart the FastX service. 
      [root]# service fastx restart

3.31.2.D Configure a Session Server

This section provides instructions on how to configure one Session Server (referred to as the initial Session Server). The configuration will then be copied to the additional Session Servers in your environment in a later procedure.

Do the following:

  1. Using a web browser, navigate to your secure Remote Visualization Session Server instance. (https://<session-host>:3443; where <session_host> is the IP address or name of the initial Remote Visualization Session Server Host).

    The Log In page displays. For example:

    Click to enlarge

  2. Log in as the FastX admin user. Do one of the following:

    • If your authentication method is password-based, do the following:
      1. Enter the user name (default is "ace").
      2. Enter the password (default is "ace").
      3. Make sure the "Use Public Key Authentication" checkbox is cleared.
      4. Click Log In.
    • If your authentication method is key-based, do the following:
      1. Enter the user name (default is "ace").
      2. Select the "Use Public Key Authentication" checkbox. Upload the public key used when you configured the Gateway Server earlier in this topic.
      3. Click Log In.

    When you first log in, you will get a message that you have no session running. That is expected.

  3. Select the icon for Admin\System Configuration. The icon is circled in the example to assist in finding its location.

    Click to enlarge

  4. Select the Network tab. If it is not already selected, select the Configuration sub-tab to display the FastX Network Configuration page.

    Click to enlarge
  5. Do the following:
    1. In the Secret Key field, remove the auto-generated key and enter the secret key used when configuring the Remote Visualization Gateway Server earlier in this topic.

      You will not be able to login to the portal on the Gateway Server until you have completed the configuration of at least one Session server. If you did not save it earlier, the secret key can be found in the /usr/lib/fastx2/config/network.json on the Gateway Server.

    2. Disable the connection to accept data from cluster members.
    3. Enable the Gateway Server to send data to cluster members.
    4. In the box to specify whether to SSL certificates, select "I am using a self-signed certificate".
    5. In the Cluster member URLs area, do the following:
      1. Click the + icon.
      2. In the box that displays, enter the IP address or name and the port number of the Gateway Server you just upgraded (for example: "https://mgmtnode:3443").

    The following image is an example of the completed FastX Network Configuration page.

    Click to enlarge

  6. Click Save to submit your changes.

3.31.2.E Copy the Session Server Configuration to the Remaining Session Servers

After you configured the initial Session Server, the settings are saved in the network.json file.

For documentation clarity, these instructions use node00 through node09 as the names of the Session Servers; with node00 designated as the initial Session Server.

On the initial Session Server Host, copy the network.json file to the remaining Session Server Hosts in your environment, and restart the FastX service.

[root]# for i in {01..09} ; do scp /usr/lib/fastx2/config/network.json root@node$i:/usr/lib/fastx2/config/network.json ; done
[root]# for i in {01..09} ; do ssh node$i "chown fastx. /usr/lib/fastx2/config/. -R" ; done
[root]# for i in {01..09} ; do ssh node$i "service fastx restart" ; done

3.31.3 Grant Users Remote Visualization Permissions in Viewpoint

If you upgraded Viewpoint from version 9.0.2 or prior, verify that the users who work with Remote Visualization have the appropriate role in their Viewpoint user principal.

These are the Viewpoint Roles for Remote Visualization:

See Creating or Editing Principals in the Moab Viewpoint Reference Guide for instructions on setting up principals.

© 2016 Adaptive Computing