Application Discovery

For additional information not included in the online help and documentation for Application Discovery, see VSE Management Software 4.1 Update 1 Documentation Addendum.

Major Issues

The following is a major issue for Application Discovery.

Workloads Defined for Red Hat Linux Systems in Virtualization Manager Using the “by application” Selection Prevent Performance Data Collection

When you define a workload for a Red Hat Linux system in Virtualization Manager based on the “by application” selection, Application Discovery supplies a procmap file that has no PIDs listed within it. To the user, it appears that the workload definition was successful, and the empty file can be found in /var/opt/amgr/procmaps. However, gWLM and the Utilization Provider cannot use this workload definition to collect application-specific data.

Workaround Avoid using the “by application” selection to define workloads for Red Hat Linux servers. If an empty procmap file is created, remove the workload associated with it.

Minor Issues

The following are minor issues for Application Discovery.

Application Discovery Could Display Incorrect Processor Clock Speed on Integrity Managed Systems On Itanium-2 processors the interval timer register runs at different frequency than the processor core, and so the kernel must additionally provide the processor core frequency to Application Discovery.
In Application Discovery's host tab, 1600 mHz Itanium systems may be displayed as running at 400mHz. Processors are shown as being slower than they really are.
Workaround VSE's own information box on a logical server displays the correct processor speed.

Application Discovery

Technical documentation

» Table of Contents

» Index

Major Issues

Workloads Defined for Red Hat Linux Systems in Virtualization Manager Using the “by application” Selection Prevent Performance Data Collection

Minor Issues