> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/private-cloud-director/getting-started/self-hosted/airctl/start-and-stop-management-plane.md).
# Start and Stop the Management Plane
This page describes how to start and stop the space.vars.self\_hosted\_product\_name management plane for a specific region or for all regions using the `airctl` CLI.
## Overview
The `airctl start` and `airctl stop` commands let you gracefully bring the management plane up or down without uninstalling it. Use these commands for planned maintenance windows, controlled shutdowns, or to restart the management plane after maintenance is complete.
Both commands accept an optional `--region` flag. When the flag is omitted, the command applies to all configured regions.
## Prerequisites
Before running `airctl start` or `airctl stop`:
* You must have `airctl` installed and a valid configuration file at `/opt/pf9/airctl/conf/airctl-config.yaml` (or a custom path you supply with `--config`).
* Confirm the regions managed by your deployment before targeting a specific region:
{% tabs %}
{% tab title="Bash" %}
```bash
airctl get-regions --config /opt/pf9/airctl/conf/airctl-config.yaml
```
{% endtab %}
{% endtabs %}
Example output:
{% tabs %}
{% tab title="Bash" %}
```bash
Deployed Regions:
• Infra
• LON
```
{% endtab %}
{% endtabs %}
## Stop the Management Plane
The `airctl stop` command scales down the management plane for the specified region. Running it without `--region` stops all configured regions.
### Command Syntax
```
airctl stop [flags]
Flags:
-r, --region string Stop the specified region only (omit to stop all regions)
Global Flags:
--config string Path to config file (default: $HOME/airctl-config.yaml)
--quiet Disable spinners
--verbose Print verbose logs to the console
-h, --help Show command help
```
### Stop a Specific Region
{% tabs %}
{% tab title="Bash" %}
```bash
airctl stop --config /opt/pf9/airctl/conf/airctl-config.yaml --region
```
{% endtab %}
{% endtabs %}
Example output:
{% tabs %}
{% tab title="Bash" %}
```bash
SUCCESS scaling down management plane
```
{% endtab %}
{% endtabs %}
### Stop All Regions
To stop all configured regions, omit the `--region` flag:
{% tabs %}
{% tab title="Bash" %}
```bash
airctl stop --config /opt/pf9/airctl/conf/airctl-config.yaml
```
{% endtab %}
{% endtabs %}
{% hint style="warning" %}
**Warning**
Stopping all regions brings down the entire management plane, including the UI and API endpoints. Ensure no critical workloads depend on management plane availability before proceeding.
{% endhint %}
## Start the Management Plane
The `airctl start` command scales up and auto-configures the management plane for the specified region. Running it without `--region` starts all configured regions.
### Command Syntax
```
airctl start [flags]
Flags:
-r, --region string Start the specified region only (omit to start all regions)
Global Flags:
--config string Path to config file (default: $HOME/airctl-config.yaml)
--quiet Disable spinners
--verbose Print verbose logs to the console
-h, --help Show command help
```
### Start a Specific Region
{% tabs %}
{% tab title="Bash" %}
```bash
airctl start --config /opt/pf9/airctl/conf/airctl-config.yaml --region
```
{% endtab %}
{% endtabs %}
Example output:
{% tabs %}
{% tab title="Bash" %}
```bash
SUCCESS scaling up management plane
```
{% endtab %}
{% endtabs %}
### Start All Regions
To start all configured regions, omit the `--region` flag:
{% tabs %}
{% tab title="Bash" %}
```bash
airctl start --config /opt/pf9/airctl/conf/airctl-config.yaml
```
{% endtab %}
{% endtabs %}
## Verify the Management Plane Is Running
After starting the management plane, confirm that all services are ready using `airctl status`:
{% tabs %}
{% tab title="Bash" %}
```bash
airctl status --config /opt/pf9/airctl/conf/airctl-config.yaml --region
```
{% endtab %}
{% endtabs %}
Example output when the region is fully operational:
{% tabs %}
{% tab title="Bash" %}
```bash
------------- deployment details ---------------
fqdn:
region:
deployment status: ready
region health: ✅ Ready
-------- region service status ----------
desired services: 45
ready services: 45
```
{% endtab %}
{% endtabs %}
For more detail on the `airctl status` command and its flags, see [Viewing and Checking Region Status](/private-cloud-director/getting-started/self-hosted/airctl/viewing-and-checking-region-status.md).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.platform9.com/private-cloud-director/getting-started/self-hosted/airctl/start-and-stop-management-plane.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.