Documente Academic
Documente Profesional
Documente Cultură
Version 3.5.1
Upgrade Guide
Revision history | 2
Contents
Introduction................................................................................................................................................. 5
System requirements................................................................................................................................. 6
3 | Contents
Configuring the Plug-in for vCenter...................................................................................................... 43
Installing the Plug-in for vCenter in a multi-domain Cisco UCS environment................................ 43
Verifying the Plug-in for vCenter installation........................................................................................ 45
Contents | 4
Introduction
This document provides instructions for upgrading to Dell EMC Vision Intelligent Operations Version
3.5.1.
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
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.
MSM VM 12 4 250
MSP VM 1 2 250
The Vision Core VM, MSM VM, and MSP VMs can be installed on the following Advanced Management
Platforms (AMP) and storage types:
AMP-2HA - VNXe3200
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:
System requirements | 6
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: https://support.vce.com/
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:
Related information
7 | System requirements
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.
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.
If upgrading from Version 3.3.0 or later, install an upgrade bundle on the multisystem
prepositioning (MSP) VM. The upgrade bundle applies security and Vision software
updates.
Related information
Version 3.5.1
Procedure
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 hardening (optional).
3 Download the following file from the VCE Download Center for the MSP VM upgrade:
vcevision_msp_upgrade-<buildnumber>.vce
Related information
Procedure
Collect any custom display names defined for your existing installation.
The following are high-level steps required to upgrade a single-site cluster with a single MSM VM:
Procedure
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 (if upgrading from Version
3.3.0 or later).
Do not power on the MSP VMs until snapshots have been taken of the other VMs.
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.
6 Power on and log on to the MSP VM, if one is associated with the MSM VM.
Related information
Procedure
1 Check whether an NTP server is configured on each Vision Core VM, MSP VM, and MSM VM.
Related information
Procedure
Related information
Upgrading compliance content for the Vision Core VM (see page 34)
Upgrading the Vision Plug-in for VMware vCenter (see page 37)
Procedure
Related information
Before starting the upgrade process for the MSM VM, collect the custom display names.
Procedure
Related information
Upgrading the Vision Shell Security Hardening remediation extension pack (see page 53)
Upgrading the remote host for the Vision shell (see page 54)
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 1025279 provides information
on best practices for snapshots in a VMware environment.
Important: Upgrading a cluster of MSM VMs is supported only when upgrading from Version 3.3.0 or
later to Version 3.5.1.
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.
Procedure
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 (if upgrading from Version
3.3.0 or later).
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.
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.
Start the upgrade process with the MSM VM that is acting as the Cassandra seed node.
Procedure
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
Configuring the NTP server
Ensure that each VM is configured to use an NTP server.
Procedure
1 Check whether an NTP server is configured on each Vision Core VM, MSP VM, and MSM VM.
Related information
You can upgrade the Vision Core VM associated with MSM VMs in the cluster in parallel.
Procedure
Related information
Upgrading compliance content for the Vision Core VM (see page 34)
Upgrading the Vision Plug-in for VMware vCenter (see page 37)
Procedure
Upgrading an MSM VM
Use this procedure to upgrade each MSM VM.
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.
Make sure that the following are complete before starting the upgrade process for the associated MSM
VM cluster members:
Do not add any Vision Core VMs to any MSM VMs in the 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.
Procedure
What to do next
Identifying the MSM VM acting as the Cassandra seed node (see page 16)
Upgrading the Vision Shell Security Hardening remediation extension pack (see page 53)
Upgrading the remote host for the Vision shell (see page 54)
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 1025279 provides information
on best practices for snapshots in a VMware environment.
The following are high-level steps required to upgrade a multi-site cluster environment:
Procedure
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 (if upgrading from Version
3.3.0 or later).
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.
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.
Procedure
1 Check whether an NTP server is configured on each Vision Core VM, MSP VM, and MSM VM.
Related information
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.
Procedure
The IP address in the output is the MSM VM address that is acting as the Cassandra seed node.
Do not add any Vision Core VMs to any MSM VM in the cluster.
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.
You can upgrade the Vision Core VMs associated with MSM VMs in the cluster in parallel.
Procedure
Related information
Upgrading compliance content for the Vision Core VM (see page 34)
Upgrading the Vision Plug-in for VMware vCenter (see page 37)
Procedure
Related information
Upgrading an MSM VM
Make sure that the following are complete before starting the upgrade process for the associated MSM
VM cluster members:
Do not add any Vision Core VMs to any MSM VMs in the 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.
Procedure
What to do next
Upgrading the Vision Shell Security Hardening remediation extension pack (see page 53)
Upgrading the remote host for the Vision shell (see page 54)
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 1025279 provides information
on best practices for snapshots in a VMware environment.
Related information
Procedure
1 Type shutdown -h now to power down the VM. The following message displays:
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.
The VMware vSphere Client prompts you to enter 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.
What to do next
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.
Verify the Vision Core VM can be directly upgraded to 3.5.1. Check the list of supported upgrade
paths to determine which path best suits your system.
Validate the components and login credentials for all components in the vblock.xml file by
typing the following command:
configTool.sh -v filename
VNXe service account password for Vblock System 100, Vblock System 2xx, Vblock System
3xx, Vblock System 5xx, and Vblock System 7xx
Procedure
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
Argument Description
version Displays the currently installed version, the version of the upgrade, and
the list of RPM files that the upgrade bundle includes.
sh vcevision_core_upgrade-<buildnumber>.vce
The upgrade scripts start running and then prompts you with the following:
Option Description
y Proceed with the upgrade if you have taken a snapshot of the Vision Core VM.
If you type y, the upgrade scripts prompt you to accept the End User License Agreement (EULA).
6 Complete the EULA acceptance. The fields in the EULA cannot exceed 500 characters or contain
angle brackets.
a Scroll through the EULA until you see the Enter Name: prompt.
e 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.
After you accept the EULA, the upgrade process continues and the script displays a summary of
the upgrade, as in the following example:
The script then prompts you to authenticate to the CAS (Central Authenticated Service) service,
as follows:
If you enter an incorrect CAS password after three attempts, the upgrade process
stops. You must then restart the upgrade.
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:
c Type 2 to change the community string. The SNMP community string must match the string
set on the server.
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:
Navisphere CLI
Unisphere Client
Unisphere Server
SMI-S Provider
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:
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:
2 to change the domain name and username for the Application Host. You must include
the domain name before the username, using a backslash.
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):
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:
The script prompts you to configure the REST API protocol credentials, as in the following
example:
The script prompts you to configure the SNMPV2C credentials, as in the following example:
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.
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.
Procedure
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:http://www.vce.com
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.
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.
Check which version of the compliance content RPM is currently installed by running the following
command:
Ensure you have the CAS authentication credentials for the administrator user. The default
credentials are:
Username: admin
Password: 7j@m4Qd+1L
1 Copy the RPM file, or files, to any location on the Vision Core VM.
Type this command and perform the following steps separately for each RPM file you
plan to install.
Where:
For example, the following command installs the Vision Core compliance content:
The command saves compliance content from the RPM file to the following location on the Vision
Core VM: /opt/vce/compliance/content.
cd /opt/vce/compliance/content
sh install_content.sh
The installation script uses the API for Compliance Checker to install the compliance content. For
this reason, you must authenticate to the CAS service.
Results
The script installs the compliance content and a message displays as shown in the following example:
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 1025279 provides information
on best practices for snapshots in a VMware environment.
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
Do not remove the existing 2.6.x or 3.x version of the Plug-in for vCenter.
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)
Log in to the vCenter Server host with a user that has administrative permissions.
Procedure
1 Stop the VMware vSphere Web Client service on the vCenter Server host.
Related information
Removing this version of the Plug-in for vCenter (see page 61)
Log in to the vCenter Server host with a user that has administrative permissions.
Procedure
1 Navigate to C:\ProgramData\VCE\vce-plugin\
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.
Related information
Removing this version of the Plug-in for vCenter (see page 61)
To configure the Vision VPM, you must specify the email 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.
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 email 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
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.
Ensure that the /opt/vce/fm/conf/vblock.xml file is configured with the vCenter Server
hostname and administrator credentials.
Procedure
cd /opt/vce/plugins
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.
5 Type the username and password for the vCenter server. The username and password must be
for the administrator user. The following message appears:
Ensure one of the following versions of the VMware vSphere Web Client is installed:
5.5
6.0
The compatibility details of each version of the VMware vSphere Web Client (VWC) are outlined
in the following table:
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.
cd /opt/vce/plugins
To enable component counts to be shown at the top level on VMware vSphere 6.0
installations, follow these steps:
b Open \ProgramData\VMware\vCenterServer\cfg\vsphere-client
\webclient.properties
Ensure the VMware vSphere Web Client service is running on the VMware vCenter Server host.
Procedure
Where fqdn is the fully qualified domain name (FQDN), or IP address, of the vCenter Server.
4 Locate the VCE Vision(TM) Plug-in for vCenter section and then select Settings.
Property Description
Port Port number for the Central Authentication Service (CAS) on the
Vision Core VM.
The default is 8443.
7 Restart the web client services on the VMware vCenter Server virtual machine.
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
Procedure
2 Install the second Plug-in for VMware vCenter instance on a different domain:
For example,
b Type the password for VMware vCenter The following message displays:
c Type cd /opt/vce/plugins.
3 Repeat Step 1 and Step 2 for each Plug-in for vCenter installation on a new domain.
What to do next
Procedure
vpm list
5 Navigate to the settings page and verify that the version of the plug-in is displayed as 3.5.1.0.
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.
Related information
If you are redeploying an MSM VM, specify an NTP server IP address when configuring the
server.
Determine the NTP server to be used for the data center. Use the VLAN gateway or the gateway of the
VCE System.
Procedure
For each MSM VM and Vision Core VM, perform the following steps:
2 Type the following command to verify that the NTP server is accessible:
ntpdate -u <IP_address>
Result:
9 Sep 15:13:59 ntpdate[30770]: adjust time server IP_address offset 0.000154 sec
Upgrading an MSM VM | 46
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.
5 Save the changes and run the following command to start the ntpd service:
6 Type the following command for the ntpd service to start on reboot:
chkconfig ntpd on
Important: After you revert to a snapshot you will need to reboot the VM before attempting another
upgrade.
Procedure
1 Type shutdown -h now to power down the VM. The following message displays:
2 Log on to the VMware vSphere Client using an account with administrative privileges.
47 | Upgrading an MSM VM
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.
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.
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.
What to do next
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
Starting an MSM VM upgrade
Execute vcevision_msm_upgrade-<buildnumber>.vce to upgrade to version 3.5.1.
Verify the MSM VM can be directly upgraded to 3.5.1. Check the list of supported upgrade paths
to determine which path best suits your system.
Ensure that all Vision Core VMs connected to the MSM VM being upgraded are powered on.
Procedure
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
Argument Description
version Displays the currently installed version, the version of the upgrade, and
the list of RPM files that the upgrade bundle includes.
sh vcevision_msm_upgrade-<buildnumber>.vce
The upgrade scripts starts running and then prompts with the following:
49 | Upgrading an MSM VM
4 Type one of the following values:
Option Description
y Proceed with the upgrade if you have taken a snapshot of the virtual machine.
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:
6 Type y to restart.
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.
Start an SSH session to the MSM VM and complete the following steps:
2 Type the following command to change the Vision Core VM root user password for MSM:
/opt/vce/multivbmgmt/install/addSlibHost.sh <core_IPaddress>
where core_IPaddress is the IP address for the Vision Core VM where the password was
changed.
Upgrading an MSM VM | 50
3 Respond by entering yes. The script prompts you for the root credentials:
Enter the SSH credentials for System Library host 10.20.30.40 (attempt 1 of 3).
User name [Default: root]:
The script continues processing with a series of messages. When it has finished, the following
message is displayed:
The new password for the Vision Core VM will be picked up by the MSM VM during the next
collection cycle.
Procedure
The URL format is https://FQDN, 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
2 Log on with your username and password.
Username: admin
Password: D@ngerous1
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 for Version 3.5.1.
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.
The Vision Dashboard URLs have changed for Version 3.3.0. Users who have bookmarked
any pages in the dashboard prior to this release need to either create them again or modify
them. To modify bookmarks, the start of the URL:
https://FQDN/#/
https://FQDN/ui/ng/
Upgrading an MSM VM | 52
Before you begin
The ZIP file must contain at least one valid XCCDF file and one valid OVAL file.
Procedure
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.
What to do next
After uploading any new compliance content, you need to re-run all compliance scans.
Procedure
Refer to the dashboard help for more information on renaming the display names.
Procedure
1 Download the RPM file for the security remediation pack from the VCE Download Center to a
location on the MSM VM.
vision-shell-security-extension-pack-x.x.x.x-build_number.x86_64.rpm
53 | Upgrading an MSM VM
3 Navigate to the location of the RPM file for the security remediation pack and type the following
command.
The RPM file for the remote shell must be copied to each remote host. The filename has the following
format:
vision-shell-remote-x.x.x.x-build_number.x86_64.rpm
Procedure
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.
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 1025279 provides information
on best practices for snapshots in a VMware environment.
Upgrading an MSM VM | 54
Upgrading the MSP VM
Perform this procedure to upgrade the MSP VM.
Procedure
1 Type shutdown -h now to power down the VM. The following message displays:
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.
The VMware vSphere Client prompts you to enter 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.
What to do next
Verify the MSP VM can be directly upgraded to 3.5.1. Check the list of supported upgrade paths
to determine which path best suits your system.
Ensure that all Vision Core VMs connected to the MSM VM being upgraded have been powered
up.
Procedure
sh vcevision_msp_upgrade-<buildnumber>.vce --argument
Argument Description
version Displays the currently installed version, the version of the upgrade, and
the list of RPM files that the upgrade bundle includes.
sh vcevision_msp_upgrade-<buildnumber>.vce
The upgrade scripts starts running and then prompts you with the following:
Option Description
y Proceed with the upgrade if you have taken a snapshot of the virtual machine.
5 The upgrade process continues and a series of messages appear. When you reach the end of
the upgrade process, the script prompts you to restart the MSP VM:
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)
6 Type y to restart.
Verify that the version of the MSP VM is the version that you installed.
Procedure
Verify that the component services are running by running the following commands:
Results
The status for each service should appear as running or provide details about running processes.
What to do next
If you updated the MSP VM password, you must change the CAS password for the MSP VM to match the
CAS password on the MSM VM.
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 1025279 provides information
on best practices for snapshots in a VMware environment.
The MSM nodes must be powered on in the reverse order that they were powered down, starting with the
seed node.
Ensure you know the order in which the MSM nodes were powered down. If the order is unknown, begin
with the MSM nodes in the seed node's VMware vCenter, starting with the seed node.
Procedure
1 Power on the MSM seed node using the vCenter vSphere Client, open a console connection to
the VM, and wait for the log on prompt.
2 Perform the following for each MSM node in the same data center in the reverse order from the
shutdown order:
a Power on the next MSM node using the vCenter vSphere Client. Continue powering on each
MSM node in the cluster in five minute increments.
Repeat the recovery process for every MSM node in each data center of your
clustered environment.
b After all of the MSM nodes in all data centers are powered back on, type the following
command on each of the MSM nodes in the clustered environment:
vision start
This command checks whether each service is running. If the command does not run, the
service is started.
/opt/cassandra/bin/nodetool status
rabbitmqctl cluster_status
3 After all of the nodes in all data centers are powered back on, do the following:
a Check the Vision dashboard to ensure you can view your VCE Systems. If you cannot view
your VCE Systems, run the following command to restart the Tomcat service:
b Check the Compliance and Remediation section of the Vision dashboard and ensure the
compliance status appears. If the compliance status does not appear, type the following
command:
To help you isolate problems and troubleshoot issues, review log messages for the upgrade in the
following files:
/opt/vce/fm/logs/patch-<time_stamp>.log
/opt/vce/logs/patch/patch-<time_stamp>.log
/opt/vce/msp/logs/patch-<time_stamp>.log
If you encounter this issue, the following messages display in the terminal window:
Complete the following steps to restart the Vision Core VM and resolve this issue:
3 Run the following command to shut down the Vision Core VM.
shutdown -h now
Procedure
2 Log in to the vCenter Server host with a user that has administrative permissions.
3 Stop the VMware vSphere Web Client service on the vCenter Server host.
When deleting files, it's advised to complete a hard delete, that is press Shift + Delete.
This permanently deletes the files, as opposed to sending the deleted files to the
recycling bin.
What to do next
Verify that the Plug-in for vCenter is successfully removed by completing the following steps:
vpm list
2 Validate that the Plug-in for vCenter is not listed in the output.
Log in to the VMware vCenter Server host with a user that has administrative permissions.
Procedure
Use, copying, and distribution of any software described in this publication requires an applicable software license.
Copyright 2017 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks of
Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA in
February 2017.
Dell EMC believes the information in this document is accurate as of its publication date. The information is subject to
change without notice.
Copyright | 64