# Managing Your Network

> Learn how to start, stop, and restart consensus nodes, reset the ledger to genesis, capture logs and diagnostics, and troubleshoot a running Solo network. Master day-to-day network operations and troubleshooting.

URL: https://solo.hiero.org/docs/simple-solo-setup/managing-your-network/

## Overview

This guide covers day-to-day management operations for a running Solo network,
including starting, stopping, and restarting nodes, resetting the ledger to
genesis, capturing logs, and troubleshooting.

## Prerequisites

Before proceeding, ensure you have completed the following:

- **[System Readiness](https://solo.hiero.org/docs/simple-solo-setup/system-readiness)** - your local environment meets all hardware and software requirements.
- **[Quickstart](https://solo.hiero.org/docs/simple-solo-setup/quickstart)** - you have a running Solo network deployed using `solo one-shot single deploy`.

> **Note:** If you need to upgrade an existing Solo network, see
> [Upgrade Your Network](https://solo.hiero.org/docs/simple-solo-setup/upgrade-your-network).

```bash
solo one-shot show deployment
```

Expected output — the deployment name you passed to `solo one-shot single deploy`, or the default `one-shot` if you did not specify `--deployment`:

  ```bash
  Deployment Name: one-shot (default)
  ```

Most management commands require your deployment name. Find it with `solo one-shot show deployment` — see [Capture your deployment name](https://solo.hiero.org/docs/simple-solo-setup/quickstart#capture-your-deployment-name). It defaults to `one-shot` unless you passed `--deployment`. Use it as `<deployment-name>` in all commands on this page.

## Stopping and Starting Nodes

> **Important:** The `solo consensus node` stop/start/restart commands act on
> **consensus nodes only**. They do not stop the mirror node, Hiero Explorer,
> JSON-RPC relay, block node, or the shared services (PostgreSQL, Redis,
> MinIO) - those keep running. Solo has no stop/start command for the
> non-consensus components (their lifecycle is `add`/`destroy`). To pause the
> whole network without deleting any pods, see [Stop the entire network](#stop-the-entire-network).

### Stop consensus nodes
Pause the consensus node(s) without destroying the deployment:

```bash
solo consensus node stop --deployment <deployment-name>
```

### Start consensus nodes
Bring stopped consensus node(s) back online:

```bash
solo consensus node start --deployment <deployment-name>
```

### Restart consensus nodes
Stop and start all consensus nodes in a single operation:

```bash
solo consensus node restart --deployment <deployment-name>
```

To verify pod status after any of the above commands, see [Verify the network](https://solo.hiero.org/docs/simple-solo-setup/quickstart#verify-the-network) in the Quickstart guide.

> **Stop/start vs. ledger reset:** `stop`/`start`/`restart` pause and resume
> consensus nodes without touching ledger state — accounts, balances, and
> transaction history are preserved. To return the ledger to genesis and
> discard all on-ledger state, see
> [Reset the ledger to genesis](#reset-the-ledger-to-genesis).

### Stop the entire network

To pause the **entire** network while preserving its state - for example, to
free up memory while working on other tasks - stop the Kind cluster's container
instead of the workloads inside it. This stops every pod without deleting any
of them, so the data on the consensus node's `emptyDir` volumes (platform
software, keys, configuration, and saved state) is kept.

Find the Kind cluster container name and stop it:

**Docker**
```bash
docker ps --filter name=solo-cluster --format '{{.Names}}'
docker stop <container-name>
```

**Podman**
```bash
podman ps --filter name=solo-cluster --format '{{.Names}}'
podman stop <container-name>
```

The container name is typically `solo-cluster-control-plane`. On macOS and
Windows you can also do this from the Docker Desktop (or Podman Desktop)
dashboard: find the container and click **Stop**.

To bring the network back online, start the container and restore
port-forwards:

**Docker**
```bash
docker start <container-name>
solo deployment port-forwards refresh --deployment <deployment-name>
```

**Podman**
```bash
podman start <container-name>
solo deployment port-forwards refresh --deployment <deployment-name>
```

> **Warning:** Do not use `kubectl scale --replicas=0` to stop the entire
> network. Scaling pods to zero deletes them, which wipes the consensus node's
> `emptyDir` volumes. The consensus node will fail to restart correctly after
> scaling back up. Use the container stop/start commands above instead.

> **Note:** To remove the network entirely (cluster, volumes, and
> configuration), use `solo one-shot single destroy` - see the
> [Cleanup guide](https://solo.hiero.org/docs/simple-solo-setup/cleanup).

### Verify Network is Working

To confirm your Hedera network is fully operational, create a test account using the Ledger account creation command:

```bash
solo ledger account create --deployment <deployment-name>
```

Expected output:

```bash
 *** new account created ***
-------------------------------------------------------------------------------
{
  "accountId": "0.0.1001",
  "publicKey": "302a300506032b6570032100439379b330f3b57b5deffda196c7c0c3387f3330a838c021954303e260606f24",
  "balance": 100
}
```

Once the account is created, verify it in the web-based Explorer UI:

1. Open your browser to **http://localhost:38080**
2. In the search bar, enter the account ID (e.g., `0.0.1001`)
3. View the account details, balance, and transaction history

This confirms that:
* The network is processing transactions
* The consensus node is responding correctly
* The mirror node is indexing transactions
* The explorer is displaying data properly

## Reset the ledger to genesis

To return a running deployment to a clean genesis state without tearing it down
and redeploying, reset the ledger system. This clears the saved consensus state
and ledger-related secrets, returning the ledger to genesis - with no accounts,
files, or balances beyond the genesis defaults:

```bash
solo ledger system reset --deployment <deployment-name>
```

`solo ledger system reset` is the counterpart to `solo ledger system init`
(which initializes a new deployment). Use it when you want a fresh ledger - for
example, to rerun a scenario from a known starting point - while keeping the
same Kind cluster and deployment.

| Flag | Description |
| --- | --- |
| `--deployment` | The deployment to reset. |
| `--node-aliases` | Comma-separated consensus node aliases to reset. Defaults to all nodes in the deployment. |
| `--cluster-ref` | The cluster reference, for a deployment that spans multiple clusters. |

> **Note:** This discards on-ledger state created since genesis and cannot be
> undone. It does not delete the cluster or deployment - to remove those
> entirely, use `solo one-shot single destroy` (see the
> [Cleanup guide](https://solo.hiero.org/docs/simple-solo-setup/cleanup)).

## Viewing Logs

To capture logs and diagnostic information for your deployment:

  ```bash
  solo deployment diagnostics all --deployment <deployment-name>
  ```

Logs are saved to `~/.solo/logs/` (on native Windows, `$env:USERPROFILE\.solo\logs\`).

**Expected output**:

  ```bash
  ******************************* Solo *********************************************
  Version : 0.59.1
  Kubernetes Context : kind-solo
  Kubernetes Cluster : kind-solo
  Current Command : deployment diagnostics all --deployment <deployment-name>
  **********************************************************************************
  
  ✔ Initialize [0.3s]
  ✔ Get consensus node logs and configs [15s]
  ✔ Get Helm chart values from all releases [2s]
  ✔ Downloaded logs from 10 Hiero component pods [1s]
  ✔ Get node states [10s]
  
  Configurations and logs saved to /Users/<username>/.solo/logs
  Log zip file network-node1-0-log-config.zip downloaded to /Users/<username>/.solo/logs/<deployment-name>
  Helm chart values saved to /Users/<username>/.solo/logs/helm-chart-values
  ```

You can also retrieve logs for a specific pod directly using `kubectl`:

  ```bash
  kubectl logs -n <namespace> <pod-name>
  ```

> **Important:** Solo deploys each network into a Kubernetes namespace. For one-shot deployments, the namespace defaults to `one-shot` (matching the default deployment name). You can override it by passing `--namespace` to `solo one-shot single deploy`.

To find your deployment namespace, use any of:

  ```bash
  # Look up the namespace Solo recorded for this deployment
  solo deployment config info --deployment <deployment-name>

  # Or list all namespaces and pick the one matching your deployment
  kubectl get ns

  # Or inspect pods and use the NAMESPACE column
  kubectl get pods -A | grep -v kube-system
  ```

For one-shot deployments the namespace matches the deployment name, which defaults to `one-shot` unless you passed `--deployment` (retrieve it with `solo one-shot show deployment`).

Replace `<namespace>` and `<pod-name>` with the values from your deployment.
