Upgrading Avaya Aura Web Gateway to a new version or release

Last Updated : Jun 05, 2026 |

About this task

Use this procedure to upgrade Avaya Aura® Web Gateway within the same major version. Avaya Aura® Web Gateway is automatically stopped for the upgrade and remains out of service until you restart it after the upgrade is completed.

Important:

Do not use this procedure to upgrade from Release 3.11 to 10.2.x. To upgrade from Release 3.11 to 10.2.x, you must use the migration procedures as described in Migrating Avaya Aura Web Gateway.
When upgrading an Avaya Aura® Web Gateway cluster, you can upgrade cluster nodes in any order. After the first node is upgraded, you can upgrade other nodes at the same time.
You can upgrade an Avaya Aura® Web Gateway cluster even if some nodes are turned off. You can upgrade these nodes later.

Before you begin

Download the required upgrade file from the Avaya support site. csa-10.2.x.x.x.bin is an example of an application layer upgrade file.
Ensure that the Avaya Aura® Web Gateway application is installed. Otherwise, the app upgrade command will not work. For more information about Avaya Aura® Web Gateway installation, see Deploying the Avaya Aura® Web Gateway.
Ensure that you know the enrollment password. Avaya Aura® Web Gateway does not store the enrollment password, so you must enter it during the upgrade.
In a cluster environment, if you use Avaya Spaces Calling Gateway, enable Maintenance mode as described in Enabling Maintenance mode.
Upgrade the system layer (operating system):
- For Avaya Aura® Web Gateway systems deployed using Avaya-provided OVAs, see the procedures in System layer (operating system) updates for virtual machines deployed using Avaya-provided OVAs.
  
  Important:
  In a cluster environment, update the system layer on all nodes before upgrading Avaya Aura® Web Gateway to a new version.
- For Avaya Aura® Web Gateway systems deployed as a software-only solution, see the procedures in Updating the system layer for software-only deployments.

Procedure

Transfer the upgrade file to the administrator home folder on the Avaya Aura® Web Gateway server using a file transfer tool of your choice.
Log in to the Avaya Aura® Web Gateway CLI as an administrator.
Set executable permissions on the upgrade file by using the following command:
```
chmod 770 <filename>
```
For example:
```
chmod 770 csa-10.2.x.x.x.bin
```
Run the following command to start the upgrade:
```
app upgrade <filename>
```
For example:
```
app upgrade csa-10.2.x.x.x.bin
```
Follow the prompts to complete the upgrade.
Restart services by running the svc csa restart command.

If you are upgrading a cluster, you can restart an upgraded node before the upgrade is completed on other nodes.

Next Steps

If WebRTC media adaptation was enabled in the previous Avaya Aura® Web Gateway release and if you are using Avaya Meetings Server Release 9.1.9 or later, configure WebRTC media adaptation as described in Configuring WebRTC media adaptation.
If the push notifications feature was enabled in the previous Avaya Aura® Web Gateway release and if you use the Avaya Push Notification provider, configure the Avaya Push Notification provider with the pnp.avaya.com provider address. For more information, see Reconfiguring the Avaya Push Notification provider after upgrade or migration.
Optionally, configure AIDE scanning as described in Advanced Intrusion Detection Environment tool management.
In a cluster environment, if you use Avaya Spaces Calling Gateway, disable Maintenance mode as described in Disabling Maintenance mode.

Send Feedback

AVAYA DOCUMENTATION CENTER

No results found