Application Discovery

Limitations

• Applications data on managed systems is not discovered by Application Discovery after a CMS upgrade or restore.

  If you previously were monitoring applications with Application Discovery, and later upgraded VSE Management Software on the CMS or restored the VSE Management Software on the CMS from a backup, applications data on managed systems might not be displayed after the upgrade or restore.

  Workaround  Reexchange Application Discovery agent certificates to reestablish communication between the CMS and the managed systems. Select ConfigureConfigure VSE AgentsExchange AD Agent Certificates... from the HP SIM menu to correct this issue.

• Workload definition in Virtualization Manager cannot retrieve details for applications after the following events:

  • Rebooting the CMS or a managed system

  • Reinstalling the Application Discovery agent on a managed system

  • Restarting the Application Discovery agent on a managed node

  If you view the properties for a workload that has application criteria in it, you might see red error text similar to the following:

  Could not retrieve details for the application with ID "Application Name", therefore this workload cannot be modified. Ensure Application Discovery is configured and running properly on the CMS and selected system.

  This is most often the result of a warmup ratio of less than 100% for the managed system.

  Workaround  Ensure the Application Discovery agent has established a connection with the CMS under the Admin/Config tab, AD Agents tab. Further, under the Discovery tab, verify that the warmup ratio (“Wrmup ratio” column) is at 100%. This issue should resolve itself when the ratio achieves 100%. For more assistance, see the “Troubleshooting and Error Messages” section in the HP Application Discovery Version 4.0 User's Guide.

• Using illegal characters when creating a regular expression in an AD template will crash the Application Discovery user interface.

  Application Discovery recognizes regular expressions constructed using Perl 5 or POSIX syntax and semantics. If you use characters or syntax not recognized by these conventions (shell syntax, for example), the AD user interface will crash.

  Workaround  See “PCRE - Perl Compatible Regular Expressions” at http://www.pcre.org/ for building valid regular expressions that you can include in AD application templates.

  In the event of a crash, go the HP SIM Tools menu, and select Integrated ConsolesApplication Discovery to start a new session.

• There is no vseassist check to verify that the Application Discovery agent is installed and running on managed systems.

  Workaround  Verify Application Discovery agent status by running ConfigureConfigure VSE AgentsCheck AD Agent States....

• New Application Discovery agent certificates must be exchanged even where managed systems already have a VSE 3.x agent installed.

  Use ConfigureConfigure VSE AgentsExchange AD Agent Certificates to re-configure those agents. For details, see “Complete the Certificate Exchange for Application Discovery” in the VSE Management Software Version 4.0 Getting Started Guide.

Major Issues

• The Applications tab on an HP SIM System Page is blank (displays no information) for managed systems where Application Discovery agent is not installed, configured, or running.

  Workaround  In the case where you know the managed system has an Application Discovery agent installed, and you think data should be visible in the Applications tab, see “Troubleshooting and Error Messages” in the HP Application Discovery Version 4.0 User's Guide to configure or start the agent.

Minor Issues

• In the situation where an existing managed system is removed from HP SIM (is no longer discovered by that CMS), and where Application Discovery agent is running and reporting to the current CMS, the Application Discovery agent continues to report to Application Discovery server on the CMS and the Application Discovery user interface continues to display the host that is no longer a managed system of that CMS.

  Workaround  To prevent this situation from occurring, it is recommended that Application Discovery agent be stopped before removing the managed system from HP SIM. Use ConfigureConfigure VSE AgentsStop AD Agents.... Alternatively, Application Discovery agent can be stopped by running /opt/amgr/bin/agent_stop as root on the HP-UX– or Linux-managed system.

• If the clock on managed systems are off by more than a few minutes to the current time on the CMS, then the Application Discovery agent communication with the CMS may be delayed by the clock differential.

• Application Discovery user interface screens display OS version number “SLES0” for SLES10 Linux managed nodes.