Overview
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.
If you would like to find out more about the upcoming versions, including release notes, see Quick Start for Virtual Appliances – Step 1: Getting Ready. Click Follow and updates to the forum will be e-mailed to you automatically.
As an Umbrella Admin, you can configure the schedule during which upgrades take place. We usually 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 virtual appliance.
IMPORTANT: In order for new versions to be automatically installed on the Virtual Appliances we require that a minimum of two Virtual Appliances are installed; otherwise, the only way to upgrade a virtual appliance by pressing the upgrade button in the dashboard.
Performing an in-place upgrade of a single virtual appliance 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.
We require that you have two VAs in place so 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, please 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:
- First, the API first checks if there is only a single VA in Site. If there is only one VA, the API does not offer a command to autoupgrade.
- Next, if there is a secondary VA for the Site but it is in an ERROR state, then the first VA will not autoupgrade.
- Then the API checks to see if a second VA for that site is already upgrading and if it is in a mid-upgrade state, if 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.
- Lastly, if all the prerequisite checks have been met, the VA is upgraded.
Automatic Upgrade for two or more Virtual Appliances
To view the version of your VAs can be seen in your dashboard and change the schedule:
- Login to the Umbrella dashboard and navigate to Settings > Sites and Active Directory.
- In the Version column, note the versions of the VA and AD Connectors.
- Change schedule time settings as required and click Set.
Time is UTC -08:00 based and the update window always show 01:00 PM UTC -08:00 as the end time.
Manual Upgrade for a single Virtual Appliance
- Login to the Umbrella dashboard and navigate to Settings > Sites and Active Directory.
- In the Version column, 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:
- Hover over the version number and click to expand the window:
- A green upgrade button displaying the latest version becomes available. In our example, the latest version is 1.3.12. The Virtual Appliances are several releases behind as they did not autoupgrade.
- Click Upgrade VA.
Before upgrade begins, a window opens reminding you that this upgrade will result in the loss of DNS service for the duration of the upgrade. We highly recommend that you perform an upgrade 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. - Click Upgrade Virtual Appliance.
Comments
0 comments
Article is closed for comments.