...
| No Format |
|---|
$> tsh login $> ssh user@hpc-login # or for users with no formal access to HPC service: $> ssh user@ecs-loginuser@ag-login |
You may also connect via SSH from another the ECMWF platform such as the Linux VDI without the need of Teleport.
| No Format |
|---|
$> ssh hpc-login
# or for users with no formal access to HPC service:
$> ssh ecs-login |
| Tip | ||
|---|---|---|
| ||
The first time you log in, we strongly recommend you set up your local SSH key-based authentication with the following command:
This step is required for many tools and applications to work well, such as ecinteractive, ecflow, and ecaccess jobs, as well as convenient access from our VDI service. |
ag-login |
See See AG: Persistent interactive job with ecinteractive if you wish to customise the resource limits of your interactive session.
| Info |
|---|
Upon logging in, please take a look at the message of the day displayed on the login nodes (or review /etc/motd). |
...
List of main entry points
You can use the hpc-* or hpc2020ag-* names in the table below if you just need to use the default HPCF complex, or the specific names for each of the complexes. For ECS, you may use the ecs-* names. Your usual interface to connect would be the *-login names, and for remote submission of jobs we would recommend using the *-batch names as they are dedicated login nodes for job submissions. If you need to set up a cronjob, then the *-cron names are to be used.:
| Generic names |
|---|
| AG Interactive Login |
|---|
aa-login
ab-login
ac-login
ad-login
ag-login |
hpc2020-login
| AG Remote batch job submission |
|---|
hpc-batch
hpc2020-batch
aa-batch
ab-batch
ac-batch
ad-batch
ecs-batch
hpc-cron
hpc2020-cron
ag-batch |