Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Upgrade Paths and Workflow

Apstra Server Supported Upgrade Paths

  • First major release versions are for new Juniper Apstra installations only. You cannot upgrade to a first major release version (to 4.1.0 for example).
  • You can upgrade to maintenance release versions and later (to 4.1.1 for example).
  • To check your current Apstra version from the Apstra web GUI navigate to Platform > About from the left navigation menu.
  • To check your current Apstra version from the CLI run the command service aos show_version.

Supported Upgrade Paths to Version 4.1.1

Table 1: Apstra Server Upgrade Paths to Version 4.1.1
From Version VM-to-VM (on new VM) In-Place (on Same VM)
4.1.0 Yes (recommended for production) Yes
4.0.2 Yes No
4.0.1 Yes No
4.0.0 Yes No

Upgrading from Apstra release versions 3.X are not supported.

Apstra Server Upgrade Workflow

Table 2: Apstra Upgrade Workflow
Stage Description
Pre-Upgrade Validation
  • Verify upgrade path is supported
  • Verify sufficient VM memory for new version
  • Review blueprints and address issues
  • Verify device OS versions are supported
  • 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)
  • Log into new server
  • Change operation mode to normal
Upgrade Agents
  • From the Apstra web GUI
Upgrade Worker Nodes (Apstra Cluster only)
  • If re-using VMs for worker nodes - import state
  • If using new VMs for worker nodes - install software on worker VM(s)