Migrate an existing deployment to v2.2

The 2.2 release brings a significant change to the base platform configuration and capabilities of the Airwall Gateway.

Airwall Gateway versatility is dramatically increased. To achieve this, this version gives up some functional interoperability between 2.2 and prior versions of Airwall Edge Services and the Conductor. A v2.2 Conductor cannot manage Airwall Edge Services on any version before v2.0. While most things still work across versions 2.0.x, 2.1.x and 2.2 during your upgrade, a best practice is to migrate 2.2.x deployments completely as soon as possible using the following order:

  1. Upgrade your Conductor to 2.1.6
  2. Upgrade all Airwall Edge Services to 2.1.6
  3. Upgrade your Conductor to 2.2.0
  4. Upgrade all Airwall Edge Services to 2.2.0

For more information on upgrading your Conductor to 2.1.6 from prior versions, contact Customer Success.