Foglight 7.1.0 - Upgrade Guide

Upgrade Foglight Resource Optimizer

The latest version of Foglight Resource Optimizer is 7.1.0.

Foglight Resource Optimizer 7.1.0 requires Management Server version 7.1.0 or Foglight Evolve 7.1.0.

Foglight Resource Optimizer for VMware Environments also requires Foglight for VMware version 7.1.0.

Foglight Resource Optimizer for Hyper-V Environments also requires Foglight for Hyper-V version 7.1.0.

NOTE: When upgrading VMware-Optimizer-5_6_16_1.car to version 5.7.0 (or later), follow one of these processes: • Upgrade the VMware-Optimizer-7_1_0.car before upgrading Optimizer-7.1.0 car. • Disable VMware-Optimizer-7_1_0.car before upgrading to Optimizer-7_1_0.car and VMware-Optimizer-7_1_0.car.

NOTE: After installing the Virtual-VMware-7_1_0.car cartridge, existing vCenter agents (VC agents) must be updated using the Update Agent button in the VMware Environment > Administration tab.

NOTE: After installing the Virtual-HyperV-7_1_0.car cartridge, existing HyperV agents must be updated using the Update Agent button in the HyperV Environment > Administration tab.

Upgrade Foglight for Storage Management cartridge

The latest version of the Foglight for Storage Management cartridge is 7.1.0.

Foglight for Storage Management cartridge 7.1.0 requires Management Server version 7.1.0 or Foglight Evolve 7.1.0. Prior to upgrading the Storage Management cartridge, you must update Foglight for VMware to version 7.1.0. For more information, see the Foglight for VMware Release Notes.

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.

NOTE: This upgrade process has changed since the previous release.

Upgrade Foglight for VMware

The latest version of Foglight for VMware is 7.1.0.

Foglight for VMware 7.1.0 requires Management Server version 7.1.0 or Foglight Evolve 7.1.0.

Upgrades are supported from Foglight for VMware 5.6.15.x and later. Upgrades from the versions earlier than 5.6.15.x are not supported.

Important: The VMware Performance Agent uses a Virtual Center account to log in to the monitored Virtual Center. The administrative role associated with that account must be granted the Performance > Modify intervals privilege. When collecting traffic-type network metrics from the monitored ESX hosts, this privilege enables the VMware Performance Agent to change the performance metric counter levels in order to collect this data. On the Virtual Center server, verify that the user has the following privileges:

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 Release Notes.

Upgrade Foglight for VMware Horizon View

The latest version of Foglight for VMware Horizon View is 7.1.0.

Foglight for VMware Horizon View 7.1.0 requires Management Server version 7.1.0 or Foglight Evolve 7.1.0. It also requires Foglight for VMware 7.1.0 (or later) to be installed and enabled on the same Foglight Management Server.

NOTE: The Summary view for any Unmanaged or Terminal Server Hosts instances would displays no data. This is due to the default properties used by the View Discovery Wizard to create Infrastructure agents, for any Unmanaged or Terminal Server Hosts.

NOTE: If some instances on the list do not have a corresponding Infrastructure agent, you must first create an Infrastructure agent manually, define appropriate agent properties, and create the correct credentials for them. Alternatively, you can add these instances to an existing credential’s resource mapping.