Upgrading Cisco VTS

This chapter provides information about how to upgrade frm Cisco VTS 2.3.1 to Cisco VTS 2.4.1

Before you upgrade, ensure that:
  • The Cisco VTS version is 2.3.1
  • In an HA setup, Both active and standby VTCs are online. You can check this using #sudo crm status
  • Cisco VTS is reachable using VIP IP address
  • Day Zero Configuration for Cisco VTS 2.4.1 is done

This chapter has the following section:

Upgrading Cisco VTS 2.3.1 to Cisco VTS 2.4.1

Do the following to upgrade from Cisco VTS 2.3.1 to 2.4.1.

    Step 1   On the active VTC VM, setup a shared drive which is accessible to be used a backup drive. For example: 
    root@controller:home/admin#mkdir extdrive
    Step 2   On active VM, mount external location for backup. 
    root@vts1:home/admin# apt-get install sshfs
root@vts1:home/admin#mkdir extdrive
root@vts1:home/admin#sshfs root@ipofcontroler:/home/admin/extdrive/ /home/admin/extdrive/
    Step 3   On the Active VM:
    1. Uninstall HA in case you have HA setup, using the following command (This upgrade uses ncs-backup from Active node only for further upgrade.): 
      sudo /opt/cisco/package/vtc/bin/uninstallHA.sh
    2. Update the following existing configuration in the file /etc/ncs/ncs.conf with new configuration.

      Existing Configuration (To be removed) 

      <japi>
    <new-session-timeout>PT1000S</new-session-timeout>
    <query-timeout>PT1000S</query-timeout>
    <connect-timeout>PT1000S</connect-timeout>
  </japi>
      New Configuration (To be added): 
      <japi>
    <new-session-timeout>PT86400S</new-session-timeout>
    <query-timeout>PT86400S</query-timeout>
    <connect-timeout>PT86400S</connect-timeout>
</japi>
    3. Run the command: 
      ncs --reload
    Step 4   On the Active VM:
    1. As root, copy the upgrade ISO from 2.4.1 build [for example, VTS-upgrade-version.iso] to any location on the VTC VM [for example: /home/admin].
    2. Mount the VTS upgrade ISO. For example: 
      mount –o loop /home/admin/VTS-upgrade-version.iso /mnt
    3. Run the upgrade script which available in /mnt/upgrades/python. 
      root@vts1:/mnt/upgrades/python#  python upgrade.py upgrade vtc -ip vip-ip  -b /home/admin/extdrive/

      After a successful upgrade, the following message is displayed: 

      {   'Host Agent': 'No Upgrade Required',
       'JDK and Apache ant': 'Upgraded',
       'NCS': 'No Upgrade Required',
       'Third Party Packages': 'No Upgrade Required',
       'VMM Plugins': 'No Upgrade Required',
       'VTC': 'Upgraded',
       'VTS GUI': 'No Upgrade Required'}
    Step 5   Back up the ncs db data to an external location. See Backing up ncs db Data.
    Step 6   Back up the credentials file from /var/vts/openstack to the external location.
    Step 7   Shutdown the active and the standby VTC.
    Step 8   Install two new VTC VMs for 2.4.1. See Installing Cisco VTS for details.

    If you have an HA deployment, install VTC 1 and VTC 2, which would be the active and standby VTC when you enable HA after the upgrade procedure is complete.

    Note    VTC 1 and VTC 2 denote the VTC VMs which would be the active and the standby, respectively, when you enable HA. Ensure that you do not setup HA until you complete the procedure mentioned in Step 10.
    Step 9   Create a directory (opt/nso/backups) and copy backup db file from external location to VTC 1 and VTC 2.
    Step 10   Restore ncs db data on VTC 1 and VTC 2. SeeRestoring ncs db Data for details.
    Step 11   Copy the credential file from external location to both active and standby at /opt/vts/etc (This is required for HA setup).
    Step 12   Setup HA. See Installing VTS in High Availability Mode for details.
    Step 13   On the active VM:
    1. As root, copy the upgrade ISO from 2.4.1 build [for example: VTS-upgrade-version.iso] to any location on the VTC vm [for example: /home/admin].
    2. Mount the VTS upgrade ISO. 
      mount –o loop /home/admin/VTS-upgrade-version.iso /mnt
    3. Run the upgrade script which available in /mnt/upgrades/python. 
       root@vts1:/mnt/upgrades/python#  python upgrade.py upgrade plugins -ip vip-ip  -p password -b /home/admin/extdrive/

      After a successful upgrade of plugins, the following message is displayed: 

       On Openstack: {   'Host Agent': 'Upgraded', 'VMM Plugins': 'Upgraded' }

On vCenter: {   'Host Agent': 'No Upgrade Required', 'VMM Plugins': 'Upgraded'}

    Backing up ncs db Data

    On a standalone VTC, run the following commands:

      Step 1   $ sudo su
      Step 2   $ source /etc/profile.d/ncs.sh
      Step 3   $ service ncs status 
      ncs start/running
      Step 4   $ service ncs stop 
      ncs stop/waiting
      Step 5   $ ncs-backup 
      INFO Backup
			 /var/opt/ncs/backups/ncs-4.1.1.3@2016-11-09T16:57:07.backup created
			 successfully
      Step 6   $ service ncs start 
      ncs start/running

      Backing up ncs db Data in an HA Deployment

      On the Active VTC, run the following commands:

        Step 1   $ sudo su
        Step 2   $ crm configure property maintenance-mode=true
        Step 3   $ source /etc/profile.d/ncs.sh
        Step 4   $ service ncs status 
        ncs start/running
        Step 5   $ service ncs stop 
        ncs stop/waiting
        Step 6   $ ncs-backup 
        INFO Backup
			 /var/opt/ncs/backups/ncs-4.1.1.3@2016-11-09T16:57:07.backup created
			 successfully
        Step 7   $ service ncs start 
        ncs start/running
        Step 8   $ crm configure property maintenance-mode=false

        Restoring ncs db Data

        Do the following to restore ncs db data.

        For an HA deployment, do these on the Active and Standby VMs.

          Step 1   $ sudo su
          Step 2   # source /etc/profile.d/ncs.sh
          Step 3   # service nso stop
          Step 4   # cd /opt/vts/etc/nso/
          Step 5   # cp ncs.conf ncs.conf_VTS241_original
          Step 6   # ncs-backup --install-dir /opt/nso --restore /opt/nso/backups/ backup filename.backup
          Step 7   # mv ncs.conf_VTS241_original ncs.conf
          Step 8   Change the permission of ncs.conf file to nso:nso
          Step 9   # service nso start

          Performing a Rollback

          If you encounter errors while installing and bringing up the new VTC VMs (from Step 7 in the upgrade procedure), you may do a rollback.

            Step 1   Shut down the newly brought up 2.4.1 VTC VMs.
            Step 2   Bring up the old VMs, you had shut down in Step 6 in the upgrade procedure.
            Step 3   Run the rollback script, which is available in /mnt/upgrades/python, on the active VM 
            root@vts1:/mnt/upgrades/python#  python upgrade.py rollback -ip vip-ip -b /home/admin/extdrive/