This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight Capacity Optimization
BMC TrueSight Capacity Optimization 20.02, 11.X, 10.X BMC Performance Assurance 9.X
- Are there any suggestions or best practice recommendations to follow in relation to the upgrade from an existing BMC Performance Assurance agent installation to a new BMC TrueSight Capacity Optimization Agent installation (where 'BMC TrueSight Capacity Optimization' Agent is just the new Licensed Product name for the BMC Performance Assurance agent)?
- Is it possible to automate the upgrade process without running the full product installation (setup.sh) on the remote agents to be updated?
- When doing an upgrade (either via the setup.sh installer UI or a silent installation, will the existing agent release be automatically removed from the machine?
The BMC Performance Assurance (BPA) / BMC TrueSight Capacity Optimization (TSCO) Agent installation or upgrade is generally a straight forward process, but there are some best practice recommendations:
- Ensure that your BPA/TSCO Agent version is the same or lower than the TSCO Gateway Server version. For example, the TSCO version 10.5 agent is not officially supported by the TSCO version 10.3 Gateway Server.
000030268: Is it necessary for the TSCO Gateway Server console on the managing node to be at the same or higher version than the TSCO Agent versions installed on the remote nodes? What if I am running a different agent version on the remote node? (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000030268)
- After the installation or upgrade of the TSCO Agent, it is a best practice to also apply the latest Cumulative Hot Fix (CHF) package that is available:
- Be aware that when a BPA/TSCO agent installation is upgraded to a new release, the upgrade clears all of the active collection requests (because the *.als file where the collection requests are registered on the agent isn't migrated forward). This means that the TSCO Agent will not collect data for the day of the upgrade. Data collection will resume at the next day after the TSCO Gateway Server has issue the new day's data collection requests.
If one were to require data collection for the date of the upgrade an ad hoc Manager run to collect for the remainder of the day can be started. For example, let's say the upgrade occurred at 1:00 PM, you can submit an ad hoc Manager run that collects data from (say, 1 PM - 11:59 PM).
- In general, when doing a deployment of an agent upgrade the best practice recommendation is to use the silent installation. It is possible to deploy the silent installation package using an automated software deployment tool, such as thee BMC Server Automation (Bladelogic) product.
The creation of a package to be deployed via an external software deployment utility is outside of the scope of TSCO Technical Support and thus we do not have example scripts or processes to provide.
Please refer to this document page about how to install the BMC TrueSight Capacity Optimization components:
Installing the Gateway Server and components
Installing the Agent in silent mode
Q: Is the silent install the only option to install or upgrade the TSCO Agent?
No, One can also use the installation GUI to install or upgrade the agent, but if a large number of agents are to be upgraded the silent mode is generally a much more efficient upgrade option.
Q: Does the silent install automatically perform an uninstall of the old version and the install of the new one?
On Windows the uninstall is done by default; but on Linux/Unix, the old version is not uninstalled by default. If you want to uninstall the old Perform Agent version there is an option that can be specified in the silent options deployment file (AgentSilentInstallationConfiguration.txt). Change:
There is also an option to uninstall the existing Agent version available via the TSCO installer UI.
Note: if you're using Silent mode and not running the installation as the root user, please don't forget to run the b1configXXXX.sh as root to complete the installation of the agent.
Note2: In order to apply the latest CHF for the TSCO Agent the patch package must be installed as the root user (since it needs access to replace the 'bgscollect' binary which is owned by root).