The Umbrella Documentation Hub

Welcome to the Umbrella documentation hub. Here you'll find access to all of our Cisco Umbrella user guides.

Get Started    

Appendix A – Updates

New software versions for virtual appliances (VAs) become available automatically and are usually applied without any user intervention required. However, you must have two VAs in order for automatic upgrades to take place to ensure high availability of DNS services.

Both the connector and the VA are capable of automatic updates. To download updates these components require access to the following URL:

  • 443 (TCP) to
  • 443 (TCP) to

If you would like to find out more about the upcoming versions, including release notes, see Service Updates. Click Follow to receive update notifications.

As an Umbrella administrator, you can configure the schedule during which upgrades take place. We recommend this be done during non-business hours.

These instructions also describe how to upgrade a single virtual appliance, which will result in downtime for your internet connectivity as there is no failover for high availability with a single VA.


In order for new versions to be automatically installed on the VAs we require that a minimum of two VAs be installed; otherwise, the only way to upgrade a VA is to click the upgrade button in the dashboard.

Performing an in-place upgrade of a single VA will result in up to 15 minutes of downtime during which time you will not be able to perform DNS queries on the network, and effectively will not have internet service.

Before you begin, you must have two VAs in place so that there is no downtime or interruption in service during the upgrade process.

How the Upgrade Process Takes Place

In order to ensure the VAs are updated in an orderly manner, the upgrade for the VA is controlled by commands from the Umbrella API that the VA are connected to. This means you cannot decide which VA is upgraded automatically. If you wish to upgrade a particular VA first, do this manually as described later in this section. Logic is built-in to our API to prevent two VAs at a single site from upgrading at once or upgrading when one of the VAs is in an error state. The following checks are performed:

  1. The API checks if there is only a single VA for the site. If there is only one VA, the API does not offer a command to autoupgrade.
  2. If there is a secondary VA for the site but it is in an ERROR state, then the first VA will not autoupgrade.
  3. The API checks to see if a second VA for that site is already upgrading and if it is in a mid-upgrade state it will not autoupgrade during that window of time. If we have ordered a VA to upgrade and have not heard back that it has complete, this qualifies as mid-upgrade state.
  4. If all the prerequisite checks have been met, the VA is upgraded.

Automatic Upgrade for Two or More Virtual Appliances

Your VA's version can be seen in your Umbrella dashboard.

  1. Navigate to Deployments > Configuration > Sites and Active Directory.
  2. Check under the Version column to note the versions of the VA and AD Connectors.
  3. You should see the following options underneath Sites & Active Directory.

You can change these settings to meet your needs, making sure to note that the time is UTC -08:00 based.

The update window will always show 01:00 PM UTC -08:00 as the end time.

Manual Upgrade for a Single Virtual Appliance

  1. Navigate to Deployments > Configuration > Sites and Active Directory.
  2. Check under the Version column to note the versions of the VA and AD Connectors. If a VA or AD Connector is out of date, you will see a yellow triangle alert.
  1. Hover over the version number and click to expand the window.
    A button appears listing the version available to which you can upgrade.
  1. Click Upgrade VA to start the upgrade process.

Before the upgrade takes place, there is a warning window reminding you that this upgrade will result in the loss of DNS service for the duration of the upgrade. We highly recommend that the upgrade is done during non-business hours, or preferably, that a second VA for this site is deployed in order to automate the process of upgrades without introducing any down time.

  1. Click Upgrade Virtual Appliance.

Configure Anycast < Appendix A – Updates > Appendix B – Sizing Guide

Updated about a year ago

Appendix A – Updates

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.