> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/knowledge-base/system-administration/proper-power-sequence-for-vergeos.md).

# Proper Power Sequence

### Proper Shutdown Sequence for a VergeOS Environment

To power off a cluster (a collection of two or more nodes), follow these steps:

1. Check any running workloads on each node of the cluster. Navigate to the node dashboard for each node and review the **Running Machines** section.
2. If there are tenants running on any of the nodes, log into those tenant environments and gracefully shut down all running workloads.
3. Power off all running workloads on each node, including VMs, tenant nodes, VMware backup services, and NAS services (if applicable).

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>vNet Containers</strong></p><p>There is no need to manually stop any running vNet containers; they will be gracefully stopped automatically in the subsequent steps.</p></div>
4. After stopping all running workloads, navigate to the **Cluster dashboard** for the cluster you wish to power off.
5. Select **Power Off** from the left-hand menu to begin shutting down each node in the cluster.
6. Finally, navigate to **System → Clusters** and select **Power Off** in the left menu to power off the entire cluster.

{% hint style="warning" %}
**IMPORTANT**

If an environment contains multiple clusters, ***ALWAYS*** shut down the cluster containing the controller nodes (Node1 & Node2) **LAST**.
{% endhint %}

***

### Proper Power-On Sequence for a VergeOS Environment

To properly power on a VergeOS environment, perform the following steps:

1. Power on **Node1**.
2. **Wait 30 seconds to a minute.**
   * This brief pause lets Node1 begin initializing before the rest of the cluster arrives.
3. **Power on all other nodes within the cluster.** All other cluster nodes can be powered on immediately -- there is no need to delay between nodes.
4. **Multi-cluster environments:** bring the controller cluster fully online before powering on additional clusters.
5. The system will automatically perform integrity checks of each storage tier.

   <div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p><strong>Storage Tier Integrity Checks</strong></p><p>See <a href="/pages/9YjLJkdeYg5ouCl5hG12">vSAN Tier Status (Journal Walks)</a> for information related to these automatic integrity checks (journal walks).</p></div>
6. **Verify system health.**
   * On the Main Dashboard, verify all nodes and vSAN tiers appear with a green status.
   * Check for any new alarms.

{% hint style="warning" %}
**Power-On After an Uncontrolled Shutdown**

Extra care should be taken when powering on a cluster after an uncontrolled shutdown (e.g. an abrupt power loss, UPS exhaustion, or facility failure). See [Cluster Recovery After Full Power Outage](/knowledge-base/system-administration/cluster-recovery-after-power-outage.md) for the full recovery procedure, including pre-power-on checks, vSAN integrity verification, and prevention guidance.
{% endhint %}

***

{% hint style="info" %}
**Document Information**

* Last Updated: 2024-08-29
* vergeOS Version: 4.12.6
  {% endhint %}


---

# 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.verge.io/knowledge-base/system-administration/proper-power-sequence-for-vergeos.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.