---
title: Scaling up the ASE cluster
description: Scale up the API Security Enforcer (ASE) cluster by adding one node at a time to an active cluster without disrupting traffic.
component: pingintelligence
version: 5.2
page_id: pingintelligence:pingintelligence_reference_guide:pingintelligence_scaling_up_the_ase_cluster
canonical_url: https://docs.pingidentity.com/pingintelligence/5.2/pingintelligence_reference_guide/pingintelligence_scaling_up_the_ase_cluster.html
revdate: May 6, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
  example: Example:
  result: Result:
---

# Scaling up the ASE cluster

Scale up the API Security Enforcer (ASE) cluster by adding one node at a time to an active cluster without disrupting traffic.

## About this task

To add a new cluster node:

## Steps

1. Enter the `peer_node` IP address or host name in the `cluster.conf` file of the ASE node.

   ### Example:

   If the IP of the first node is 192.168.20.121 with port 8020, then the `peer_node` parameter would be 192.168.20.121:8020.

   ```
   ; ASE cluster configuration. These configurations apply only when you have enabled cluster in the api_config file.
   ; Unique cluster ID for each cluster. All the nodes in the same cluster should have the same cluster ID.
   cluster_id=ase_cluster
   ; Cluster management port.
   cluster_manager_port=8020
   ; Cluster's active nodes. This can be a comma separated list of nodes in ipv4_address:cluster_manager_port format.
   peer_node=192.168.20.121:8020
   ```

2. Start the ASE node by changing the working directory to `bin`and running the `start.sh` script.

   ### Result:

   The new node synchronizes configuration and cookie data from the peer nodes. After loading, it becomes part of the cluster.