# Load balancing across active DMZ clusters for outbound file transfers

In a complex architecture composed of multiple DMZ components, load distribution can be implemented across all elements to optimize and enhance overall performance. The load can be distributed equally, either randomly or in round robin mode, on each STENG.

To manage and balance outbound file transfer loads across all active DMZ clusters with at least one active gateway, add the `load-balancing-policy` advanced setting by following these steps:

1. Go to **Setup** → **Advanced Settings**.
2. Click the **New** button and enter these fields:
   1. **Module**: ghibli-dmz
   2. **Section**: outbound-routes
   3. **Property name**: load-balancing-policy
   4. **Property value**: random (default) or roundrobin
      1. **random**: the STENG randomly selects which cluster to route the outbound connection to.
      2. **roundrobin**: the STENG sequentially cycles through all its DMZ clusters for outbound connections.
3. Click **Confirm**.

This advanced property is read at runtime and takes effect after a one-minute interval. If the key is not set, the default is set to `random`.

If a gateway is disabled, it will be automatically excluded from the load-balancing process.

If a new active gateway is added, it will be automatically included in the load balancing. If this active gateway belongs to a DMZ cluster configured on the peer, it will be used from the set of DMZ clusters available for selection.


---

# Agent Instructions: 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:

```
GET https://docs.primeur.com/data-mover-1.21/infrastructure/dmz-clusters/load-balancing-across-active-dmz-clusters-for-outbound-file-transfers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.