Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Apstra Server Upgrade Workflow

Stage Description
Pre-Upgrade Validation

  • Verify upgrade path is supported

  • Verify sufficient VM memory for new version

  • Check the new Apstra version release notes for config-rendering changes that could impact the data plane. Update configlets, as needed.

  • Review blueprints and address issues

  • Verify device models and OS versions are supported.

  • If you're using Junos devices and upgrading to Apstra version 4.2.1, make sure pristine configuration includes mgmt_junos VRF.

  • Remove any device AAA configuration

  • Remove any configlets used to configure firewalls

  • Back up current Apstra environment
Upgrade Apstra Server

  • Download Apstra VM image

  • Install software on controller VM (Check configlets for conflicts.)

  • Install software on worker VMs (new VMs with Apstra Cluster only)

  • Verify connections to new server

  • Import SysDB database (new VMs only)

  • Verify that configlets don’t conflict with newly rendered config

  • Log in to the upgraded server

  • Change operation mode to normal
Upgrade Agents

  • From the Apstra GUI
Upgrade Worker Nodes (Apstra Cluster only)

  • If using new VMs for worker nodes - import state from the new controller

  • If reusing VMs for worker nodes - install software on worker VM(s)
Upgrade Device NOS, as needed If the NOS versions of your devices are not qualified on the new Apstra version, upgrade them to a qualified version. (See the Juniper Apstra User Guide for details.)
Shut down old Apstra server If you're upgrading an Apstra cluster and you replaced your worker nodes with new VMs, shut down the old worker VMs as well.
Roll back Apstra Server, as needed

If you upgraded on a new VM, you can roll back to a previous Apstra version.