> For the complete documentation index, see [llms.txt](https://docs.tensorwave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tensorwave.com/slurm/access.md).

# Access

### SSH Access

The login URL for your cluster is available in the TensorWave dashboard or in the handoff documentation provided at cluster delivery.

Depending on how your cluster is exposed, the SSH service listens on either **port 22** or **port 32222**. Check your handoff documentation if you are unsure which applies.

```bash
ssh <your-username>@<cluster-ssh-host>
# or, if using the node port:
ssh -p 32222 <your-username>@<cluster-ssh-host>
```

Authentication is by SSH key. Password authentication is disabled. Your public key must be present in your LDAP user record before first login; contact your cluster administrator if you cannot connect.

Successful login lands you on a **login pod** for your user. This is where you submit jobs, inspect the queue, and manage your files. Login pods are not intended for compute-intensive work.

***

### Slurm Accounting and User Setup

The cluster enforces **Slurm accounting**: every user must have a Slurm account and association before they can submit jobs. This is required by the QOS and limits configuration.

#### Initial setup (cluster administrator)

A cluster administrator performs the following steps once per user using `sacctmgr` from a login pod or the Slurm controller.

**1. Create an account** (if one does not already exist for the team or project):

```bash
sacctmgr add account <account-name> Description="<description>"
```

**2. Add the user and associate them with the account:**

```bash
sacctmgr add user <username> Account=<account-name> DefaultAccount=<account-name>
```

**3. Verify the association is in place:**

```bash
sacctmgr show assoc where user=<username>
```

The user can now submit jobs. Without a valid association, job submissions will be rejected.

#### Checking your own account

Users can verify their associations at any time:

```bash
sacctmgr show assoc where user=$USER
```

For full `sacctmgr` reference, see the [Slurm accounting documentation](https://slurm.schedmd.com/accounting.html).

***

### Accessing Worker Pods

Worker pods are accessible by SSH from within a login pod. Access is restricted to users who have a job currently running or a resource allocation active on the target node.

#### Connecting to a worker pod

If you already have a job running, find its allocated nodes:

```bash
squeue -u $USER
```

Then SSH to the worker pod by its Slurm node name directly from the login pod:

```bash
ssh <node-name>
# example:
ssh tus1-p14-g36
```

> **Note:** SSH to a worker pod will be refused if you do not have an active allocation on that node. This is by design.

Worker pods use port 2222 internally. This is configured automatically on login pods; no additional flags are required.

***

### IDP Configuration (Optional)

The cluster supports identity provider (IDP) integration, which allows users to authenticate using your organization's existing SSO, such as Okta, Azure AD, or Google Workspace.

IDP setup requires coordination during or after initial cluster deployment. To discuss options or initiate configuration, contact your TensorWave account manager.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tensorwave.com/slurm/access.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.