Apstra DCD Server Upgrade Workflow

Table 1: Apstra DCD Server Upgrade Workflow
Stage	Description
Pre-Upgrade Validation	Verify the upgrade path is supported. Ensure sufficient VM memory for the new version. Check for any config-rendering changes affecting the data plane, see the Apstra DCD Release Notes. Update configlets, as needed. Review blueprints and resolve issues. Confirm device models and OS versions are supported. For Junos devices, ensure pristine configuration includes `mgmt_junos` VRF. Remove device AAA configuration. Delete configlets for firewalls setup. Back up the current Apstra DCD environment.
Upgrade Apstra DCD Server	Download the Apstra DCD VM image. Install software on the controller VM and check configlets for conflicts. Install software on the worker VMs (new VMs with Apstra DCD Cluster only). Verify connections to the new server. Import the SysDB database. Verify that configlets do not conflict with the newly rendered configuration. Log in to the upgraded server. Change operation mode to normal mode.
Upgrade Agents	Upgrade agents from the Apstra DCD GUI.
Upgrade Worker Nodes (Apstra DCD Cluster only)	For new VMs as worker nodes, import the state from the new controller.
Upgrade Device NOS, as needed	Upgrade your devices to a qualified NOS version if their current versions are not compatible with the new Apstra DCD version (see the Apstra DCD User Guide for details).
Shut down old Apstra DCD server	If upgrading an Apstra DCD cluster, shut down old worker VMs after replacing them with new ones.
Roll back Apstra DCD Server, as needed	Roll back to a previous Apstra DCD version, if needed.