> ## Documentation Index
> Fetch the complete documentation index at: https://dpos.xdr.ooo/llms.txt
> Use this file to discover all available pages before exploring further.

# DP Client Upgrade Commands

> Use Menu 7 as the authoritative source for DP-side commands and cluster execution order.

# DP Client Upgrade Commands

Open **Menu 7 — Show DP Client Upgrade Commands** only after Menu 4 reports `PASS`.

Menu 7 generates commands from the current Preparation Mode, Mirror Server IP, and cluster configuration. Do not construct equivalent commands manually unless the release procedure explicitly requires it.

The generated output is also saved at:

```text theme={null}
/var/log/ubuntu-mirror-automation/dp-client-upgrade-commands.txt
```

## Cluster execution model

For clustered deployments, the current workflow separates common node preparation from final master orchestration.

| Steps            | Run on                                                  |
| ---------------- | ------------------------------------------------------- |
| Common steps 1–6 | DL master + all DL workers + DA master + all DA workers |
| Final DL step    | DL master only                                          |
| Final DA step    | DA master only                                          |

The exact step numbers shown by Menu 7 can differ by Preparation Mode; follow the generated output.

Key rules:

* complete the common staging/prerequisite steps on **all** target nodes first
* run final bringup from the DL master using its configured DL workers
* run final bringup from the DA master using its configured DA workers
* do not manually run the final master-orchestration step on workers
* for AIO/single-node, no worker flags or worker password are added

## If the Mirror Server IP changes

Do not reuse previously generated commands. Update the saved Mirror Server IP, rerun the required preparation/publish/readiness steps, and generate a new Menu 7 output.

## Security

Menu 7 may include environment-specific command material. Treat the generated file as operational data and do not publish passwords, tokens, or internal credentials in external tickets or public documentation.