(Click to open topic with navigation)

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

3.25 Upgrading Remote Visualization (RPM)

Remote Visualization needs to be upgraded on the gateway server and on all the session servers (Torque MOM Hosts).

Remote Visualization Server 9.0.2 is required for Viewpoint 9.0.2.

In this topic:

3.25.1 Upgrade the Gateway Server

Do the following:

  1. 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.2 Preparing the Host – Typical Method or 3.4 Preparing the Host – Offline Method.

    2. Install the new Remote Visualization RPM.

      [root]# yum update 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.25.2 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).

  2. Log in as the FastX admin user.

    Click to enlarge

  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, 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.25.3 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. On the each Session Server host, do the following:
    1. Upgrade FastX.
      [root]# yum update StarNetFastX2
[root]# chown fastx. /usr/lib/fastx2/config -R
[root]# rm -f /usr/lib/fastx2/config/session-server.json
    2. Restart the FastX service. 
      [root]# service fastx restart

3.25.4 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).

  2. Log in as the FastX admin user.

    Click to enlarge

  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, enter the name of the secret key used when configuring the 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.25.5 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

© 2016 Adaptive Computing