1. Home
  2. Docs
  3. General Computing Environment
  4. Login, Compute, and Home nodes

Login, Compute, and Home nodes

Home nodes:

Home nodes can be used for light shell access (e.g. things that were traditionally done on the legacy MCS login nodes), such as interactive sessions and no CPU-heavy jobs. You can directly SSH to these from any internal trusted network (desktops, Argonne-Auth wifi).

  • homes.cels.anl.gov (round robin DNS entry for the hosts listed below)
    • homes-01.cels.anl.gov
    • homes-02.cels.anl.gov

Compute nodes:

These are for more CPU-heavy compute jobs. You can directly SSH to these from any internal trusted network (desktops, Argonne-Auth wifi). This list will grow as legacy compute nodes are rebuilt as GCE compute nodes.

  • compute-01.cels.anl.gov (nomachine, see below)
  • compute-02.cels.anl.gov
  • compute-03.cels.anl.gov
  • compute-04.cels.anl.gov
  • compute-05.cels.anl.gov
  • compute-06.cels.anl.gov

Login nodes:

GCE login nodes function differently than the legacy MCS login nodes. While the login nodes are still your way in to the GCE environment while offsite, shell access on the login nodes is now prohibited. Instead, the login nodes will be used as an SSH proxy tunnel to your preferred GCE endpoint.

  • logins.cels.anl.gov (round robin DNS entry for the login nodes listed below)
    • login-01.cels.anl.gov
    • login-02.cels.anl.gov

GUI nodes:

GCE also has a compute node available for interactive GUI logins via NoMachine.  Download the client at nomachine.com and configure it to connect via SSH.  If you are connecting from onsite or a trusted network, you can connect directly to nomachine.cels.anl.gov in the configuration.

Please note: By default, nomachine uses its own SSH instead of the system version, which ignores your .ssh/config.  To fix this, you must edit your .nx/config/player.cfg file and change “SSH client mode” from library to native.  See this for more information.

From offsite, you must either use the VPN or this SSH connection will have to be proxied through the logins.  See SSH documentation.

  • Quick cheat sheet:
    • Mac/Linux users
      • If you used the two line basic configuration from above, use the hostname “nomachine.cels.anl.gov” for the Host in the NoMachine setup.
      • If you used the Advanced SSH config from above, add the following lines to your ~/.ssh/config immediately after the “homes-gce” section in the docs linked above.
        Host nomachine nomachine.cels.anl.gov
        User <anlusername>
        Hostname nomachine.cels.anl.gov
        ProxyJump login-gce
        ForwardX11Trusted yes

        Then, in nomachine, configure a connection via SSH to the host “nomachine” (presuming you used the example above).

      • Important: Make sure in your connection, you go into the Configuration tab and specify Use key-based authentication with a SSH agent, then choose Modify and check Forward Authentication.  If you do not do this, you may not be able to connect from outside Argonne networks.
    • Windows users
      • The Windows nxclient will not obey your .ssh config, so you must set up a separate SSH tunnel.  To do this, put the following entries in your .ssh\config file:
        Host nomachine nomachine.cels.anl.gov
        User <anlusername>
        Hostname nomachine.cels.anl.gov
        ProxyJump login-gce
        ForwardX11Trusted yes
        LocalForward 4100 localhost:4000
      • Next, configure your connection to nomachine with the following settings:
        • Name: CELS Nomachine
        • Host: localhost
        • Port: 4100
        • Protocol: NX
        • In the configuration tab for Authentication, Use password authentication.
      • From a commandline, “ssh nomachine” and wait for a successful connection.  After you see the shell prompt, then you can connect your nomachine client.

 

Was this article helpful to you? Yes 2 No

How can we help?