Visitors

HOW TO: Upgrade VCE Vision

VCE RCM 5.0.5 adds support for the VCE Vision Intelligent Operations v. 2.6.2.

The upgrade procedure includes the following tasks:

  1. Downloading the files you need to perform the upgrade.
  2. Installing an upgrade bundle on the VCE Vision virtual machine.
    The upgrade bundle does the following:

    • Applies security updates.
    • Updates VCE Vision software, including the VCE Vision™ System Library and the VCE Vision™ Compliance Checker.
  3. Upgrading the VCE Vision™ Plug-in for vCenter.
  4. Upgrading the compliance content on the VCE Vision virtual machine.
  5. Upgrading the VCE Vision™ Adapter for vCenter Operations Manager, if required.

Ok, let’s get started:

  1. Download VCE Vision upgrade files:
    • vcevision_upgrade-2.6.2.0-16469.vce – VCE Vision virtual appliance upgrade
    • vblock_adapter3-2.6.2-1261.pak – Adapter for vCenter Operations Manager. N.B. VCE supports VMware vCenter Operations Manager version 5.8 only!
    • vce-compliance-content-2.6.0.0-2015.03.00.x86_64.rpm – The latest VCE RCM compliance content file

    VCE Support Portal / VCE Download Center/ VCE™ Software and VCE™ Software Documentation for VCE™ Converged Infrastructure Systems:

    • VB500 family – VCE Software
    • VB540 – VCE Software Documentation.  The folder is quite misleading labeled “VCE Vision (TM) Intelligent Operations Documentation for Vblock System 540 in French” but contains documentation in English, up to version 2.6.0 though…
  2. Upgrade VCE Vision virtual appliance:
    • Shutdown VCE Vision VA and take a snapshot;
    • Use WinSCP or similar tools to upload vcevision_upgrade-2.6.2.0-16469.vce to the /root folder on the VCE Vision VA;
    • Run sh vcevision_upgrade-version_build.vce --argument.
      Where:

      • version_build is the version and build number for the VCE Vision software upgrade bundle.
      • argument is one of the following optional arguments:
        • check – Performs a check for minimum requirements such as available disk space.
        • noprompt – Runs the upgrade process without prompting you to confirm if:
          • You have taken a virtual machine snapshot.
          • You want to reboot the virtual machine.
        • version – Displays the currently installed version, the version of the upgrade, and the list of RPM files that the upgrade bundle includes.
        • help – Displays help usage.
    • [root@vim001 ~]# sh vcevision_upgrade-2.6.2.0-16469.vce --version
      
      Self Extracting Installer
      
      20150415-16:09:16: Running VCE Vision(TM) Intelligent Operations upgrade.  Please wait...
      20150415-16:09:17: See /opt/vce/fm/logs/patch-20150415-16:09:16.log for details
      20150415-16:09:17: Currently installed OVA version is 2.6.0.0
      20150415-16:09:17: This bundle version is 2.6.2.0-16469
      20150415-16:09:17:
      20150415-16:09:17: Security updates:
      20150415-16:09:19: ntp-4.2.6p5-2.el6.centos.x86_64.rpm
      20150415-16:09:19: ntpdate-4.2.6p5-2.el6.centos.x86_64.rpm
      20150415-16:09:19:
      20150415-16:09:19: Plugins:
      20150415-16:09:19: vce-plugin-2.6.2.0-3210.x86_64.rpm
      20150415-16:09:19:
      20150415-16:09:19: Vision IO updates:
      20150415-16:09:19: FMagent-2.6.2.0-16515.x86_64.rpm
      20150415-16:09:19: VblockVision-2.6.2.0-16515.x86_64.rpm
      20150415-16:09:19: flyway-2.1.1-1826.x86_64.rpm
      20150415-16:09:19: jboss-7.1.1.Final-8.x86_64.rpm
      20150415-16:09:19: jre-7u67-linux-x64.rpm (already installed)
      20150415-16:09:19: snmpri-17.3.0.9-1826.x86_64.rpm
      20150415-16:09:19: vce-asset-manager-2.6.2.0-4493.x86_64.rpm
      20150415-16:09:20: vce-compliance-api-2.6.2.0-3549.x86_64.rpm
      20150415-16:09:20: vce-puppetmodules-2.6.2.0-1881.x86_64.rpm
      20150415-16:09:20: vce-upgrade-manager-2.6.0-4478.x86_64.rpm
      20150415-16:09:20: vce-vision-release-2.6.2.0-16469.x86_64.rpm
      20150415-16:09:20: vce-vision-repo-2.6.2.0-4498.x86_64.rpm
      20150415-16:09:20: vpm-2.6.2.0-1889.x86_64.rpm
      20150415-16:09:20:
    • You can also confirm the current version of the VA by running the following command:
      [root@vim001 conf]# getFMagentInfo
      OVA version: 2.6.0.0-1258
      Name        : FMagent                      Relocations: (not relocatable)
      Version     : 2.6.0.0                           Vendor: VCE
      Release     : 15661                         Build Date: Wed Dec  3 18:01:03 2014
      Install Date: Sun Feb  1 18:02:06 2015         Build Host: fmdev08.iaas.lab
      Group       : VCE Applications/System       Source RPM: FMagent-2.6.0.0-15661.src.rpm
      Size        : 63747031                         License: Commercial
      Signature   : RSA/SHA1, Wed Dec  3 18:01:09 2014, Key ID e01792e3d99b5d06
      URL         : http://www.vce.com
      Summary     : VCE FMagent
      Description :
      VCE FMagent build for System Library Integration
      'rpm -qi FMagent' will get the same information.
    • [root@vim001 ~]# sh vcevision_upgrade-2.6.2.0-16469.vce --noprompt
      Self Extracting Installer
      20150415-16:11:17: Running VCE Vision(TM) Intelligent Operations upgrade.  Please wait...
    • You need to accept the EULA:
      Do you accept the End User License Agreement: [yes/no]
      yes
      Softcopy of End User License Agreement File created in:
      /opt/vce/fm/eula/VCE_EULA_V2_2.txt
      20150415-16:12:38: EULA has been accepted
    • After you accept the EULA, the upgrade process continues and the script displays a summary of the upgrade:
      20150415-16:12:38: EULA has been accepted
      20150415-16:12:39: Available disk space: 158845124608
      20150415-16:12:39: Patch size: 537163299
      20150415-16:12:39: Currently installed OVA version is 2.6.0.0
      20150415-16:12:39: This bundle version is 2.6.2.0-16469
    • The script then prompts you to authenticate to the CAS service (the admin password):
      20150415-16:13:16: The CAS password is required to upgrade the VCE Software
      Please enter the CAS password (attempt 1 of 3):
      20150415-16:13:39: Validating CAS password...
      20150415-16:13:40: Running pre-upgrade steps

      If you do not enter the correct CAS password after three attempts, the upgrade process stops. You must then restart the upgrade.

    • For Log Collection to work, you must perform the following steps depending on your Vblock System model, please refer to VCE Vision Upgrade Guide.
      You may configure 0 to 2 additional ApplicationHosts. Enter the number of additional application hosts you are configuring  (Enter number or 's' to skip): s
      Do you want to include ISILON in this configuration?  ('0' to include 's' to skip) [s] :s
    • VCE Vision will validate Vblock configuration and restart the appliance.
    • When VCE Vision virtual appliance comes back online, ensure that the Version field displays the version of VCE Vision software you just installed:
      [root@vim001 ~]# getFMagentInfo
      OVA version: 2.6.0.0-1258
      Name        : FMagent                      Relocations: (not relocatable)
      Version     : 2.6.2.0                           Vendor: VCE
      Release     : 16515                         Build Date: Fri Feb 27 17:30:48 2015
      Install Date: Wed Apr 15 16:15:45 2015         Build Host: fmbuild01.iaas.lab
      Group       : VCE Applications/System       Source RPM: FMagent-2.6.2.0-16515.src.rpm
      Size        : 74944464                         License: Commercial
      Signature   : RSA/SHA1, Fri Feb 27 17:30:55 2015, Key ID e01792e3d99b5d06
      URL         : http://www.vce.com
      Summary     : VCE FMagent
      Description :
      VCE FMagent build for System Library Integration
      'rpm -qi FMagent' will get the same information.
  3. Upgrading the VCE Vision™ Plug-in for vCenter.

    Removing older versions of the Plug-in for vCenter
    If version 2.5.x or version 2.1.x of the VCE Vision™ Plug-in for vCenter is installed on VMware vCenter Server, you must remove it before you deploy the Plug-in for vCenter with the VCE Vision Plug-in Manager (VPM).
    Note: Do not remove version 2.6 of the Plug-in for vCenter.
    For information about how to remove earlier versions of the Plug-in for vCenter, refer to the VCE Vision™ Intelligent Operations Version 2.6 Upgrade Guide.

    • [root@vio001 /]# cd /opt/vce/plugins
      [root@vio001 plugins]# ls -lh
      total 53M
      -rw-r--r-- 1 root root 26M Dec  3 18:46 vce-plugin-2.6.0.0-3029.x86_64.rpm
      -rw-r--r-- 1 root root 27M Apr 15 16:14 vce-plugin-2.6.2.0-3210.x86_64.rpm
    • Run rpm -Uvh vce-plugin-2.6.2.0-build_number.x86_64.rpm to install the Plug-in for vCenter.
      [root@vio001 plugins]# rpm -Uvh vce-plugin-2.6.2.0-3210.x86_64.rpm
      Preparing...                ########################################### [100%]
      Upgrading VCE Vision (TM) plugin
      Successfully unregistered 'vce-plugin-2.6.0.0.zip'
      Successfully undeployed 'vce-plugin-2.6.0.0.zip'
      Successfully deleted 'vce-plugin-2.6.0.0.zip'
      1:vce-plugin             ########################################### [100%]
      Successfully imported 'vce-plugin-2.6.2.0.zip'
      Successfully deployed 'vce-plugin-2.6.2.0.zip'
      Successfully registered 'vce-plugin-2.6.2.0.zip'
    • Restart VMware vSphere Web Client service
    • Here is an interesting bit: Although we have just upgraded VCE Plug-in for vCenter to v 2.6.2, the plug-in folder name is actually “com.vce.vblock-2.6.1.0” and if you check plug-in’s version in the vCenter Extension Manager, it is also2.6.1.0. The plug-in server URL points to “https://VCE_Vision_FQDN:8443/vpm/vce-plugin-2.6.2.0.zip” and the plug-in folder contains 2.6.2.0.jar files…
      UPDATE: This issues has been resolved in VCE Vision v. 2.6.3, see Vblock VCE Vision 2.6.3 Release Notes for details
    • In vSphere Web Client go to the Home window and make sure the Vblock System icon is visible in the Inventories section. If you cannot see the Vblock, check plug-in settings, see next point.
    • Configure the Plug-in for vCenter:
      • Log in to the vSphere Web Client with administrative privileges;
      • On the Home window select Administration in the left navigation pane;
      • Locate the VCE Vision(TM) Plug-in for vCenter section and then select Settings.
      • Confirm the setting are correct and click Update Settings and then click OK when prompted.
  4. Upgrading the compliance content on the VCE Vision virtual machine.
    Although this is an easy procedure, I will publish a separate post on that, please stay tuned!
    UPDATE: please see VCE Vision: How to check Vblock System RCM and Security compliance for details
  5. Upgrading the VCE Vision™ Adapter for vCenter Operations Manager, if required.
    Note: VCE supports VMware vCenter Operations Manager version 5.8 only. Before you upgrade the Adapter for vCenter Operations Manager to version 2.6.2, you must upgrade VMware vCenter Operations Manager to version 5.8

Stay tuned for other VCE Vision related articles…

3 comments to HOW TO: Upgrade VCE Vision

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>