Dell EMC Vision Intelligent Operations. Version Upgrade Guide

Transcription

1 Dell EMC Vision Intelligent Operations Version Upgrade Guide Document revision 1.0 May 2017

2 Revision history Date Document revision Description of changes May New release of the product. Revision history 2

3 Contents Introduction...5 System requirements... 6 Preparing to upgrade Vision software...8 Upgrade overview... 8 Supported upgrade paths...9 Downloading Vision software upgrade files...9 Collecting the custom display names Upgrading a Vision software deployment Upgrading a single MSM VM...11 Taking a snapshot of VMs Configuring the NTP server Upgrading a Vision Core VM Upgrading the MSP VM Upgrading the MSM VM...13 Removing a VM snapshot...14 Upgrading a single site cluster containing multiple MSM VMs...14 Taking a snapshot of VMs in the cluster...16 Identifying the MSM VM acting as the Cassandra seed node Configuring the NTP server Upgrading a Vision Core VM Upgrading the MSP VM Upgrading an MSM VM...18 Removing a VM snapshot...19 Upgrading a multi-site cluster...19 Taking a snapshot of VMs in the cluster...21 Configuring the NTP server Identifying the data center...22 Upgrading the data center VMs Removing a VM snapshot...25 Upgrading a Vision Core VM...26 Taking a snapshot of the Vision Core VM Starting a Vision Core VM upgrade...27 Verifying a Vision Core VM upgrade Upgrading compliance content for the Vision Core VM...34 Removing a VM snapshot Upgrading the Vision Plug-in for VMware vcenter...37 Removing older versions of the Plug-in for vcenter...37 Removing the Plug-in for vcenter version 2.1.x Removing the Plug-in for vcenter version 2.5.x Configuring the Vision Plug-in Manager...39 Installing the Plug-in for vcenter Contents

4 Configuring the Plug-in for vcenter Installing the Plug-in for vcenter in a multi-domain Cisco UCS environment...43 Verifying the Plug-in for vcenter installation Upgrading an MSM VM...46 Configuring the NTP server...46 Taking a snapshot of the MSM VM Starting an MSM VM upgrade Updating the MSM credential manager service Verifying the MSM VM upgrade Uploading compliance content Re-entering the custom display names Upgrading the Vision Shell Security Hardening remediation extension pack...53 Upgrading the remote host for the Vision shell Removing a VM snapshot Upgrading the MSP VM Taking a snapshot of the MSP VM...55 Starting the MSP VM upgrade...56 Verifying the MSP VM upgrade Removing a VM snapshot Troubleshooting the Vision software upgrade Recovering the MSM cluster Reviewing log files...60 Services do not start after Vision Core VM upgrade Removing this version of the Plug-in for vcenter Manually unregistering the Plug-in for vcenter...62 Contents 4

5 Introduction This document provides instructions for upgrading Dell EMC Vision Intelligent Operations. The target audience for this document includes customers, internal teams working with customers, and professional services. The Glossary provides terms, definitions, and acronyms that are related to VCE Systems. 5 Introduction

6 System requirements The system requirements specify the minimum support required for the Vision Core VM, the multisystem management (MSM) VM, and the multisystem prepositioning (MSP) VM. VM Memory requirement (GB) vcpus Disk size (GB) Vision Core VM MSM VM MSP VM The Vision Core VM, MSM VM, and MSP VMs can be installed on the following Advanced Management Platforms (AMP) and storage types: Logical AMP - Vblock System storage array HA-AMP version 1 - VNXe3100 HA-AMP version 2 - VNXe3150 AMP-2V - Vblock System storage array AMP-2P - C-Series local storage AMP-2RP - C-Series local storage AMP-2HA - VNXe3200 AMP-2LP - C-Series local storage AMP-2S - VNXe storage Use the attended configuration tool to configure AMP-2S on the Vblock System 240. Use the unattended configuration tool to configure AMP-2S on the following systems: VxBlock System 240 Vblock System 350 and VxBlock System 350 Vblock System 540 and VxBlock System 540 Vblock System 740 and VxBlock System 740 AMP-3V - Vblock System storage array AMP-3P - C-Series local storage VxRack Controller - Management servers local storage System requirements 6

7 You must consider the following when deploying the Vision Core VM, MSM VM, and MSP VMs: When deploying on AMP, the RAM size must be greater than or equal to 128 GB. If the RAM is less than 128 GB, the AMP must be upgraded to a minimum of 128 GB of RAM. Contact VCE Support for assistance when upgrading the AMP: It is recommended to use NFS mount from the storage array for the MSP VM, where available. For AMP, VNXe3100 and VNXe3150 leverage the local storage capacity. Storage can be added and is documented by Cisco but this might add downtime. Depending on the VCE System, the Vision Core, MSM, and MSP VMs can be installed on either a logical or physical AMP as described in the following table: VCE System Logical AMP Physical AMP Vblock System 100 Yes No Vblock System 200 Yes Yes Vblock System 240 Yes Yes VxBlock System 240 Yes Yes Vblock System 300 series No Yes VxBlock System 340 No Yes VxBlock System 350 No Yes Vblock System 540 No Yes VxBlock System 540 No Yes Vblock System 700 series No Yes VxBlock System 740 No Yes VxRack System with FLEX No Yes Related information Upgrading a Vision Core VM (see page 26) Upgrading an MSM VM (see page 46) 7 System requirements

8 Preparing to upgrade Vision software Complete the Vision Core VM upgrade before upgrading the MSM VM. Upgrade overview Upgrading Vision Intelligent Operations enables you to install the most recent version of Vision software on your existing deployment. The upgrade process includes the following tasks: 1 Download the files you need to perform the upgrade. 2 Install an upgrade bundle on each Vision Core VM. The upgrade bundle does the following: Applies security updates. Updates Vision software, including the Vision System Library and the Vision Compliance Checker. 3 Upgrade the compliance content on the Vision Core and multisystem management (MSM) VMs. 4 Upgrade the Vision Plug-in for vcenter. 5 Install an upgrade bundle on each multisystem management (MSM) VMs. The upgrade bundle does the following: Applies security updates. Updates Vision software. 6 Perform one of the following: Install an upgrade bundle on the multisystem prepositioning (MSP) VM. The upgrade bundle applies security and Vision software updates. Related information Upgrading the MSP VM (see page 13) Preparing to upgrade Vision software 8

9 Supported upgrade paths Review the supported paths for upgrading Vision software. Version Supported upgrade paths > > > Downloading Vision software upgrade files To upgrade Vision software, you must download the files required to upgrade the Vision Core VM, multisystem management (MSM) VM, and the multisystem prepositioning (MSP) VM to the latest version of the software. 1 Download the following files from the Download Center for the Vision Core VM and copy to the / root directory on the Vision Core VM: vcevision_core_upgrade-<buildnumber>.vce RPM Package Manager (RPM) files with the latest version of the compliance content. RPM Package Manager (RPM) files with the latest version of the compliance content hardening (optional). If you downloaded and installed VCE Security Advisory (VSA) or VCE Technical Advisory (VTA) content from the VCE Download Center, you must use RPM Package Manager (RPM) files with the latest version of the compliance content. 2 Download the following files from the VCE Download Center for the MSM VM and copy to the / root directory on the MSM VM: vcevision_msm_upgrade-<buildnumber>.vce ZIP files with the latest version of the compliance content. ZIP files with the latest version of the compliance content hardening (optional). If you downloaded and installed Security Advisory (VSA) or Technical Advisory (VTA) content from the VCE Download Center, use the ZIP files with the latest version of the compliance content. 3 Download the following file from the VCE Download Center for the MSP VM upgrade: vcevision_msp_upgrade-<buildnumber>.vce Related information VCE Download Center 9 Preparing to upgrade Vision software

10 Collecting the custom display names In a single multisystem management (MSM) deployment, custom display names are not retained after an upgrade. Therefore, you need to collect the custom display names before you upgrade so you can reenter them after the upgrade completes. Custom display names are retained in a clustered environment. Collect any custom display names defined for your existing installation. Preparing to upgrade Vision software 10

11 Upgrading a Vision software deployment The steps required to upgrade Vision software in a data center environment vary depending on whether you are using a single-site or multi-site environment. After the VM cluster upgrade process begins: Do not add any Vision Core nodes to MSM VMs in a cluster. Do not join any additional MSM VMs to an MSM cluster. Upgrading a single MSM VM Follow the process outlined here to upgrade in a data center environment with multiple Vision Core VMs mapped to a single MSM VM. Here is an example of what a single-site cluster might look like. The following are high-level steps required to upgrade a single-site cluster with a single MSM VM: 1 Take a snapshot of the VMs. 2 Configure the NTP server. 3 Upgrade each Vision Core VM. 4 Upgrade the MSP VM. 5 Upgrade the MSM VM. 6 Remove the snapshots of the VMs. 11 Upgrading a Vision software deployment

12 Taking a snapshot of VMs Before upgrading, create a snapshot of each VM in the cluster. If you encounter problems during the upgrade process, you can use the snapshot to revert the VM. 1 Power down and take a snapshot of each Vision Core VM being upgraded. Do not power on the Vision Core VMs until snapshots have been taken of the other VMs. 2 Power down and take a snapshot of the MSP VM being upgraded. Do not power on the MSP VMs until snapshots have been taken of the other VMs. 3 Power down and take of snapshot of each MSM VM being upgraded. Do not power on the MSM VMs until snapshots have been taken of the other VMs. 4 Power on and log on to each Vision Core VM associated with the MSM VM. 5 Power on and log on to the MSM VM. 6 Power on and log on to the MSP VM, if one is associated with the MSM VM. Related information Taking a snapshot of the Vision Core VM (see page 26) Taking a snapshot of the MSP VM (see page 55) Taking a snapshot of the MSM VM (see page 47) Configuring the NTP server Ensure that each VM is configured to use an NTP server. 1 Check whether an NTP server is configured on each Vision Core VM, MSP VM, and MSM VM. 2 Configure the NTP server if necessary. Related information Configuring the NTP server (see page 46) Upgrading a Vision software deployment 12

13 Upgrading a Vision Core VM Use this procedure to upgrade the Vision Core VMs associated with the MSM VM in parallel. 1 Start the Vision Core VM upgrade. 2 Verify the Vision Core VM upgrade. 3 Upgrade compliance content for the Vision Core VM. Related information Starting a Vision Core VM upgrade (see page 27) Verifying a Vision Core VM upgrade (see page 33) Upgrading compliance content for the Vision Core VM (see page 34) Upgrading the Vision Plug-in for VMware vcenter (see page 37) Upgrading the MSP VM Use this procedure to upgrade the MSP VM. 1 Start the MSP VM upgrade. 2 Verify the MSP VM upgrade. Related information Upgrade overview (see page 8) Starting the MSP VM upgrade (see page 56) Verifying the MSP VM upgrade (see page 58) Upgrading the MSM VM Use this procedure to upgrade the MSM VM. Before you begin Before starting the upgrade process for the MSM VM, collect the custom display names. 1 Start the MSM VM upgrade. 13 Upgrading a Vision software deployment

14 2 Update the MSM credential manager service. 3 Verify the MSM VM upgrade. 4 Upload compliance content. 5 Re-enter the custom display names. 6 Upgrade the Vision Shell Security Hardening remediation extension pack. 7 Upgrade the remote host for the Vision shell. Related information Starting an MSM VM upgrade (see page 49) Updating the MSM credential manager service (see page 50) Verifying the MSM VM upgrade (see page 51) Uploading compliance content (see page 52) Re-entering the custom display names (see page 53) Upgrading the Vision Shell Security Hardening remediation extension pack (see page 53) Upgrading the remote host for the Vision shell (see page 53) Removing a VM snapshot As a best practice, remove VM snapshots after you successfully upgrade the VMs. If a VM is part of a cluster, do not remove the VM snapshot until all VMs are successfully upgraded. Refer to the VMware documentation for more information. VMware knowledge base article ID provides information on best practices for snapshots in a VMware environment. Upgrading a single-site cluster containing multiple MSM VMs Follow the process outlined here to upgrade Vision software in a data center environment with multiple MSM VMs, each associated with up to two Vision Core VMs. Upgrading a Vision software deployment 14

15 Here is an example of what a single-site cluster containing multiple MSM VMs might look like. The following are high-level steps required to upgrade a single-site cluster with multiple MSM VMs: 1 Take a snapshot of the VMs in the cluster in a powered-down state. Power up each in reverse sequence, in five minute intervals. 2 Identify the MSM VM acting as the Cassandra seed node. 3 Configure the NTP server. 4 Upgrade each Vision Core VM. 5 Upgrade the MSP VM. 6 Upgrade the MSM VMs. 7 Remove the snapshots of the VMs in the cluster. 15 Upgrading a Vision software deployment

16 Taking a snapshot of VMs in the cluster Before upgrading, create a snapshot of each VM in the cluster. If you encounter problems during the upgrade process, you can use the snapshot to revert the virtual machine. 1 Power down and take a snapshot of each Vision Core VM being upgraded. Do not power on the Vision Core VMs until snapshots have been taken of the other VMs. 2 Power down and take a snapshot of the MSP VM being upgraded. Do not power on the MSP VMs until snapshots have been taken of the other VMs. 3 Power down all MSM VMs in the correct sequence. Note the following: The MSM VM that is acting as the Cassandra seed node should be the last MSM VM to be shut down. Record the order in which the MSM VMs are shut down. This is used when powering on the MSM VMs. Shut down the MSM VMs in the cluster one by one, in five minute intervals. Do not power on the MSM VMs until snapshots have been taken of the other VMs. 4 In the powered-off state, take of snapshot of each MSM VM being upgraded. 5 Power on and log on to each Vision Core VM associated with the MSM VMs in the cluster. 6 Power on all MSM VMs in the reverse sequence of how they were shut down, starting with the seed node. Allow five minute intervals between powering up each MSM VM. 7 Power on and log on to the MSP VM, if one is associated with the cluster. Identifying the MSM VM acting as the Cassandra seed node Use this procedure to find the seed node and determine the MSM VM with which to start the upgrade. About this task Start the upgrade process with the MSM VM that is acting as the Cassandra seed node. 1 Start an SSH session to any MSM VM in the cluster. 2 Type the following command: grep seeds: /opt/cassandra/conf/cassandra.yaml The IP address in the output is the IP address of the MSM VM acting as the Cassandra seed node. For example: seeds: ip address Upgrading a Vision software deployment 16

17 Configuring the NTP server Ensure that each VM is configured to use an NTP server. 1 Check whether an NTP server is configured on each Vision Core VM, MSP VM, and MSM VM. 2 Configure the NTP server if necessary. Related information Configuring the NTP server (see page 46) Upgrading a Vision Core VM Use this procedure to upgrade a Vision Core VM. Before you begin You can upgrade the Vision Core VM associated with MSM VMs in the cluster in parallel. 1 Start the Vision Core VM upgrade. 2 Verify the Vision Core VM upgrade. 3 Upgrade compliance content for the Vision Core VM. Related information Starting a Vision Core VM upgrade (see page 27) Verifying a Vision Core VM upgrade (see page 33) Upgrading compliance content for the Vision Core VM (see page 34) Upgrading the Vision Plug-in for VMware vcenter (see page 37) Upgrading the MSP VM Use this procedure to upgrade the MSP VM. 1 Start the MSP VM upgrade. 2 Verify the MSP VM upgrade. 17 Upgrading a Vision software deployment

18 Related information Upgrade overview (see page 8) Starting the MSP VM upgrade (see page 56) Verifying the MSP VM upgrade (see page 58) Upgrading an MSM VM Use this procedure to upgrade each MSM VM. About this task Perform the upgrade for each MSM VM, beginning with the one acting as the Cassandra seed node. Perform the upgrade of the MSM VM cluster members sequentially. Before you begin Make sure that the following are complete before starting the upgrade process for the associated MSM VM cluster members: Upgrade of Vision Core VMs Upgrade of the MSP VM After the VM cluster upgrade process begins: Do not add any Vision Core VMs to any MSM VMs in the cluster. Do not join any additional MSM VM to the MSM cluster. After any MSM VM in a cluster is upgraded, exceptions might appear in the /opt/vce/ multivbmgmt/logs/collectionmanager.log until all MSM VMs are upgraded. Collections can temporarily fail on all non-upgraded MSM VM until they are updated. Important: Start the upgrade process with the MSM VM that is acting as the Cassandra seed node. 1 Start the MSM VM upgrade. 2 Update the MSM credential manager service. 3 Verify the MSM VM upgrade. 4 Upgrade the Vision Shell Security Hardening remediation extension pack. 5 Upgrade the remote host for the Vision shell. What to do next Upload compliance content. Upgrading a Vision software deployment 18

19 Related information Collecting the custom display names (see page 10) Identifying the MSM VM acting as the Cassandra seed node (see page 16) Starting an MSM VM upgrade (see page 49) Updating the MSM credential manager service (see page 50) Verifying the MSM VM upgrade (see page 51) Uploading compliance content (see page 52) Upgrading the Vision Shell Security Hardening remediation extension pack (see page 53) Upgrading the remote host for the Vision shell (see page 53) Removing a VM snapshot As a best practice, remove VM snapshots after you successfully upgrade the VMs. If a VM is part of a cluster, do not remove the VM snapshot until all VMs are successfully upgraded. Refer to the VMware documentation for more information. VMware knowledge base article ID provides information on best practices for snapshots in a VMware environment. Upgrading a multi-site cluster Follow the process outlined here to upgrade an environment of up to three data centers, each having up to two MSM VMs. These MSM VMs can each be associated with up to two Vision Core VMs. 19 Upgrading a Vision software deployment

20 Here is an example of what a multi-site cluster data center environment might look like. The following are high-level steps required to upgrade a multi-site cluster environment: 1 Take a snapshot of the VMs in the cluster. 2 Configure the NTP server. 3 Identify the data center. 4 Upgrade the VMs in each data center. a b c Upgrade each Vision Core VM. Upgrade the MSP VM, if present. Upgrade each MSM VM. 5 Remove the snapshots of the VMs in the cluster. Upgrading a Vision software deployment 20

21 Taking a snapshot of VMs in the cluster Before upgrading, create a snapshot of each VM in the cluster. If you encounter problems during the upgrade process, you can use the snapshot to revert the virtual machine. 1 Power down and take a snapshot of each Vision Core VM being upgraded. Do not power on the Vision Core VMs until snapshots have been taken of the other VMs. 2 Power down and take a snapshot of the MSP VM being upgraded. Do not power on the MSP VMs until snapshots have been taken of the other VMs. 3 Power down all MSM VMs in the correct sequence. Note the following: The MSM VM that is acting as the Cassandra seed node should be the last MSM VM to be shut down. Record the order in which the MSM VMs are shut down. This is used when powering on the MSM VMs. Shut down the MSM VMs in the cluster one by one, in five minute intervals. Do not power on the MSM VMs until snapshots have been taken of the other VMs. 4 In the powered-off state, take of snapshot of each MSM VM being upgraded. 5 Power on and log on to each Vision Core VM associated with the MSM VMs in the cluster. 6 Power on all MSM VMs in the reverse sequence of how they were shut down, starting with the seed node. Allow five minute intervals between powering up each MSM VM. 7 Power on and log on to the MSP VM, if one is associated with the cluster. Configuring the NTP server Ensure that each VM is configured to use an NTP server. 1 Check whether an NTP server is configured on each Vision Core VM, MSP VM, and MSM VM. 2 Configure the NTP server if necessary. Related information Configuring the NTP server (see page 46) 21 Upgrading a Vision software deployment

22 Identifying the data center Perform this task to find the seed node and determine the MSM VM with which to start the upgrade. About this task When the MSM cluster spans multiple data centers, perform the upgrade on each data center separately. Start the upgrade process with the MSM VM that is acting as the Cassandra seed node. In the following illustration, the MSM VMs in data center 1 should be upgraded first, because data center 1 contains the MSM VM that is acting as the Cassandra seed node. After the MSM VMs in data center 1 are successfully upgraded, upgrade data center 2 MSM VMs. 1 Start an SSH session to any MSM VM in the cluster. 2 Type the following command: grep seeds: /opt/cassandra/conf/cassandra.yaml The IP address in the output is the MSM VM address that is acting as the Cassandra seed node. Upgrading a Vision software deployment 22

23 Upgrading the data center VMs Upgrade the VMs in each data center starting with the data center containing the MSM VM that is acting as the Cassandra seed node. After the MSM VM cluster upgrade process starts in a data center: Do not add any Vision Core VMs to any MSM VM in the cluster. Do not join any additional MSM VMs to the MSM cluster. Upgrading Vision Core VMs The Vision Core VMs can be upgraded across data centers before beginning MSM VM upgrades. This helps minimize the time between upgrading MSM VMs in different data centers. Before you begin You can upgrade the Vision Core VMs associated with MSM VMs in the cluster in parallel. 1 Start the Vision Core VM upgrade. 2 Verify the Vision Core VM upgrade. 3 Upgrade compliance content for the Vision Core VM. Related information Starting a Vision Core VM upgrade (see page 27) Verifying a Vision Core VM upgrade (see page 33) Upgrading compliance content for the Vision Core VM (see page 34) Upgrading the Vision Plug-in for VMware vcenter (see page 37) Upgrading the MSP VM Use this procedure to upgrade the MSP VM. 1 Start the MSP VM upgrade. 2 Verify the MSP VM upgrade. Related information Upgrade overview (see page 8) 23 Upgrading a Vision software deployment

24 Starting the MSP VM upgrade (see page 56) Verifying the MSP VM upgrade (see page 58) Upgrading an MSM VM Use this procedure to upgrade an MSM VM. About this task Perform the upgrade of the MSM VM cluster members sequentially. Before you begin Make sure that the following are complete before starting the upgrade process for the associated MSM VM cluster members: Upgrade of Vision Core VMs Upgrade of the MSP VM, if one is associated with the cluster After the MSM VM cluster upgrade process begins: Do not add any Vision Core VMs to any MSM VMs in the cluster. Do not join any additional MSM VMs to the MSM cluster. After any MSM VM in a cluster is upgraded, exceptions might appear in the /opt/vce/ multivbmgmt/logs/collectionmanager.log until all MSM VMs in the cluster are upgraded. Collections can temporarily fail on all non-upgraded MSM VM until they are updated. This means that, until both data centers are upgraded, an MSM VM upgrade in one data center impacts collections by MSM VMs running in the other data center. Important: Start the upgrade process with the MSM VM that is acting as the Cassandra seed node. 1 Start the MSM VM upgrade. 2 Update the MSM credential manager service. 3 Verify the MSM VM upgrade. 4 Upgrade the Vision Shell Security Hardening remediation extension pack. 5 Upgrade the remote host for the Vision shell. What to do next Upload compliance content. Re-run all compliance scans. Upgrading a Vision software deployment 24

25 Related information Collecting the custom display names (see page 10) Identifying the data center (see page 22) Starting an MSM VM upgrade (see page 49) Updating the MSM credential manager service (see page 50) Verifying the MSM VM upgrade (see page 51) Uploading compliance content (see page 52) Re-entering the custom display names (see page 53) Upgrading the Vision Shell Security Hardening remediation extension pack (see page 53) Upgrading the remote host for the Vision shell (see page 53) Removing a VM snapshot As a best practice, remove VM snapshots after you successfully upgrade the VMs. If a VM is part of a cluster, do not remove the VM snapshot until all VMs are successfully upgraded. Refer to the VMware documentation for more information. VMware knowledge base article ID provides information on best practices for snapshots in a VMware environment. 25 Upgrading a Vision software deployment

26 Upgrading a Vision Core VM The Vision Core VM upgrade must complete before you start upgrading the MSM VM. Related information System requirements (see page 6) Supported upgrade paths (see page 9) Taking a snapshot of the Vision Core VM Before upgrading, you should create a snapshot of the Vision Core VM. If you encounter problems during the upgrade process, you can revert the VM using the snapshot. Before you begin Connect to the Vision Core VM. 1 Type shutdown -h now to power down the VM. The following message displays: The system is going down for halt NOW! 2 Log on to the VMware vsphere Client using an account with administrative privileges. 3 In the Navigation bar, select Home > Inventory > Hosts and Clusters in the following screenshot: The VMware vsphere Client displays the hosts and clusters available in the environment. 4 Navigate to the VM for which you want to take a snapshot. Upgrading a Vision Core VM 26

27 5 Right-click the VM and select Snapshot > Take Snapshot in the following screenshot: The VMware vsphere Client prompts you to enter a name and description for the snapshot. 6 Specify a name and description for the snapshot. Choose a name and description that are easy to recognize and meaningful to others. 7 Clear the check boxes to snapshot the VM memory and quiesce the guest file system, if available. 8 Click OK to take the snapshot of the VM. What to do next If the VM is not part of a cluster, power on the VM and log on. If the VM is part of a cluster, power on the VM and log on only after the VM snapshots have been taken of the other cluster members. Starting a Vision Core VM upgrade Execute vcevision_core_upgrade-<buildnumber>.vce to upgrade. Before you begin Verify the Vision Core VM can be directly upgraded. Check the list of supported upgrade paths to determine which path best suits your system. Take a snapshot of the Vision Core VM. Validate the components and login credentials for all components in the vblock.xml file by typing the following command: configtool.sh -v filename 27 Upgrading a Vision Core VM

28 Ensure you have credentials for the following: Central Authentication Service (CAS) administrator password VNXe service account password for Vblock System 100, Vblock System 2xx, Vblock System 3xx, Vblock System 5xx, and Vblock System 7xx VNX SPB credentials for Vblock System 2xx and 3xx VMAX Gateway credentials for Vblock System 7xx Connect to the Vision Core VM using SSH. 1 Copy vcevision_core_upgrade-<buildnumber>.vce to the /root directory on the Vision Core VM. 2 (Optional) To verify that the Vision Core VM meets the minimum requirements for the update, to check the version, or to get help for the command, type the following command: sh vcevision_core_upgrade-<buildnumber>.vce --argument Where argument is one of the following optional arguments: Argument check noprompt silent version help Description Performs a check for minimum requirements such as available disk space. Runs the upgrade process without prompting you to confirm: You have a virtual machine snapshot. You want to reboot the virtual machine after upgrade. Installs the bundle in silent mode that requires minimal to no user input. Displays the currently installed version, the version of the upgrade, and the list of RPM files that the upgrade bundle includes. Displays help usage. If you select the silent argument, you will not be prompted to manually enter the IPI appliance, Application Hosts, and to restart the Vision Core VM. These will happen automatically. 3 To start the upgrade, type: sh vcevision_core_upgrade-<buildnumber>.vce The upgrade scripts start running and then prompts you with the following: It is recommended that you take a snapshot before proceeding. Continue? Enter 'y' for yes or 'n' for no (default): Upgrading a Vision Core VM 28

29 4 Type one of the following values: Option y n Description Proceed with the upgrade if you have taken a snapshot of the Vision Core VM. Stop the upgrade and take a virtual machine snapshot. If you type y, the upgrade scripts prompt you to accept the End User License Agreement (EULA). 5 Type y to accept the EULA and continue. 6 Complete the EULA acceptance. The fields in the EULA cannot exceed 500 characters or contain angle brackets. a b c d e f Scroll through the EULA until you see the Enter Name: prompt. Type your name and press Enter. Type your job title and press Enter. Type the name of the licensee company and press Enter. Optional: Type the name of the accepting company and press Enter. If you do not specify an accepting company, the value defaults to the licensee company. Type Yes when prompted to accept the EULA. After you accept the EULA, the upgrade process continues and the script displays a summary of the upgrade, as in the following example: timestamp: EULA has been accepted timestamp: Waiting for services to start. This may take several minutes. Please wait... The script then prompts you to authenticate to the CAS (Central Authenticated Service) service, as follows: timestamp: The CAS password is required to upgrade the VCE Software Please enter the CAS password (attempt 1 of 3): 7 Type the CAS password. If you enter an incorrect CAS password after three attempts, the upgrade process stops. You must then restart the upgrade. 29 Upgrading a Vision Core VM

30 8 For a Vblock System 340, Vblock System 540, Vblock System 720, or a Vblock System 740, the script prompts you to include an IPI appliance in the configuration, as in the following: Do you want to configure Panduit Rack of UCS Technology Extension ('0' to include, 's' to skip) [s] :0 a Type 0 to include the configuration or type s to skip. The script prompts you to configure the IPI appliance: Panduit Rack configuration (1) ipaddress, 'null' (2) Community, '' Enter selection ('0' to continue to next step, or 'v' to validate ): [0] :1 Enter value for attribute 'ipaddress': Enter selection ('0' to continue to next step, or 'v' to validate ): [0] :2 Enter value for attribute 'Community': public Panduit Rack configuration (1) ipaddress, ' ' (2) Community, 'public' Enter selection ('0' to continue to next step, or 'v' to validate ): [0] : b c d Type 1 to change the IP address. Type 2 to change the community string. The SNMP community string must match the string set on the server. Type v to validate the configuration for the IPI appliance. For a Vblock System 340 or a Vblock System 720, you can configure between 0 and 99 additional IPI appliances. The script prompts you to enter the number of additional IPI appliances you want to configure, as in the following: Enter the number of additional Panduit Racks you are configuring (Enter number or 's' to skip): You will then be prompted to: Enter selection ('0' to continue to next step, or 'v' to validate ): [0] : Upgrading a Vision Core VM 30

31 9 Follow these steps to include Application Hosts in the configuration. Each Application Host is a Windows-based VM on an Advanced Management Platform (AMP) with one or more of the following management software applications: Navisphere CLI PowerPath/ Electronic License Management Server Unisphere Client Unisphere Server Unisphere Service Manager SMI-S Provider The script prompts you to enter the number of Application Hosts. You may configure 0 to 2 additional ApplicationHosts. Enter the number of additional application hosts you are configuring (Enter Number or 's' to skip): a Enter the number of Application Hosts for each Windows-based VM on an AMP that has one or more management software applications installed. The script prompts you to configure the IP address for the Application Host, as follows: ApplicationHost ManagedSoftware 2 address: ' ', name: 'app-host-1', type: 'windows' (1) address, ' ' To change an attribute enter the corresponding number from the list ('0' to continue to next step): b To change the IP address of the Application Host, type 1 and then enter the IP address. Otherwise, type 0 and continue to the next step. The script prompts you to change the credentials for the Application Host as follows: Credentials ApplicationHost 3 method: 'wmi', username: 'admin', (1) password, '**************' (2) username, 'domain\admin' or 'admin@domain' Enter selection ('0' to continue to next step, or 'v' to validate ): c Type any of the following values: 1 to change the password for the Application Host. 2 to change the domain name and username for the Application Host. You must include the domain name before the username, using a backslash. 0 to continue to the next step. 31 Upgrading a Vision Core VM v to validate the information for the Application Hosts.

32 d Repeat these steps for each Application Host in your configuration. The upgrade process continues and a series of messages display. When you reach the end of the upgrade process, the script prompts you to restart the Vision Core VM, as follows: A system reboot is required for all updates to complete. If you do not reboot now, the system will be unusable until a reboot occurs. Reboot system now? Enter 'n' for no or 'y' for yes (default): 10 For the VxBlock and Vblock Systems 300 series and the VxBlock and Vblock Systems 700 series, follow these steps to include Isilon in the configuration. The script prompts you to include Isilon in the configuration as in the following example: Please configure the Isilon Cluster (The address can be any node IP address within the cluster) type, 'ISILON' (1) componenttag, 'ISILON-ARRAY-CLUSTER-1' (2) address, " Enter selection ('0' to continue to next step):(0): a b Type 0 to continue to the next step. Type 2 to enter the IP address of the storage cluster. For the Isilon storage cluster IP address, use the IP address of any node within the Isilon storage cluster. For example, use the IP address of the first node within the Isilon storage cluster. The script prompts you to configure the SSH protocol credentials, as in the following example: Please configure the Isilon Cluster ssh credentials. method, 'ssh' (1) username, '' (2) password, '' c d Type 1 to enter the username. Type 2 to enter the password. The script prompts you to configure the REST API protocol credentials, as in the following example: Please configure the Isilon Cluster restapi credentials. method, 'restapi' (1) username, '' (2) password, '' e Type 1 to enter the username. Upgrading a Vision Core VM 32

33 f Type 2 to enter the password. The script prompts you to configure the SNMPV2C credentials, as in the following example: Please configure the Isilon Cluster snmpv2c credentials. method, 'snmpv2c' (1) community, '' g Type 1 to enter community. The upgrade process continues and a series of messages display. When you reach the end of the upgrade process, the script prompts you to restart the Vision Core VM, as follows: A system reboot is required for all updates to complete. If you do not reboot now, the system will be unusable until a reboot occurs. Reboot system now? Enter 'n' for no or 'y' for yes (default): 11 Enter y to restart. The following message displays: The system is going down for reboot NOW! VCE Vision will now reboot to apply all updates What to do next Verify the version of the Vision Core VM is the version you just installed. Note: If you want to add VMware NSX components (NSX Controller and the NSX Manager) or Red Hat Enterprise Linux components to the Vision software discovery process, see the Dell EMC Vision Intelligent Operations Administration Guide. Verifying a Vision Core VM upgrade After completing the upgrade process, verify the version of the Vision Core VM is the version you just installed. Before you begin Connect to the Vision Core VM. 1 Type the following command: getfmagentinfo. 33 Upgrading a Vision Core VM

34 2 The Vision Core VM returns the version and build information, as in the following example. OVA version:x.x.x.x-build_number Name:FMagent Relocations:(not relocatable) Version:X.X.X.X Vendor:VCE Release:release Build Date:time_stamp Install Date:time_stamp Build Host:hostname Group:VCE Applications/System Source RPM:fmAGENT-X.X.X.X-build_number.src.rpm Size:size License:Commercial Signature:RSA/SHA1, time_stamp,key ID key_id URL: Summary:VCE FMagent Description: VCE FMagnet build for System Library Integration ' rpm -qi FMagent' will get the same information. 3 Ensure that the Version field contains the version of Vision software you just installed. The OVA version displayed may differ and refer to the originally installed version of the OVA. Upgrading compliance content for the Vision Core VM Upgrading compliance content ensures that the Compliance Checker has the most recent compliance information for your VCE System. Compliance content includes policies for RCMs, Security Compliance Validation, and Dell EMC VCE Technical Advisory compliance. About this task This step is applicable only if you are upgrading compliance content on Vision Core for Vblock Systems. To upgrade compliance content for other VCE Systems, refer to uploading compliance content as part of the MSM VM upgrade. If you want to run compliance scans against the latest compliance content using the Plug-in for vcenter, you must complete the steps below to ensure the downloaded compliance content is installed correctly on the Vision Core VM. Before you begin Check which version of the compliance content RPM is currently installed by running the following command: rpm -qa grep vce-compliance-content Download the compliance content RPM files. Ensure you have the CAS authentication credentials for the administrator user. The default credentials are: Username: admin Password: 7j@m4Qd+1L Connect to the Vision Core VM. Upgrading a Vision Core VM 34

35 1 Copy the RPM file, or files, to any location on the Vision Core VM. 2 Change to the directory that contains the RPM file. 3 Type the following command: rpm -Uvh content_rpm_name-build_number.rpm Where: Type this command and perform the following steps separately for each RPM file you plan to install. rpm is the command to run RPM Package Manager. -Uvh is the option to upgrade the RPM. content_rpm_name-build_number.rpm is the name of the RPM file. For example, vce-compliance-content-build_number.rpm and vce-compliancecontent-hardening-build_number.rpm. For example, the following command installs the Vision Core compliance content: rpm -Uvh vce-compliance-content-build_number.rpm The command saves compliance content from the RPM file to the following location on the Vision Core VM: /opt/vce/compliance/content. 4 Type the following command: cd /opt/vce/compliance/content 5 Type the following command: sh install_content.sh Results 6 Authenticate to the CAS service when prompted. The installation script uses the API for Compliance Checker to install the compliance content. For this reason, you must authenticate to the CAS service. The script installs the compliance content and a message displays as shown in the following example: CONTENT INSTALL RESULTS Successfully imported content: Hardening Content for VCE Vblock (TM) System 300 family RCM Content for VCE Vblock (TM) System Upgrading a Vision Core VM

36 Related information Uploading compliance content (see page 52) Removing a VM snapshot As a best practice, remove VM snapshots after you successfully upgrade the VMs. If a VM is part of a cluster, do not remove the VM snapshot until all VMs are successfully upgraded. Refer to the VMware documentation for more information. VMware knowledge base article ID provides information on best practices for snapshots in a VMware environment. Upgrading a Vision Core VM 36

37 Upgrading the Vision Plug-in for VMware vcenter Perform this upgrade if you have installed the Vision Plug-in for vcenter. Before upgrading the Vision Plug-in for vcenter, you must consider the following scenarios: If you are a 2.6.x (or above) user, you must complete the following procedures when upgrading the Vision Plug-in for vcenter Installing the Plug-in for vcenter (see page 40) Verifying the Plug-in for vcenter installation (see page 45) Removing older versions of the Plug-in for vcenter If version 2.5.x of the 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 Vision Plug-in Manager (VPM). Do not remove the existing 2.6.x or 3.x version of the Plug-in for vcenter. The Plug-in for vcenter is installed in the following directory: C:\ProgramData \VMware\vSphere Web Client\vc-packages\vsphere-client-serenity. You must enable hidden folders to view the Program Data folder. For information on how to remove and manually unregister this version of the Plug-in for vcenter, refer to the Related information section. Related information Removing this version of the Plug-in for vcenter (see page 61) Removing the Plug-in for vcenter version 2.1.x Remove the Plug-in for vcenter version 2.1.x from the VMware vcenter Server host and manually delete all installed artifacts. Before you begin Log in to the vcenter Server host with a user that has administrative permissions. 1 Stop the VMware vsphere Web Client service on the vcenter Server host. 2 Remove the Plug-in for vcenter and all artifacts as follows: a Delete all content in drive:\programdata\vmware\vspherewebclient \serviceability\logs\. Where drive is the letter assigned to the drive. 37 Upgrading the Vision Plug-in for VMware vcenter

38 b Delete vce.properties in drive:\programdata\vmware\vspherewebclient\. Where drive is the letter assigned to the drive. c d Delete vce-plugin in drive:\program Files\VMware\Infrastructure \vspherewebclient\plugin-packages\. Delete all content in drive:\program Files\VMware\Infrastructure \vspherewebclient\server\work\. Where drive is the letter assigned to the drive. 3 Start the VMware vsphere Web Client service. Related information Removing this version of the Plug-in for vcenter (see page 61) Removing the Plug-in for vcenter version 2.5.x Remove the Plug-in for vcenter version 2.5.x from the VMware vcenter Server host and manually delete all installed artifacts. Before you begin Log in to the vcenter Server host with a user that has administrative permissions. 1 Navigate to C:\ProgramData\VCE\vce-plugin\ 2 Run the following batch script: uninstall.bat. The script removes the Plug-in for vcenter, restarts the VMware vsphere Web Client service, and opens the vsphere Web Client. 3 Stop the VMware vsphere Web Client service on the vcenter Server host. 4 Verify that the vce-plugin directory is not present in drive:\program Files\VMware \Infrastructure\vSphereWebClient\plugin-packages\ Where drive is the letter assigned to the drive. If the vce-plugin directory is still present after running uninstall.bat, manually delete it. 5 Remove all Plug-in for vcenter artifacts as follows: a b Delete all content in drive:\program Files\VMware\Infrastructure \vspherewebclient\server\work\. Delete all content in drive:\programdata\vmware\vspherewebclient \serviceability\logs\. Upgrading the Vision Plug-in for VMware vcenter 38

39 6 Start the VMware vsphere Web Client service. Related information Removing this version of the Plug-in for vcenter (see page 61) Configuring the Vision Plug-in Manager The Vision Plug-in Manager (VPM) is a framework for deploying the Plug-in for vcenter to VMware vcenter Server. If upgrading from Vision software Version 2.5.x or earlier, you must configure the VPM before you install the Plug-in for vcenter if you are upgrading from Vision software Version 2.5.x or earlier. About this task To configure the Vision VPM, you must specify the address of the administrator who manages the VMware vcenter Server plug-ins. You must also specify the hostname of the vcenter Server and administrator credentials if they are not set in the vblock.xml file. If the vpm-settings.properties file has already been created in the /opt/vce/ tools/vpm/conf folder, then the following message appears: A VPM configuration file has already been created. To overwrite the existing file, use the 'vpm setup force option, which will configure VPM with the settings in vblock.xml The vpm-settings.properties file does not need to be updated after upgrade unless the administrator address or the vcenter credentials in the vblock.xml file has changed. If you specify a command line parameter with a backslash character (\), you must escape the backslash character with an additional backslash character. For example, to provide the vcenter server hostname and credentials domain\username, you must type domain\\username. The Administrator group must have permission for the following resources: Extension.Register Extension.Unregister Extension.Update Before you begin Uninstall the existing Plug-in for vcenter from the Vision Core VM. Ensure that the user is part of the Administrator user group in the VMware vsphere Client. Refer to the VMware vsphere documentation. 39 Upgrading the Vision Plug-in for VMware vcenter

40 Ensure that the user has administrative permission to the vcenter Server. For example, the local Administrator is granted the Administrator role below. Ensure that the /opt/vce/fm/conf/vblock.xml file is configured with the vcenter Server hostname and administrator credentials. Connect to the Vision Core VM. 1 Type the following command: cd /opt/vce/plugins 2 Type the following command: vpm setup Type vpm setup -help for usage options. The following message appears: VPM configuration file does not exist yet. Use the setup command to configure VPM. 3 Type the address when prompted. Extension administrator address: username@companyname.com 4 Type the FQDN of the vcenter Server. 5 Type the username and password for the vcenter server. The username and password must be for the administrator user. The following message appears: The VPM configuration has been saved to '/opt/vce/tools/vpm/conf/vpmsettings.properties' Installing the Plug-in for vcenter Use this procedure to install the Plug-in for vcenter on your vcenter Server. Upgrading the Vision Plug-in for VMware vcenter 40

41 Before you begin Ensure one of the following versions of the VMware vsphere Web Client is installed: The compatibility details of each version of the VMware vsphere Web Client (VWC) are outlined in the following table: Compatibility with: vcenter 5.5 vcenter 6.0 VWC 5.5 Yes No VWC 6.0 Yes Yes Ensure the vcenter Server host can resolve the fully qualified domain name (FQDN) of the Vision Core VM. If you use a host file for FQDN resolution, remove the entry after you install the Plug-in for vcenter. Removing the host file entry ensures that it does not conflict with any IP address changes you make. The Administrator group must have permission for the following resources: Extension.Register Extension.Unregister Extension.Update Ensure that the user is part of the Administrator user group in the VMware vsphere Client. Refer to the VMware vsphere documentation. Ensure that the user has administrative permission to the vcenter Server. For example, the local Administrator is granted the Administrator role below. Connect to the Vision Core VM. 41 Upgrading the Vision Plug-in for VMware vcenter

42 1 Type the following command: cd /opt/vce/plugins 2 Type the following command to install the Plug-in for vcenter: rpm -Uvh vce-plugin-version_number-build_number.x86_64.rpm The following messages display: Preparing... ########################################### [100%] 1:vce-plugin ########################################### [100%] Installing VCE Vision (TM) plugin Successfully imported 'vce-plugin-version_number.zip' Successfully deployed 'vce-plugin-version_number.zip' Successfully registered 'vce-plugin-version_number.zip' To enable component counts to be shown at the top level on VMware vsphere 6.0 installations, follow these steps: a b c d Log on to the machine where VMware vsphere 6.0 is installed. Open \ProgramData\VMware\vCenterServer\cfg\vsphere-client \webclient.properties Locate the property named large.inventory.mode. Change the value to false. e Reload any open browser instances of vsphere Restart the VMware vsphere Web Client service. Upgrading the Vision Plug-in for VMware vcenter 42

43 Configuring the Plug-in for vcenter Configure the Plug-in for vcenter so that it can connect to Vision Core VM. Before you begin Ensure the VMware vsphere Web Client service is running on the VMware vcenter Server host. 1 Open a web browser and navigate to the following URL: Where fqdn is the fully qualified domain name (FQDN), or IP address, of the vcenter Server. 2 Log on to the vsphere Web Client with administrative privileges. 3 Select Administration in the left navigation pane on the Home window. 4 Locate the VCE Vision(TM) Plug-in for vcenter section and then select Settings. 5 Set connection properties as follows: Property Hostname Port Description Case sensitive FQDN of the Vision Core VM. Port number for the Central Authentication Service (CAS) on the Vision Core VM. The default is The port number value cannot be modified. Username CAS user for the Vision Core VM. The username cannot be modified. Password Confirm Password Password that corresponds to the CAS user. Confirmation of the password. 6 Select Update Settings and click OK when prompted. 7 Restart the web client services on the VMware vcenter Server virtual machine. Installing the Plug-in for vcenter in a multi-domain Cisco UCS environment In a multi-domain UCS environment, you can install multiple Plug-in for VMware vcenter instances. Before you begin You must have one instance of the Plug-in for VMware vcenter installed and configured. Follow these steps to add additional Plug-in for VMware vcenter instances to manage additional domains. 43 Upgrading the Vision Plug-in for VMware vcenter

44 1 Delete the existing vpm-settings.properties file in the /opt/vce/tools/vpm/conf/ directory that was created while installing the first Plug-in for VMware vcenter instance. 2 Install the second Plug-in for VMware vcenter instance on a different domain: a Type vpm setup - your @domain.com -vcenterhostname <FQDN of the first domain> -vcenterusername <username> -P. Tip: Type vpm setup -help for usage options. For example, #vpm setup - your @domain.com -vcenterhostname vb700swqavc251.vb700swqa.vcemo.lab -vcenterusername vb700swqa\\rtest -P If the username contains a backslash, add another backslash, for example, vb700swqa\rtest would become vb700swqa\\rtest. b Type the password for VMware vcenter The following message displays: The VPM configuration has been saved to '/opt/vce/tools/vpm/conf/vpmsettings.properties' c d Type cd /opt/vce/plugins. Type rpm -Uvh vce-plugin-version_number-build_number.x86_64.rpm to install the Plug-in for vcenter. Enter the password for vcenter. The following message displays: The VPM configuration has been saved to '/opt/vce/tools/vpm/conf/vpmsettings.properties' The following messages display: Preparing... ########################################### [100%] 1:vce-plugin ########################################### [100%] Installing VCE Vision (TM) plugin Successfully imported 'vce-plugin-version_number.zip' Successfully deployed 'vce-plugin-version_number.zip' Successfully registered 'vce-plugin-version_number.zip' 3 Repeat Step 1 and Step 2 for each Plug-in for vcenter installation on a new domain. What to do next Configure each Plug-in for VMware vcenter. Upgrading the Vision Plug-in for VMware vcenter 44

45 Verifying the Plug-in for vcenter installation After you complete the steps to install the Plug-in for vcenter, verify that it installed successfully on the vcenter Server virtual machine. 1 Connect to the Vision Core VM. 2 Type the following command: vpm list 3 Verify that the extension ID displays com.vce.vblock Version:version number in the output. 4 Log on to the VMware vcenter Web Client. 5 Navigate to the settings page and verify that the version of the plug-in is displayed as version number. 6 Select or highlight the top-level VCE System icon. 7 Click Manage > Compliance > Policies. If you installed the compliance content package, you will see one or more policies. If the VCE System platform type is changed from the last time the compliance content was installed, you must reinstall the compliance content. 45 Upgrading the Vision Plug-in for VMware vcenter

46 Upgrading an MSM VM All of the Vision Core VMs must be upgraded before you start the upgrade process for the MSM VM. Related information System requirements (see page 6) Supported upgrade paths (see page 9) Configuring the NTP server Use this procedure to configure each MSM VM and Vision Core VM to use an NTP server. If you are redeploying an MSM VM, specify an NTP server IP address when configuring the server. Before you begin Determine the NTP server to be used for the data center. Use the VLAN gateway or the gateway of the VCE System. For each MSM VM and Vision Core VM, perform the following steps: 1 SSH to the VM as the root user. 2 Type the following command to verify that the NTP server is accessible: ntpdate -u <IP_address> where IP_address is the NTP server IP address. Result: 9 Sep 15:13:59 ntpdate[30770]: adjust time server IP_address offset sec 3 Edit the /etc/ntp.conf file. Upgrading an MSM VM 46

47 4 Comment out the default CentOS server entries and add the following entry: server IP_address, where IP_address is the NTP server IP address. If the lines are already commented out, skip this step and run service ntpd status to check if the NTP daemon is running. If the daemon is running, skip the remaining steps and move to the next VM. #server 0.centos.pool.ntp.org iburst #server 1.centos.pool.ntp.org iburst #server 2.centos.pool.ntp.org iburst #server 3.centos.pool.ntp.org iburst server IP_address 5 Save the changes and run the following command to start the ntpd service: service ntpd restart 6 Type the following command for the ntpd service to start on reboot: chkconfig ntpd on Taking a snapshot of the MSM VM Before upgrading, create a snapshot of the MSM VM. If you encounter problems during the upgrade process, you can revert the virtual machine using the snapshot. Important: After you revert to a snapshot you will need to reboot the VM before attempting another upgrade. Before you begin Connect to the MSM VM. 1 Type shutdown -h now to power down the VM. The following message displays: The system is going down for halt NOW! 2 Log on to the VMware vsphere Client using an account with administrative privileges. 47 Upgrading an MSM VM

48 3 In the Navigation bar, select Home > Inventory > Hosts and Clusters in the following screenshot: The VMware vsphere Client displays the hosts and clusters available in the environment. 4 Navigate to the VM for which you want to take a snapshot. 5 Right-click the VM and select Snapshot > Take Snapshot in the following screenshot: The VMware vsphere Client prompts you to enter a name and description for the snapshot. 6 Specify a name and description for the snapshot. Choose a name and description that are easy to recognize and meaningful to others. 7 Clear the check boxes to snapshot the VM memory and quiesce the guest file system, if available. 8 Click OK to take the snapshot of the VM. What to do next If the VM is not part of a cluster, power on the VM and log in. If the VM is part of a cluster, power on the VM and log in only after the VM snapshots have been taken of the other cluster members. Upgrading an MSM VM 48

49 Starting an MSM VM upgrade Execute vcevision_msm_upgrade-<buildnumber>.vce to upgrade. Before you begin Verify the MSM VM can be directly upgraded. Check the list of supported upgrade paths to determine which path best suits your system. Take a snapshot of the MSM VM. Connect to the MSM VM using SSH. Ensure that all Vision Core VMs connected to the MSM VM being upgraded are powered on. 1 Copy vcevision_msm_upgrade-<buildnumber>.vce to the /root directory on the MSM VM. 2 (Optional) To verify that the MSM VM meets the minimum requirements for the update, check the version. To get help for the command, type the following command: sh vcevision_msm_upgrade-<buildnumber>.vce --argument Where argument is one of the following optional arguments: Argument check noprompt silent version help Description Performs a check for minimum requirements such as available disk space. Runs the upgrade process without prompting you to confirm: You have a virtual machine snapshot. You want to reboot the virtual machine after upgrade. Installs the bundle in silent mode that requires minimal to no user input. Displays the currently installed version, the version of the upgrade, and the list of RPM files that the upgrade bundle includes. Displays help usage. If you select the silent argument, you will not be prompted to manually restart the MSM VM. These will happen automatically. 3 To start the upgrade, type the following command: sh vcevision_msm_upgrade-<buildnumber>.vce The upgrade scripts starts running and then prompts with the following: It is recommended that you take a snapshot before proceeding. Continue? Enter 'y' for yes or 'n' for no (default): 49 Upgrading an MSM VM

50 4 Type one of the following values: Option y n Description Proceed with the upgrade if you have taken a snapshot of the virtual machine. Stop the upgrade and take a virtual machine snapshot. Before proceeding with the upgrade, make sure that all Vision Core VMs that are connected to the MSM VM being upgraded are powered on. 5 The upgrade process continues and the script displays a summary of the upgrade, as in the following example: timestamp: Available disk space: timestamp: Patch size: timestamp: Currently installed OVA version is timestamp: This bundle version is build_number 6 Type y to restart. The following message appears: The system is going down for reboot NOW! VCE Vision will now reboot to apply all updates After upgrading, you need to re-run all compliance scans. In a clustered environment, compliance scan results previous to the upgrade are retained. In a single MSM deployment, the details are not retained. What to do next Verify that the version of the MSM VM corresponds to the version that you installed. Updating the MSM credential manager service If the root or vision user password has been changed on the Vision Core VM, you must update the MSM credential manager service with the new password. Start an SSH session to the MSM VM and complete the following steps: 1 Log on to the MSM VM as the root user. 2 Type the following command to change the Vision Core virtual machine root user password for MSM: /opt/vce/multivbmgmt/install/addslibhost.sh <core_ipaddress> where core_ipaddress is the IP address for the Vision Core virtual machine where the password was changed. The script prompts you to update the configuration: Upgrading an MSM VM 50

51 Would you like to update existing configuration? (yes/no) [Default = no]: 3 Respond by entering yes. The script prompts you for the root credentials: Enter the SSH credentials for System Library host (attempt 1 of 3). User name [Default: root]: 4 Enter the root (or press Enter) for the username. 5 Type the new password for the Vision Core virtual machine. The script continues processing with a series of messages. When it has finished, the following message is displayed: Vision System Library Host(s) at have been added successfully! The new password for the Vision Core virtual machine will be picked up by the MSM VM during the next collection cycle. Verifying the MSM VM upgrade After completing the upgrade process, use the Vision dashboard to verify that the version number corresponds to the version that you installed. Before you begin You need the following information to access the dashboard: Fully-qualified domain name (FQDN) of the multisystem management (MSM) VM. A username and password with access to the Vision dashboard. One of the following supported browsers: Google Chrome Microsoft Internet Explorer, Version 11 The dashboard supports a minimum screen resolution of 1280 x Use a web browser to navigate to the MSM VM. The URL format is where FQDN is the fully qualified domain name of the MSM VM. The MSM VM has to be able to ping the FQDN of the Vision Core VM. If it cannot, a host file entry for the Vision Core VM must exist on the MSM VM. 51 Upgrading an MSM VM

52 2 Log on with your username and password. The default credentials for the dashboard are: Username: admin Password: This password should be changed to protect the system from unauthorized access. If this is the first time you have opened the dashboard, there is a quick tour of some of the new features. The display takes a number of minutes to appear. 3 Click About at the end of the screen and verify the version number is correct. If the search field returns a message Unable to execute search when you log on to the MSM, the database rebuild has not completed post-upgrade. Please allow 15 minutes for this process to complete and log on to the MSM VM again. What to do next If using a single MSM VM, upload the compliance content using the Vision dashboard. If using a single-site cluster MSM VM, repeat upgrading MSM VM steps for non-seed MSM nodes and then upload the compliance content using the Vision dashboard. If using a multi-site cluster MSM VM, repeat upgrading MSM VM steps for non-seed MSM nodes in the same data center, followed by non-seed MSM nodes in the second data and so on and then upload the compliance content using the Vision dashboard. Uploading compliance content Use the dashboard to upload and install new compliance content. You can get new compliance content from the VCE Download Center. Before you begin To install new compliance content, it must meet the following requirements: All of the XML content must be in a compressed ZIP file. The ZIP file must contain at least one valid XCCDF file and one valid OVAL file. Click the menu icon ( ) in the toolbar and select Manage > Compliance Policies. Results The Manage Compliance Policies dialog box appears. The prompts step you through the process of uploading the compliance content ZIP file, setting the target profile, and running compliance scans. Upgrading an MSM VM 52

53 What to do next After uploading any new compliance content, you need to re-run all compliance scans. Re-entering the custom display names In a single MSM deployment, custom display names are not retained after an upgrade. Therefore, you need to re-enter the names you defined before you began the upgrade process. Custom display names are retained in a clustered environment. Re-enter the custom display names. Refer to the dashboard help for more information on renaming the display names. Upgrading the Vision Shell Security Hardening remediation extension pack If your Vision software includes the Shell Security Hardening Remediation Extension Pack, it must be upgraded after the MSM VM upgrade has completed. 1 Download the RPM file for the security remediation pack from the VCE Download Center to a location on the MSM VM. The filename has the following format: vision-shell-security-extension-pack-x.x.x.x-build_number.x86_64.rpm where x.x.x.x is the Vision software release number. 2 Start an SSH session to the virtual machine and log in as root. 3 Navigate to the location of the RPM file for the security remediation pack and type the following command. rpm -Uvh rpm_filename.rpm Upgrading the remote host for the Vision shell After upgrading the MSM VM, all users accessing the shell from a remote host need to upgrade their remote shell installation. Before you begin The RPM file for the remote shell must be copied to each remote host. The filename has the following format: 53 Upgrading an MSM VM

54 vision-shell-remote-x.x.x.x-build_number.x86_64.rpm where x.x.x.x is the Vision software release number. 1 Start an SSH session to the virtual machine for the remote host and log in as root. 2 Navigate to the location of the RPM file for the remote host and type the following command. rpm -Uvh rpm_filename.rpm What to do next Start a shell session on the remote host and verify that it initiates correctly. Removing a VM snapshot As a best practice, remove VM snapshots after you successfully upgrade the VMs. If a VM is part of a cluster, do not remove the VM snapshot until all VMs are successfully upgraded. Refer to the VMware documentation for more information. VMware knowledge base article ID provides information on best practices for snapshots in a VMware environment. Upgrading an MSM VM 54

55 Upgrading the MSP VM Perform this procedure to upgrade the MSP VM. Taking a snapshot of the MSP VM Before upgrading, power down the MSP VM and create a snapshot. Use the snapshot to revert the VM to its previous state if any problems are encountered during the upgrade process. Before you begin Connect to the MSP VM. 1 Type shutdown -h now to power down the VM. The following message displays: The system is going down for halt NOW! 2 Log on to the VMware vsphere Client using an account with administrative privileges. 3 In the Navigation bar, select Home > Inventory > Hosts and Clusters in the following screenshot: The VMware vsphere Client displays the hosts and clusters available in the environment. 4 Navigate to the VM for which you want to take a snapshot. 55 Upgrading the MSP VM

56 5 Right-click the VM and select Snapshot > Take Snapshot in the following screenshot: The VMware vsphere Client prompts you to enter a name and description for the snapshot. 6 Specify a name and description for the snapshot. Choose a name and description that are easy to recognize and meaningful to others. 7 Clear the check boxes to snapshot the VM memory and quiesce the guest file system, if available. 8 Click OK to take the snapshot of the VM. What to do next Power on the VM and log in. Starting the MSP VM upgrade Execute vcevision_msp_upgrade-<buildnumber>.vce to upgrade. Before you begin Verify the MSP VM can be directly upgraded. Check the list of supported upgrade paths to determine which path best suits your system. Take a snapshot of the MSP VM. Connect to the MSP VM using SSH. Ensure that all Vision Core VMs connected to the MSM VM being upgraded have been powered up. 1 Copy vcevision_msp_upgrade-<buildnumber>.vce to the /root directory on the MSP VM. Upgrading the MSP VM 56