> For the complete documentation index, see [llms.txt](https://docs.constellationnetwork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.constellationnetwork.io/run-a-node/validator-node-guides/operational-guides/upgrade-tessellation-quick-start.md).

# Upgrade Tessellation Quick Start

## **Introduction**

This guide walks you through upgrading your Validator node to the latest version of **Tessellation** using `nodectl`, leveraging non-interactive mode with recommended defaults.  Please refer to the full upgrade guide for a more detailed walk-through.

{% content-ref url="/pages/JuRmmWP9Uf0qjo0x3B1L" %}
[Upgrade Tessellation Guide](/run-a-node/validator-node-guides/operational-guides/upgrade-tessellation-guide.md)
{% endcontent-ref %}

***

{% stepper %}
{% step %}

## SSH Into Your VPS

### [<kbd>How to SSH into a VPS</kbd>](/run-a-node/references/ssh-remote-access/how-to-ssh-into-vps.md)&#x20;

```bash
ssh -i /path/to/ssh/private/key nodeadmin@<vps_ip_address> -p <port>
```

{% endstep %}

{% step %}

### Begin the Upgrade

Execute the following command to begin a **non-interactive** upgrade. This will automatically pull and install the latest Tessellation release using default settings.

```bash
sudo nodectl upgrade --ni
```

{% endstep %}

{% step %}

### Single Layer Nodes

If you're running a [**single-layer**](/run-a-node/validator-node-guides/build-your-node/node-specifications.md#dor-data-layer-1-node) Validator (Layer0 or Layer1 only), you can skip directly to the **Confirm Status** step below.
{% endstep %}

{% step %}

### Hybrid Node Considerations

If your node operates in [**hybrid mode**](/run-a-node/validator-node-guides/build-your-node/node-specifications.md#constellation-network-hybrid-node) (participating in both Layer0 and Layer1):

* You **must wait** for the **Layer0 profile to reach the `Ready` state** before attempting to connect Layer1.
* Layer1 cannot join the cluster until the full Layer0 chain is downloaded and synchronized.
  {% endstep %}

{% step %}

### Auto Restart (If Enabled)

If you have the [`auto_restart`](/run-a-node/validator-node-guides/enable-auto-restart.md) feature enabled:

* Your node will detect when Layer0 reaches `Ready` state.
* It will automatically initiate the Layer1 connection.
  {% endstep %}

{% step %}

### Watch for Layer0 to Reach `Ready`

Use the command below to monitor the Layer0 profile. Adjust the `-p` flag to match your profile name.

```bash
sudo nodectl status -p dag-l0 -w 120
```

{% endstep %}

{% step %}

### Manually join Layer1

Once Layer0 is in the Ready state, attempt to join Layer1:

```bash
sudo nodectl join -p dag-l0
```

{% endstep %}

{% step %}

### Confirm Status

Check the final status of all profiles:

```bash
sudo nodectl status
```

Expected output

```
JOIN STATE     Ready
IN CONSENSUS   True
```

{% endstep %}
{% endstepper %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.constellationnetwork.io/run-a-node/validator-node-guides/operational-guides/upgrade-tessellation-quick-start.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.