---
title: Restarting an ASE cluster
description: To ensure consistent cluster behavior, you should restart API Security Enforcer (ASE) cluster nodes, one node at a time.
component: pingintelligence
version: 5.2
page_id: pingintelligence:pingintelligence_reference_guide:pingintelligence_restarting_ase_cluster
canonical_url: https://docs.pingidentity.com/pingintelligence/5.2/pingintelligence_reference_guide/pingintelligence_restarting_ase_cluster.html
revdate: April 3, 2024
section_ids:
  steps: Steps
  example: Example:
---

# Restarting an ASE cluster

To ensure consistent cluster behavior, you should restart API Security Enforcer (ASE) cluster nodes, one node at a time.

## Steps

1. Stop all the nodes in the cluster by running the following command on any ASE node in the cluster:

   ```
   /opt/pingidentity/ase/bin/stop.sh cluster –u admin –p
   ```

2. Start the first node or management node in the cluster by running the following command:

   ```
   /opt/pingidentity/ase/bin/start.sh
   ```

   |   |                                                                                                                      |
   | - | -------------------------------------------------------------------------------------------------------------------- |
   |   | The first node or management node of the ASE cluster has the `peer_node` parameter empty in the `cluster.conf` file. |

3. Verify the status of the node by running the `status` command.

4. Start the next node in the cluster only after the status of the node changes to `started`.

   ### Example:

   ```
   /opt/pingidentity/ase/bin/cli.sh status -u admin -p
   Status: started
   ```

5. Repeat steps 2 and 3 for all the other nodes in the cluster to complete the cluster restart.