Upgrading VTC
Before you upgrade, ensure that:
-
Cisco VTS is running version 2.6.5.
-
The admin has taken the backups for Day Zero and Day One configurations for all the switches managed by Cisco VTS.
See Device documentation for the procedure about how to copy Day Zero configuration locally.
-
In an HA set up, HA status is checked on both the VMs. On the Cisco VTS GUI, check HA status under Administration > High Availability Or, you may use the following command:
# sudo crm status
-
In an HA setup, both VTCs are online, and one is set as Master and other is set as Slave.
-
In an HA setup, service nso status of both VTCs is in active (running) state.
-
In an HA setup, VTS is reachable using the VIP IP address (the IP address used to log in to the Cisco VTS GUI).
-
The VTS virtual machines have enough disk-space before starting the upgrade. See Prerequisites chapter for details.
-
All the devices in the inventory are reachable and accessible via Cisco VTS. Use the check-sync functionality to make sure all devices are in sync (Inventory > Network Inventory GUI).
- For devices that you want to be in unmanaged state, you set the devices to unmanaged mode:
set devices device [device_name] [device_extension]:device-info device-use unmanaged commit
Examples:
When a device is specified as unmanaged, Cisco VTS will not sync with these devices as part of the upgrade process. Hence, if before upgrade, you use the above command to mark the devices that are not managed by Cisco VTS, then VTS will not sync with these devices and this will not cause a failure during the upgrade.set devices device asr-dci1 asr9k-extension:device-info device-use unmanaged set devices device n9k-leaf n9k-extension:device-info device-use unmanaged
-
Devices are in unlocked state (check Inventory > Network Inventory GUI).
-
You back up the current VTC VMs (Master and Slave) as snapshots which will need to be used to rollback if there is any problem found during the upgrade.
Note |
VTC and VTS are interchangeable. "Source VTC/VTS System" can be in 2.6.5. |
If there are service extensions or device template is configured, then follow steps mentioned in VTS Service Extension and Device Templates Migration section.
Procedure
Step 1 |
Take the snapshot of the existing VTC VM. See Backing up VTC VMs as Snapshots for details. |
||
Step 2 |
Download vts-backup.sh from Cisco.com, to your VTC VM (Master VTC in an HA setup). |
||
Step 3 |
Go to root user using sudo su - from admin user login. |
||
Step 4 |
Run the following command on the source VTC system.
This command backs up log files, including device configuration, and generates a tar file. Copy the tar file outside of the VTC host. This file will be required for troubleshooting purpose. This needs to be done on both VTC nodes in case of an HA setup. |
||
Step 5 |
Run the backup script to take a backup of the database, credential files, and templates of source VTC. This copies the backup tar file to a local directory and the home directory of the remote server you specify.
|
||
Step 6 |
Shutdown the current VTC VM (both Master and Slave in case of HA). |
||
Step 7 |
Bring up the new VTC VM with the 2.6.6 image, with the same management IP address (both Master and Slave VTC VM in case of HA). |
||
Step 8 |
Copy the vts-backup.tgz backup file created on 2.6.5 VM from a remote location to current VTC. |
||
Step 9 |
Copy the upgrade ISO file from cisco.com to a local directory on VTC VM. |
||
Step 10 |
Log in to VTC VM (Master VTC in case of HA) as root user using sudo su - from admin user login. |
||
Step 11 |
Create a mount directory.
|
||
Step 12 |
Mount the ISO which is copied to the local directory to /mnt/vts-upgrade
|
||
Step 13 |
Enter into the mount directory.
|
||
Step 14 |
Run the upgrade script as ./upgrade.sh <backup tar file with path>.
|
||
Step 15 |
Run the following command, as root user.
This command backs up log files, including device configuration, and generates a tar file. Copy the tar file outside of the VTC host. This file will be required for troubleshooting purpose. This needs to be done on both VTC nodes in case of an HA setup.
|
||
Step 16 |
Log in to VIP and do sync-to to all devices, except for VTSR. |
Backing up VTC VMs as Snapshots
Saving VTC snapshots involves:
-
On vCenter—Need to be done for all VTC VMs (Master and Slave):
-
Power Off the VTC VM (recommended)
-
Right click on the VTC VM, select Snapshot, and then select Take Snapshot....
-
Enter Name and Description for snapshot and click Ok.
-
Power on the VTC VM.
-
-
On OpenStack—Need to be done for all VTC VMs (Master and Slave):
-
Shutdown the VTC VMs to take snapshot using virsh save utility. VTC VMs will no longer be available in running state.
Run virsh list, which shows the VTC domain ID, name, and status. Use Domain ID to save VTC VMs. root@vts-controller-110 ]# virsh list Id Name State ------------------------------------- 236 VTC1 running 237 VTC2 running
virsh save <id> <file>
For example:
virsh save <VTC Domain ID> <file>
virsh save 236 vtc1.txt virsh save 237 vtc2.txt
-
Take vtc.qcow2 image backup which was used to bring up Master and Slave.
tar –cvf vtc1.qcow2.tar vtc1.qcow2 tar –cvf vtc2.qcow2.tar vtc2.qcow2
-
Copy tar images to external drive (vtc1.qcow2.tar ,vtc2.qcow2.tar are VTC snapshots, which will be used to rollback).
-
Restore VTC VMs which will bring VTC VMs back to running state.
virsh restore vtc1.txt virsh restore vtc2.txt
-
Verify if Master and Slave are up and running in HA mode. Verify GUI login using VIP IP.
-
Preserving Out of Band Template Configuration
If you have out of band template configuration in 2.6.5 and want to upgrade to 2.6.6, do the following to ensure that the out of band template configuration is preserved after you upgrade to 2.6.6 without any interruption to the data plane.
Procedure
Step 1 |
Upgrade to VTS 2.6.6 without doing a sync-to.
|
Step 2 |
Run sync-to dry-run.
|
Step 3 |
Check /opt/vts/run/upgrade/ folder with files having non-zero size. |
Step 4 |
If there are files with non-zero size, then Southbound lock all the devices.
|
Step 5 |
Create templates that contain the out of band configuration and apply the templates. Configuration with - sign will be removed from device configuration. Configuration with + sign will be added to device configuration. |
Step 6 |
Unlock all the devices.
|
Step 7 |
Do a sync-to to all the devices.
|