Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight Evolve 9.2 - Upgrade Guide

Component versions

The upgrade process automatically updates your product components to the following version numbers:

•
Management Server, version 5.9.7
 
* 
NOTE: Foglight for Infrastructure 5.9.7 is embedded with the Management Server.
•
Agent Manager, version 5.9.7
•
Foglight for Action Packs, version 5.6.3.8
•
Foglight Automation, version 5.6.3.8
•
Foglight Capacity Director, version 5.8.2
•
Foglight Change Analyzer, version 5.8.2
•
Foglight for Hyper-V, version 5.8.2
•
Foglight for Perspectives, version 5.8.2
•
Foglight Resource Optimizer, version 5.8.2
 
* 
NOTE: Foglight Resource Optimizer provides recommendations for changes in the VMware® or Hyper-V® environments, to make more efficient the use of resources. This requires that the VMware or Hyper-V agent is configured with a user that has elevated privileges, beyond the read-only privileges required for monitoring. For a list of privileges required for the VMware or Hyper-V agent, refer to section “Configuring Monitoring Agents for Data Collection” in the Foglight for VMware User and Reference Guide and Foglight for Hyper-V User and Reference Guide, respectively.
•
Foglight for Storage Management cartridge, version 4.8.5
•
Foglight for VMware, version 5.8.2
 
* 
NOTE: Java 7 or later requires that the vCenter Certificate’s public key length must be 1024-bits or higher and should not use MD5.
If you try to add a vCenter for monitoring, and these requirements are not met, the server generates a Certificate error and cannot add the vCenter. The vCenter server Certificate should be updated to 1024-bits or higher and no MD5, to be able to add it for monitoring. For more information, see the Foglight for VMware 5.7.5 Release Notes.
•
Foglight for VMware Horizon View, version 5.8.2
•
Foglight for vCloud Director, version 5.8.2
•
Foglight for Citrix XenDesktop and XenApp, version 5.8.2
•
Foglight Hybrid Cloud Manager, version 1.8.0
•
Quest Protect Dashboard, version 1.8.0
•
Foglight Cost Director, version 5.8.2
•
Foglight for NetVault, version 1.4.0
•
Foglight for Container Management, version 3.0.0
•
Foglight for Cloud Migration, version 5.8.2
•
Foglight for Apache, version 5.9.0
•
Foglight Net Monitor, version 5.9.7
•
Foglight Web Monitor, version 5.9.7
•
Foglight for Active Directory, version 5.8.2
•
Foglight for Exchange, version 5.8.2
•
Foglight for Office365, version 5.8.2

For a complete list of fixes for any of these components, refer to the release notes that accompany them. If you decide to maintain the version you have of any of the updated components, as opposed to upgrading, you will not acquire the new fixes for that component.

Upgrading to Foglight Evolve

Depending on the products you already have installed, the upgrade path to Foglight Evolve may differ. Refer to the applicable set of instructions for your existing product:

•
Upgrading Foglight Evolve from Foglight for Virtualization, Enterprise Edition or a previous version of Foglight Evolve
•
Upgrading cartridges in a Federated Server environment

Upgrading Foglight Evolve from Foglight for Virtualization, Enterprise Edition or a previous version of Foglight Evolve

This section guides you through the process of upgrading Foglight Evolve from Foglight for Virtualization, Enterprise Edition or a previous version of Foglight Evolve.

A typical Foglight Evolve installation includes a Management Server, at least one Foglight database, a number of cartridges installed on the server, and usually just one installation of the Agent Manager. There may also be customizations to the server in the form of custom cartridges.

The upgrade process updates each of these components to the latest version of Foglight Evolve, automatically:

•
Preparing to upgrade Foglight Evolve
•
Upgrading Foglight Evolve

When upgrading Foglight Evolve from Foglight for Virtualization, Enterprise Edition, the license that is provided to the existing users must be updated:

•
Upgrading Foglight Evolve License

Some deployed agents may need to be manually updated - for more information see:

•
Upgrading the Agent Manager
•
Upgrading Foglight Evolve agents

Preparing to upgrade Foglight Evolve

 

* 
NOTE: Upgrades from Foglight for Virtualization Enterprise (FVE) edition to Foglight Evolve edition are not automatically free. To take advantage of the changed licensing and new functionality in Foglight Evolve, contact your Quest Account Manager to review your requirements.

Preparing for a Foglight Evolve upgrade from Foglight for Virtualization, Enterprise Edition or a previous version of Foglight Evolve is straightforward, but may be time-consuming. Before upgrading you should:

1
Create a support bundle from your Management Server. For information on how to do this, see the topic “Managing Support Bundles” in the Administration and Configuration Guide.
2
Back up the file system in which Foglight for Virtualization, Enterprise Edition or Foglight Evolve is installed. For information on how to do this, see the topic “Backing up Foglight” in the Administration and Configuration Help.
3
Back up your database. For information on how to do this, see the topic “Backing up Foglight” in the Administration and Configuration Help.
 
* 
IMPORTANT: If you are using Oracle® RAC, back up the oracle-ds.xml file (or any other database connection files) before performing the upgrade.
4
Deactivate all agents through the Agent Status dashboard (Dashboards > Administration > Agents > Agent Status).
5
If you are upgrading to the Agent Manager-based VMware Performance Agent, identify the machine that will run the agent.
Recommended operating systems:
•
64-bit Windows® Server 2012 R2, with 4 GB or more RAM
•
64-bit Linux®, with 4 GB or more RAM
If you are currently running the VMware Performance Agent on a 64-bit Management Server, you can use the embedded Agent Manager for the VMware Agent to monitor up to 500 total VMs.
Note for installations monitoring large VMware environments

Some installations monitoring large VMware® environments have customized the VMware agent memory settings. These settings must be reapplied because the upgrade procedure overwrites them with the default settings.

For each Agent Host with existing VMware Performance agents:

1
On the agent machine, open the baseline.jvmargs.config file for editing. The file is located in the <Agent_Manager_home>/state/default/config directory.
2
Make note of the vmparameter.x values.
If the values on your agent are different, they must be reapplied after the upgrade.
3
After upgrading and reapplying the values in the baseline.jvmargs.config file, remove the deployed negotiation configuration settings directory (<Agent_Manager_home>/state/default/config/deployments), and restart the Agent Manager.
The new settings take effect after the Agent Manager is restarted.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation