HPCE/gitea-pages
HPCE/gitea-pages
0
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Activity

Update NX

Browse Source
This commit is contained in:
caubet_m 2024-08-02 17:50:50 +02:00
parent 5eb5bad57e
commit 1d4cde414c
1 changed files with 20 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
pages/merlin7/02-How-To-Use-Merlin/nomachine.md
View File

@ -1,7 +1,7 @@
--- ---
title: Remote Desktop Access title: Remote Desktop Access
#tags: #tags:
keywords: NX, nomachine, remote desktop access, login node, login001, login002, merlin-nx-01, merlin-nx-02, merlin-nx, rem-acc, vpn keywords: NX, nomachine, remote desktop access, login node, login001, login002, merlin7-nx-01, merlin7-nx-02, merlin7-nx, rem-acc, vpn
last_updated: 07 September 2022 last_updated: 07 September 2022
#summary: "" #summary: ""
sidebar: merlin7_sidebar sidebar: merlin7_sidebar
@ -15,14 +15,14 @@ It uses the NX protocol to enable a graphical login to remote servers.
## Installation ## Installation
NoMachine is available for PSI Windows computers in the Software Kiosk under the NoMachine is available for PSI Windows computers in the Software Kiosk under the
name **NX Client**. Please use the latest version (at least 6.0). For MacOS and name **NX Client**. Please use the latest version (at least 8.1.3). For MacOS and
Linux, the NoMachine client can be downloaded from https://www.nomachine.com/. Linux, the NoMachine client can be downloaded from https://www.nomachine.com/.
## Accessing Merlin7 NoMachine from PSI ## Accessing Merlin7 NoMachine from PSI
The Merlin7 NoMachine service is hosted in the following machine: The Merlin7 NoMachine service is hosted in the following machine:
* **`merlin-nx.psi.ch`** * **`merlin7-nx.psi.ch`**
This is the **front-end** (hence, *the door*) to the NoMachine **back-end nodes**, This is the **front-end** (hence, *the door*) to the NoMachine **back-end nodes**,
which contain the NoMachine desktop service. The **back-end nodes** are the following: which contain the NoMachine desktop service. The **back-end nodes** are the following:
@ -30,10 +30,13 @@ which contain the NoMachine desktop service. The **back-end nodes** are the foll
* `login001.merlin7.psi.ch` * `login001.merlin7.psi.ch`
* `login002.merlin7.psi.ch` * `login002.merlin7.psi.ch`
Any access to the login node desktops must be done through **`merlin-nx.psi.ch`** Any access to the login node desktops must be done through **`merlin7-nx.psi.ch`** .
(or from **`rem-acc.psi.ch -> merlin-nx.psi.ch`** when connecting from outside PSI).
The **front-end** service running on **`merlin-nx.psi.ch`** will load balance the sessions {% comment %}
(or from **`rem-acc.psi.ch -> merlin7-nx.psi.ch`** when connecting from outside PSI).
{% endcomment %}
The **front-end** service running on **`merlin7-nx.psi.ch`** will load balance the sessions
and login to any of the available nodes in the **back-end**. and login to any of the available nodes in the **back-end**.
**Only 1 session per back-end** is possible. **Only 1 session per back-end** is possible.
@ -45,10 +48,10 @@ NoMachine service running on a login node.
#### Adding a new connection to the front-end #### Adding a new connection to the front-end
Click the **Add** button to create a new connection to the **`merlin-nx.psi.ch` front-end**, and fill up Click the **Add** button to create a new connection to the **`merlin7-nx.psi.ch` front-end**, and fill up
the following fields: the following fields:
* **Name**: Specify a custom name for the connection. Examples: `merlin-nx`, `merlin-nx.psi.ch`, `Merlin Desktop` * **Name**: Specify a custom name for the connection. Examples: `merlin7-nx`, `merlin7-nx.psi.ch`, `Merlin Desktop`
* **Host**: Specify the hostname of the **front-end** service: **`merlin-nx.psi.ch`** * **Host**: Specify the hostname of the **front-end** service: **`merlin7-nx.psi.ch`**
* **Protocol**: specify the protocol that will be used for the connection. *Recommended* protocol: **`NX`** * **Protocol**: specify the protocol that will be used for the connection. *Recommended* protocol: **`NX`**
* **Port**: Specify the listening port of the **front-end**. It must be **`4000`**. * **Port**: Specify the listening port of the **front-end**. It must be **`4000`**.
@ -63,7 +66,7 @@ You will be requested for the crendentials (username / password). **Do not add `
### Opening NoMachine desktop sessions ### Opening NoMachine desktop sessions
By default, when connecting to the **`merlin-nx.psi.ch` front-end** it will automatically open a new By default, when connecting to the **`merlin7-nx.psi.ch` front-end** it will automatically open a new
session if none exists. session if none exists.
If there are existing sessions, instead of opening a new desktop session, users can reconnect to an If there are existing sessions, instead of opening a new desktop session, users can reconnect to an
@ -87,15 +90,20 @@ X Windows:
### No VPN access ### No VPN access
No VPN access from outside is not possible for the pre-production phase, since it requires advanced network knowledge to do so, and the external **rem-acc.psi.ch**
service does not allow access to the new cluster yet.
{% comment %}
Access to the Merlin7 NoMachine service is possible without VPN through **'rem-acc.psi.ch'**. Access to the Merlin7 NoMachine service is possible without VPN through **'rem-acc.psi.ch'**.
Please follow the steps described in [PSI Remote Interactive Access](https://www.psi.ch/en/photon-science-data-services/remote-interactive-access) for Please follow the steps described in [PSI Remote Interactive Access](https://www.psi.ch/en/photon-science-data-services/remote-interactive-access) for
remote access to the Merlin7 NoMachine services. Once logged in **'rem-acc.psi.ch'**, you must then login to the **`merlin-nx.psi.ch` front-end** . remote access to the Merlin7 NoMachine services. Once logged in **'rem-acc.psi.ch'**, you must then login to the **`merlin7-nx.psi.ch` front-end** .
services. services.
{% endcomment %}
### VPN access ### VPN access
Remote access is also possible through VPN, however, you **must not use 'rem-acc.psi.ch'**, and you have to connect directly Remote access is also possible through VPN, however, you **must not use 'rem-acc.psi.ch'**, and you have to connect directly
to the Merlin7 NoMachine **`merlin-nx.psi.ch` front-end** as if you were inside PSI. For VPN access, you should request to the Merlin7 NoMachine **`merlin7-nx.psi.ch` front-end** as if you were inside PSI. For VPN access, you should request
it to the IT department by opening a PSI Service Now ticket: it to the IT department by opening a PSI Service Now ticket:
[VPN Access (PSI employees)](https://psi.service-now.com/psisp?id=psi_new_sc_cat_item&sys_id=beccc01b6f44a200d02a82eeae3ee440). [VPN Access (PSI employees)](https://psi.service-now.com/psisp?id=psi_new_sc_cat_item&sys_id=beccc01b6f44a200d02a82eeae3ee440).