Manually Upgrading a Socket

This article explains the manual upgrade process for Socket sites.


Cato manages the Socket firmware upgrades and version control for Socket sites to make sure that they are running up-to-date versions. Major Socket versions are usually released quarterly. For more information, see Understanding Cato's Managed Socket Upgrade Service.

There are some scenarios where a Socket skipped an upgrade, for example, the Socket was not connected to the Cato Cloud during the maintenance window. When this happens, you will see a notification in the Cato Management Application, and you'll receive an email that the upgrade was skipped.

If that happens, you have the option to upgrade the Socket manually.

Upgrading the Socket

This section explains how to perform a manual upgrade of your Socket.

  • You can only upgrade one Socket at a time

  • Cato recommends as a best practice to upgrade to the latest Socket version

The upgrade process takes approximately 20 minutes, and downtime is approximately 2 minutes.

To manually upgrade the Socket

  1. From the Network page, select the Socket you want to upgrade.

  2. Navigate to Site Configuration > Socket.

  3. Click Actions > Upgrade.

    If there is already an upgrade in progress for this Socket, the Upgrade menu option is greyed out.

    1. Select the version to which to upgrade.

  4. Click Upgrade.

Manually Upgrading for HA Deployments

For HA deployments, Cato recommends that you first upgrade the primary Socket, which triggers a failover to the secondary Socket. The primary Socket completes the upgrade, including the downtime, and after approximately 20 minutes, you will receive an email notification that the upgrade was successful and the primary Socket is upgraded and stable.

At that point, you can upgrade the secondary Socket, which triggers a failover back to the primary Socket and after approximately 20 minutes, the HA status should be Up.

Was this article helpful?

1 out of 1 found this helpful


Add your comment