Apstra Server Upgrade Workflow

Table 1: Apstra 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 Juniper Apstra 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 environment.
Upgrade Apstra Server	Download the Apstra VM image. Install software on the controller VM and check configlets for conflicts. Install software on the worker VMs (new VMs with Apstra 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 agnets from the Apstra GUI.
Upgrade Worker Nodes (Apstra Cluster only)	For new VMs as worker nodes, import the state from the new controller. For reused VMs, install software on the worker VMs.
Upgrade Device NOS, as needed	Upgrade your devices to a qualified NOS version if their current versions are not compatible with the new Apstra version (see the Juniper Apstra User Guide for details).
Shut down old Apstra server	If upgrading an Apstra cluster, shut down old worker VMs after replacing them with new ones.
Roll back Apstra Server, as needed	Roll back to a previous Apstra version, if needed.