サポートと今すぐチャット
サポートとのチャット

Foglight 7.3.0 - Upgrade Guide

Understand product versions Best practices Upgrade the Foglight Management Server Upgrade the Foglight Agent Manager Upgrade the Database cartridges Upgrading the Infrastructure Management cartridges Upgrade the Integration cartridges Upgrade the cartridges in a federated or High Availability (HA) environment Appendix: Deploying an agent package using the browser interface

Upgrade the Agent Manager

To upgrade the Agent Manager to the latest version:
1
Navigate to Dashboards > Administration > Cartridges > Cartridge Inventory.
2
On the Installed Cartridges tab of the Cartridge Inventory dashboard, click Install Cartridge.
3
In the Install Cartridge dialog box, click Browse to locate the .car file you require to upgrade the Agent Manager.
 
* 
NOTE: On all platforms, the Agent Manager 5.8.1 and later includes an updated version of the Java® Runtime Environment (JRE). Therefore, you cannot use the Agent Manager patch cartridge (FglAM-patch-<version>.car) to upgrade from a pre-5.8.1 version to 5.8.1 or later. For that upgrade, you must use either FglAM-all-<version>.car, or one or more of the platform-specific FglAM-<platform>-<version>.car files.
4
Ensure that the Enable on Install box is selected.
 
* 
IMPORTANT: If the Enable on Install box is not selected, you must manually enable many different cartridges that are contained in the upgrade .car file you are deploying.
5
Click Install Cartridge to install the latest version of the Agent Manager upgrade .car file on the Management Server. Do not delete any of the old .car files.
A progress message appears and, after a few moments, the Operation(s) Complete message box appears, indicating success.
6
Click OK to close the message box.
7
On the navigation panel, click Dashboards > Administration > Agents > Agent Managers.
The Agent Managers dashboard lists connected Agent Managers.
8
Select one or more Agent Managers that you want to upgrade. If you are selecting more than one Agent Manager, they must have the same operating system name.
9
Click Upgrade.
The Deploy Agent Package dialog box opens.
10
From the Package list, select the version to which you want to upgrade, and then click Deploy.
It may take some time for the upgrade process to complete. The more Agent Managers you upgrade, the longer it takes. Once the upgrade is complete, the Agent Manager restarts.
After the “Agent deployment was successful.” message and a green checkmark appear in the Deploying Agent Package box (that is, after the Agent Managers have restarted), you must wait a few additional minutes for the version number of the affected Agent Manager to be updated.
11
On the Agent Managers page, click Refresh.
The version number for the Agent Manager you have modified is updated to the new number, for example 7.3.0.

Upgrade concentrators

When the Agent Manager is deployed using concentrators, all of the concentrators need to be upgraded before the downstream clients are upgraded. Otherwise, when a downstream client is restarted, it sends its upstream concentrator messages in an unknown format, making communication between the two impossible.

Consequently, the Upgrade button on the Agent Hosts dashboard is disabled for downstream clients until all of the upstream concentrators have been upgraded to the latest version.

See the Foglight Agent Manager Installation Guide for more information about running Agent Managers as concentrators.

Upgrade installations with multiple state instances

When upgrading an Agent Manager installation that has multiple state instances running, all the state instances must be upgraded simultaneously, otherwise the upgrade process fails with errors.

You must use one of the following upgrade options:

•
Option 1: Select all hosts in the Agent Manager installation-set when initiating the upgrade.
•
Option 2: If the hosts must be upgraded individually, deactivate all of the Foglight 4 based agents running on the Agent Manager hosts that have already been upgraded in the installation-set.

Once you finish upgrading the Agent Manager hosts, restart each of the agents that were deactivated.

 
* 
NOTE: There is currently a know issue related to this type of installation. For details, see FglAM vm.config file migration fails under multi-state installations.

 

Upgrade a 32-bit FglAM installation on a 64-bit operating system

This section provides instructions for upgrading an existing 32-bit FglAM installation on a 64-bit operating system.

 
* 
NOTE: When existing installations of 32-bit FglAM instances on 64-bit operating systems are improperly updated to 64-bit installations, this causes the FglAM instances to fail when they are restarted. New 32-bit installations of FglAM 5.8.1 or later are not affected by this issue.
To upgrade an existing 32-bit FglAM installation on a 64-bit operating system:
1
Shut down the existing FglAM instance.
2
Install a “new” copy of FglAM, version 5.8.1 or later, on the same system.
3
Edit the “new” {{state/default/config/fglam.config.xml}} file, and replace the {{<config:id> ... </config:id>}} value with that obtained from the “existing” FglAM installation.
4
Edit the “new” {{state/default/config/fglam.config.xml}} file, and replace the {{<config:host-display-name> ... </config:host-display-name>}} value with that obtained from the “existing” FglAM installation.
5
Start the new FglAM installation and deploy to it all cartridges that we deployed to the old FglAM installation.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択