Introduction
This document provides step-by-step procedures for SD-WAN Controllers (vManage, vBond, and vSmart) upgrade and getting ready for Migration. We will also provide verification at each step and ensure we have achieved the specified task.
Prerequisite
- Have all the information regarding the controllers tabulated in one place before we start with the actual upgrades
| Controller Type |
Host-name |
System-IP |
Mgmt-IP |
Current SW version |
Upgrade to version |
SW download Link |
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
- Verify that all edge devices are compatible with the new software on the controllers
- Run Cisco SD-WAN SURE (also called AURA) command line to perform approx 30 tests on the SD-WAN vManage. The purpose of the tool is to prevent any potential failures and recommend corrective actions for a seamless upgrade process. The tool retrieves data from the vManage using GET API calls and show/shell commands. Learn more about the tool and download it from here.
- Controller images for an upgrade can be found here, and select the "SD-WAN Software Update" option.
- Now, we will upload the downloaded images to the vManage Repository. Login to vManage WebUI > Maintenance > Software Repository > Click "Add New Software" and choose vManage. In the pop-up window, either Browse for the image or Drag and drop the images and click Upload.
- Please "Do not refresh the Web Browser or click Web Browser Back button while the image is being uploaded"
Pre-Migration Task
vManage
- Capture the number of control connections from WebUI or CLI using "show control connections"
- Capture the number of device templates and feature templates
- Capture the number of devices from vManage UI > Configuration > Devices
- Check Centralized policy and take screenshots vManage UI > Configuration > Policies > Centralized Policy
- In the case of a cluster environment, make a note of what services are running on what node. Go to vManage UI > Administration > Cluster Management and take screenshots to compare at a later time
- Validate that the new software is present on the vManage repo. Go to vManage UI > Maintenance > Software Repository
- Take a vManage snapshot
- Take a configuration-db backup using "request nms configuration-db backup path /opt/data/backup/" and copy the file out and save it on the PC or server
vBond
- Capture the number of control connections from vManage WebUI or CLI using "show orchestrator connections"
- Capture the running configuration from the device
vSmart
- Verify the number of control connections from vManage WebUI or CLI using "show control connections"
- Capture the number of OMP sessions
- Capture the running configuration from the device
Migration Activity
Upgrade vManage
- Start the upgrade of vManage first from WebUI > Maintenance > Software Upgrade > vManage tab > Upgrade and make sure to select the correct image from the drop-down
- Once the image is copied and installed, we will have to Activate the image from WebUI > Maintenance > Software Upgrade > vManage tab > Activate and again select the correct image from the drop-down.
- Once the device boots up with the new image, we need to set the default image to the new image by going to WebUI > Maintenance > Software Upgrade > vManage tab > Set Default Version
- Delete the older image at this point as we cannot downgrade vManage once it is upgraded. From WebUI > Maintenance > Software Upgrade > vManage tab > choose "Delete Available Software", from the window that comes up, select the old image and click delete.
Upgrade vBond
- Once the vManage upgrade is complete, we can start with the vBond upgrade by going to WebUI > Maintenance > Software Upgrade > Controller Tab > vBond > Upgrade. From the drop-down, select the correct version to install on vBond
- Once the image is installed on vBond, we need to Activate the new image by going to WebUI > Maintenance > Software Upgrade > Controller Tab > vBond > Activate and select the correct image from the drop-down
- Once the vBond is reachable on vManage, we need to set the default image to the new image by going to WebUI > Maintenance > Software Upgrade > Controller tab > vBond > Set Default Version and select the newly upgraded image
Upgrade vSmart
- Once the vBond upgrade is complete, we can start with the vSmart and upgrade by going to WebUI > Maintenance > Software Upgrade > Controller Tab > vSmart > Upgrade. From the drop-down, select the correct version to install on vSmart
- Once the image is installed on vBond, we need to Activate the new image by going to WebUI > Maintenance > Software Upgrade > Controller Tab > vSmart > Activate and select the correct image from the drop-down
- Once the vBond is reachable on vManage, we need to set the default image to the new image by going to WebUI > Maintenance > Software Upgrade > Controller tab > vSmart> Set Default Version and select the newly upgraded image
Post Validation
vManage
- Verify control connections from WebUI or CLI using "show control connections"
- Verify the number of Device Templates, Feature Templates
- Verify Centralized policy and status are the same as before
- Verify the number of devices from WebUI
- Verify the services running on the individual nodes (in case of the cluster) are the same as before
vBond
vSmart
- Verify control connections
- Verify the config is the same as before
- Verify OMP sessions before and after
Rollback Activities
vManage
- In case of any failures on vManage, open the Cisco TAC case and work on debugging the issue
- If we are unable to resolve the issue then rollback vManage to the previous version using the snapshot taken
vBond
- Depending on the issue, we will have to open a TAC case and work on debugging the issue
- If unable to resolve, downgrade the vBond to the previous image by activating the older image
vSmart
- Depending on the issue, we will have to open a TAC case and work on debugging the issue
- If unable to resolve, downgrade the vSmart to the older image by activating the older image
