Page tree

Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

In TrueSight Capacity Optimization data collection by means of Agents and Proxy Agents is accomplished by installing a Gateway Server . The collected data is periodically transferred to the Gateway Server, where it is automatically processed into hourly intervals and saved in text files called vis files.

Agent are typically installed on the machine whose data is to be collected. In the case of Windows machines, it is also possible to collect data agentlessly using Windows Management Instrumentation (WMI). In this case, you designate a special Windows machine as a proxy agent node. You install an Agent on this machine, and this single agent collects data from a list of Windows machines that you specify. For more information, see Considerations for installing Agents on Windows, UNIX and Linux.

Gateway Server data and retention

On the Gateway Server machine, the collected data is processed in an automated fashion by a program called Analyze. This program also outputs other files. For more information, see Outputs of Analyze.

As a general guideline, you should keep about three months' worth of vis files. These are useful in case you need to "recover" data (see recovery section below).

For UDR and vis files, it is recommended to keep three months worth of data, of which the oldest two months could be kept compressed to save space.

Manager runs and domains

  • Each manager run should have no more than 4 domains (one domain is one vis file)
  • One domain should have no more than 25 nodes (managed systems)
  • Information about Autonode Discovery is covered in the following attachment: Setting up and configuring BMC Capacity Optimization EE.

Loading Gateway Server data into BMC TrueSight Capacity Optimization

The recommended method to load Gateway Server collected data into BMC TrueSight Capacity Optimization is to use an OOTB Gateway Server vis files parser. For more information, see the following topics:

The vis files are produced on the Gateway Server machine. It is reasonable to assign one manager run to one ETL, if the manager runs contain 4 vis files. If the manager runs contain only one vis file each (i.e., one domain each), then it is reasonable to assign up to four manager runs to a single ETL.

The recommended way to automatically move these files to the BMC TrueSight Capacity Optimization ETL Engine is to use the via gateway service selection in the "Extractor mode" option in the BMC TrueSight Capacity Optimization Gateway Server VIS files parser ETL.

Multiple vis files parser ETLs

If there are multiple vis file parser ETLs scheduled on a scheduler, then we recommend they be included in a task chain, with the "parallelism" parameter set to twice the number of CPU cores available on the ETL Engine. In addition, you should follow all the sizing guidelines for any ETL Engine. For more information, see Sizing considerations for ETL Engine Servers.

Discovering and configuring Gateway Server

The Gateway Manager page in the Admin section of the BMC TrueSight Capacity Optimization Console lets you look at the available consoles and configure additional ones. The Gateway Manager page offers various management operations to deal with the Gateway Server and their Manager runs that are producing data. For more information, see Gateway Manager.

Recovering data that has not been loaded into BMC TrueSight Capacity Optimization

If data is missed for any reason, you can "recover" it using existing vis files provided you have been retaining them according to the recommended procedure above. For recovery, you can use a Gateway Server vis files parser ETL with a special configuration. Note the Data Retention section above; the main reason to keep vis files for three months is to enable data recovery. For more information, see Recovering data using the vis files parser.

When you use the vis files parser as a recovery ETL, you can use a single one to recover all the Gateway Server ETLs in a task chain. The particular vis files to be recovered are automatically identified by recovery scripts on the Gateway Server and made available in a predefined directory for the vis files parser to consume. For more information, see Creating recovery scripts.

Appendix: Gateway Server platform classifications

Platform classificationBMC TrueSight Capacity Optimization System Type(s) for compute
A machine running a PowerVM hypervisorVirtual Host - AIX PowerVM
AIX in a PowerVM LPAR/SPLPARVirtual Machine - AIX LPAR; Virtual Machine - AIX Shared Processor LPAR
VIO Server in PowerVMVirtual Machine - AIX VIO LPAR
A workload partition in AIXWorkload Partition - AIX WPAR
Solaris in any LDOM/Zone/DSDVirtual Host - Solaris; Virtual Machine - Solaris LDOM; Virtual Machine - Solaris Zone; Virtual Machine - Solaris Dynamic System Domain
HP IntegrityVirtual Host - HP Integrity; Virtual Machine - HP Integrity
HP-UX virtualizationVirtual Host - HP nPar/vPar; HP nPartition; HP vPartition
Xen hypervisorVirtual Host - Xen; Virtual Machine - Xen
Microsoft Hyper-VVirtual Host - HyperV; Virtual Machine - HyperV
KVMVirtual Host - KVM; Virtual Machine - KVM
Any operating system running directly on a "standalone" x86 based machineGeneric
Any operating system running on an x86 based hypervisorVirtual Node - HyperV; Virtual Node - KVM; Virtual Node - VMware; Virtual Node - Xen