Guest

Cisco Virtual Application Cloud Segmentation Services Installation and Upgrade Guide, Release 5.4STV3.0

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco Virtual Application Cloud Segmentation Services Installation and Upgrade Guide, Release 5.4STV3.0

Chapter Title

Upgrading Cisco VACS

Results

Updated:
June 16, 2016

Chapter: Upgrading Cisco VACS

Upgrading Cisco VACS

This chapter contains the following sections:

About Upgrading Cisco VACS

You can upgrade the earlier versions of Cisco VACS to Cisco VACS Release 5.4STV3.0 by applying the Cisco VACS patch to the Cisco UCS Director.

This upgrade process is not revocable. Hence, after you upgrade the software, you cannot downgrade this software to the previous release.

Guidelines and Limitations

Follow these guidelines and limitations while upgrading the Cisco VACS:
  • We recommend that you upgrade Cisco UCS Director to Release 5.4.0.3 before upgrading the Cisco VACS software.

    Note

    For information on upgrading Cisco UCS Director to Release 5.4 and later, see the Upgrading Cisco UCS Director to Release 5.4 section.

  • The following upgrade path is supported and recommended:

    • Cisco UCS Director Release 5.4.0.2 + Cisco VACS Release 5.3STV2.1.2 > Cisco UCS Director Release 5.4.0.3 + Cisco VACS Release 5.4STV3.0.

    • Cisco UCS Director Release 5.4.0.2 + Cisco VACS Release 5.3STV2.1.1 > Cisco UCS Director Release 5.4.0.3 + Cisco VACS Release 5.4STV3.0.

    • Cisco UCS Director Release 5.3.1.2 + Cisco VACS Release 5.3STV2.0.1 > Cisco UCS Director Release 5.4 > Cisco UCS Director Release 5.4.0.3 + Cisco VACS Release 5.4STV3.0.

      Note

      We recommend that you upgrade Cisco UCS Director to Release 5.4.0.3, although it is optional if you are on Cisco UCS Director Release 5.4.0.2.

Prerequisites for Upgrading the Cisco VACS

Upgrading the Cisco VACS has the following prerequisites:
  • You have installed Cisco UCS Director Release 5.4 and the 5.4 based patch releases.

    Note

    We recommend that you install it on Cisco UCS Director Release patch 5.4.0.3.

  • The setup meets the system requirements with respect to the memory, disk size, and so on.

  • You have administrator privileges to install Cisco VACS and the components.

Process Flowchart to Upgrade Cisco VACS

Use the procedures in this chapter and the following workflow as a guide to upgrade Cisco VACS.
Figure 1. Process Workflow—Upgrading Cisco VACS



Upgrading Cisco VACS

Before You Begin

  • Download the Cisco VACS patch from http:/​/​www.cisco.com. This patch file is a signed zip file with the following format: VACS-5_4_STV_3_0-pkg.zip.

  • If NFS mount is used for application storage, disable it before you apply a patch. If you do not, the upgrade will fail.

Attention:

Unzip the zip file and place the software in the FTP or HTTP server that you plan to use to install the Cisco VACS patch.

    Step 1   Start your current version of Cisco UCS Director.
    Step 2   Log in to the SSH application using the shelladmin credentials and proceed to the Cisco UCS Director Shell Menu, and enter the appropriate numbers from this menu.
    Step 3   In the shelladmin, choose Stop services to stop all services.
    Step 4   To verify that all services are stopped, choose Display services status.
    Step 5   (Optional)If desired, you can choose Backup database to back up the Cisco UCS Director database.

    You do not need to back up the database if you took a snapshot of the VM before you started.

    Step 6   To apply the Cisco VACS patch, choose Apply patch.
    Step 7   When prompted, enter the location of the Cisco VACS patch.

    ftp://username:password@hostname|IP_address/software_location_and_name or http://http server name|IP_address/software_location_and_name.

    Note   

    In this procedure, we are using the FTP option to install the Cisco VACS patch.

    Step 8   Wait for the download and installation to complete.
    Step 9   When prompted, choose Start services to start services and complete the installation process.
    Upon a successful VACS patch installation (or an upgrade), you see the following options on the screen: 
     
vacs_pre_install_3.0.sh Begin .....
vacs_pre_install_3.0.sh End
vacs_post_install_3.0.sh Begin .....
vacs_post_install_3.0.sh End
Completed installing package 0
    Note   

    • After you apply the Cisco VACS patch and complete that installation, choose the Start Services option of ShellAdmin to start/restart the Cisco UCS Director services and complete the patch process. The patch process is not complete or successful until the Cisco UCS Director services have started, Cisco UCS Director is available, the login screen is displayed, and the admin user can log in to Cisco UCS Director.

      All Cisco UCS Director services must be started before you attempt to perform other shelladmin procedures, such as apply additional patches, take a database backup, or restore a database from a backup.

    • If the inframgr services are not running after you upgrade to Cisco UCS Director Release 5.4, you must restart Cisco UCS Director.

    Upgrading Cisco Virtual Switch Update Manager

    The Cisco VSUM upgrade is done automatically as a part of the post-install script of the Cisco VACS patch application. This script checks for an existing Cisco VSUM available for every virtual account and upgrades it to Release 1.5.6.

    Note

    • It is important that you upgrade Cisco VSUM before you upgrade VMware vSphere to Release 6.0.

    • If the Cisco VSUM upgrade process fails, see the Problems with Upgrading Cisco VACS section for the solution.

    Verifying the Cisco VACS Upgrade Process

    You can verify the Cisco VACS upgrade using any one of the following methods:

    1. Log in to the Cisco UCS Director through the web browser (with the admin credentials), and choose Solutions > VACS Container. You can view the Cisco VACS solution task icons.

    2. Log in to the Cisco UCS Director through the web browser (with the admin credentials), and choose Solutions > VACS Container > About VACS. You can view the installed version of Cisco VACS The installed version will be 5.4STV3.0.

    Verifying the Cisco VSUM Upgrade Process

    You can verify the Cisco VACS upgrade using any one of the following methods:

      Step 1   Check the console logs of the patch install done via the shelladmin login to Cisco UCS Director. The follows logs are seen at the end of the upgrade process: 
      Printing the VSUM upgrade report

==================================
          VSUM Upgrade Report         
==================================

======
VSUM 1
======

Name           : vsum
IP Address     : 192.168.0.1
vCenter_ip     : 192.168.255.254
Upgrade Status : Success
Errors         : None
      Step 2   Verify the Upgrade status for VSUM. The upgrade process is successful if the upgrade status displays as Success. If the upgrade status displays failure, see the Problems with Upgrading Cisco VACS section to re-run the upgrade process.

      (Optional) Upgrading Cisco Cloud Services Router (CSR) 1000V

      You must upgrade Cisco CSR 1000V if the Cisco VACS version that you are using is a version earlier than Release 5.4STV2.1. In this case, you must migrate Cisco Cloud Services Router 1000V (CSR) from Release 3.14 to release 3.16.1a.
      Before You Begin

      Install a SCP server or an RCP server application on a TCP/IP-ready workstation or PC.

        Step 1   Download the Cisco CSR 1000V file (csr1000v-universalk9.03.16.01a.S.155-3.S1a-ext.SPA.bin) from https:/​/​software.cisco.com/​download/​release.html?mdfid=284364978&softwareid=282046477&release=3.16.1aS.
        Step 2   Log into the Cisco CSR 1000V VM and copy the downloaded system file to the boot flash. 
        buni01-primary-10#copy scp: bootflash:
Address or name of remote host []?172.31.255.254
Source username [admin]? user1
Source filename []? /bkup/csr1000v-universalk9.03.16.01a.S.155-3.S1a-ext.SPA.bin
Destination finename [csr1000v-universalk9.03.16.01a.S.155-3.S1a-ext.SPA.bin]?
Passwored:
 Sending file modes: C0640 354917760 csr1000v-universalk9.03.16.01a.S.155-3.S1a-ext.SPA.bin
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
        Step 3   Verify that the image is available in the bootflash. 
        buni01-primary-10#sh bootflash: | inc bin
27         73 Nov 07 2015 07:04:48 +00:00 /bootflash/tracelogs/binos_log_R0-0.log
67  354917760 Nov 10 2015 10:23:49 +00:00 /bootflash/csr1000v-universalk9.03.16.01a.S.155-3.S1a-ext.SPA.bin
        Step 4   Deregister the current smart license. 
        buni01-primary-10#license smart deregister
buni01-primary-10# conf t
buni01-primary-10(config)#no license smart enable
buni01-primary-10(config)#end
buni01-primary-10#
        Step 5   Verify the license information using show license all command.
        Step 6   Set the boot parameters to the new system file name and save the configuration. 
        buni01-primary-10#conf t
buni01-primary-10(config)#no boot system
buni01-primary-10(config)#boot system bootflash:csr1000v-universalk9.03.16.01a.S.155-3.S1a-ext.SPA.bin
buni01-primary-10(config)#exit
buni01-primary-10#write memory
Building configuration...
[OK]
        Step 7   Verify the current version. 
        buni01-primary-10#sh version
Cisco IOS XE Software, Version 03.14.00.S - Standard Support Release
Cisco IOS Software, CSR1000V Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(1)S, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Thu 20-Nov-14 17:11 by mcpre
Cisco IOS-XE software, Copyright (c) 2005-2014 by cisco Systems, Inc.
All rights reserved.  Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0.  The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY.  You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0.  For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.
 
 
ROM: IOS-XE ROMMON
 
buni01-primary-10 uptime is 3 days, 3 hours, 39 minutes
Uptime for this control processor is 3 days, 3 hours, 40 minutes
System returned to ROM by reload
System image file is "bootflash:packages.conf"
Last reload reason: <NULL>
        Step 8   Reload the Cisco CSR 1000V. 
        buni01-primary-10# reload
Proceed with reload? [confirm]
        Step 9   Verify the Cisco CSR 1000V version after it reboots. 
        buni01-primary-10#sh version
Cisco IOS XE Software, Version 03.16.01a.S - Extended Support Release
Cisco IOS Software, CSR1000V Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S1a, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Wed 04-Nov-15 12:09 by mcpre

        For more information on the Cisco CSR 1000V upgrade process, see http:/​/​www.cisco.com/​c/​en/​us/​td/​docs/​routers/​csr1000/​software/​configuration/​csr1000Vswcfg/​swupgradecsr.html.

        Step 10   Once Cisco CSR 1000V reboots with the accurate version, set the boot level license to Cisco VACS. 
        buni01-primary-10(config)#license boot level vacs
% use 'write' command to make license boot config take effect on next boot
 
buni01-primary-10(config)#end
buni01-primary-10#write memory
Building configuration...
  [OK]
        Step 11   Verify that the start up and running configurations are in the Cisco VACS mode. 
        buni01-primary-10#sh run    
buni01-primary-10#sh running-config | inc vacs
license boot level vacs
buni01-primary-10#sh start | inc vacs        
license boot level vacs
buni01-primary-10#
        Step 12   Reload Cisco CSR 1000V. 
        buni01-primary-10#reload
Proceed with reload? [confirm]
        Step 13   Once Cisco CSR 1000V reboots, verify the boot license, and configure the Cisco VACS license server information. The Cisco VACS license server is the Cisco UCS Director appliance where the Cisco VACS software is installed. 
        buni01-primary-10#sh running-config | inc vacs
license boot level vacs
buni01-primary-10#sh startup-config | inc vacs
license boot level vacs
 
buni01-primary-10#conf t
bbuni01-primary-10(config)# platform hardware vacs connect ip <YOUR_UCSD_IP> port 5000   
buni01-primary-10(config)#write memory
        Step 14   Verify the system throughput. 
        buni01-primary-10#sh platform hardware throughput level   
The current throughput level is 10000000 kb/s
buni01-primary-10#
        Step 15   Check the license count in the Cisco UCS Director from Virtual > Network > VACS:CSR License Balance.
        Note   

        The license count in Cisco UCS Director is subjective to the availability of the license.

        Was this Document Helpful?

        Feedback

        Let Us Help