Introduction

Check that OpenSSL is installed on the managed node and that it is free of outstanding security issues.

To learn about the latest security bulletins, check http://www.openssl.org/news.

	OpenSSL : OpenSSL is required on managed systems so that the Application Discovery agent software can securely send application information to the CMS. To obtain the latest version of OpenSSL for HP-UX, go to the Security and Manageability page on HP Software Depot web site (http://software.hp.com/). Find OpenSSL and click the download link. On Linux systems, OpenSSL is usually installed by default, or it can be installed from the Linux distribution media. To avoid a number of known security vulnerabilities, use one of the following versions: 0.9.7l or later for the 0.9.7 branch, or 0.9.8d or later for the 0.9.8 branch. Check the web site http://www.openssl.org/news for announcements of OpenSSL security advisories and dates on various historical OpenSSL software releases.

Check that HP WBEM Services software is installed on the managed node and that it is a compatible version.

To obtain a new version of HP WBEM Services for HP-UX, go to the Security and manageability page on HP Software Depot web site (http://software.hp.com/). Find 'WBEM Services for HP-UX'. For details on which is the appropriate version to download by operating system version, please consult the VSE Management Software Installation and Update Guide system requirements for WBEM. AppDiscAgent runs with any 2.x version of HP WBEM Services for HP-UX.

To obtain a new version of HP WBEM Services for Linux, go to the Internet ready and networking page on HP Software Depot web site (http://software.hp.com/). Find HP WBEM Services for Linux, and click the download link.

Check that the Application Discovery WBEM provider has been installed on the managed node.

Type the following command on the command line of the managed node:

# cimprovider -l -m AmgrAgentProviderModule
  AmgrAgentProvider

A return of AmgrAgentProvider indicates that the WBEM provider is installed.

If this value is not returned, first clean up the provider by typing:

# /opt/amgr/bin/agent_wbem_cleanup
  Removing the AmgrAgentProvider

Then configure the provider by typing the following on the command line:

# /opt/amgr/bin/agent_wbem_config
  Loading Application Discovery schema
  Loading Application Discovery metadata

Check that the Application Discovery agent certificate has been installed on the managed node.

Type the following on the command line of the managed node:

# ls /var/opt/amgr/ssl/agent_cert.pem 
  /var/opt/amgr/ssl/agent_cert.pem

If agent_cert.pem is not listed, you can create the certificate by typing the following on the command line:

# /opt/amgr/bin/make_agent_cert 
  Host name is xyz.cup.hp.com 
  ... 
  Finished agent certificate creation.

Check that the application is not hidden from view in the application table.

Tables that list applications are preceded by the 'Application Visibility' drop-down that lets you toggle to Show hidden apps. Select this option and scan the table for your application.

Also, check that no filters are in operation in the table. (If one or more filters have been applied to the table, they are listed on the right in the dark gray table header bar.) To remove current filters, right-click anywhere on the table, and select Clear all filters.

If you cannot find the application, Application Discovery is not currently recognizing the application as matched to a template.

It is possible that certificate exchange has not been completed.

See “Completing Certificate Exchange” for instructions on completing the certificate exchange. The Application Discovery agent starts running (and begins sending data to the Application Discovery server) on completion of the certificate exchange.

	Have you recently restored or removed and reinstalled the CMS? : A restore or removal of the central management server also removes the certificate recognition previously established between Application Discovery server on the CMS and Application Discovery agents on managed nodes. This relationship must be re-established when the CMS is reinstalled or restored by completing the Application Discovery certificate exchange.

Check that Application Discovery is showing that the discovery ratio is 100%.

Check that any usage of regular expression syntax in the defining application template is correct.

Application Discovery recognizes regular expressions constructed using Perl 5 or POSIX syntax and semantics.

Check that any string or regular expression used in the executable path field of the defining application template describes the desired running process.

Application Discovery differs from Global Workload Manager (gWLM) in how it matches user input data to discovered applications. gWLM uses a combination of a fully qualified path and retrieved inode information to find a process on one managed node. Application Discovery does not infer the location of running processes based on the presence or location of installed applications. For broader coverage of all running processes (not just those associated with installed software packages) within a network of machines, Application Discovery matches strings and regular expressions exactly when comparing templates to running processes.

It may help to think of the difference between AD and gWLM this way:

To check your application template data against the process data that Application Discovery has catalogued, you can consult the following:

	NOTE: Where large amounts of data are present in tables, it can be useful to sort or filter the data to find the exact process and associated attributes for which you are searching.

Check that the host appears on the list of hosts managed via HP Systems Insight Manager.

An unlisted host is not being managed via HP Systems Insight Manager, and therefore, cannot be discovered by Application Discovery.

To learn how to add a managed system to HP Systems Insight Manager's system list, see “Setting up managed systems” in HP Systems Insight Manager User Guide.

Check that the host is marked as 'visible' in Application Discovery.

Check that no firewall is blocking port 22 (used by SSH) or port 5989 (used by WBEM) on managed systems.

Unblock the ports.

Once this action is taken, check that Application Discovery is receiving messages from the host. (See #8 in this section.)

Check that the managed node has been configured to allow remote command execution by the CMS.

To set the managed node to allow remote command execution, type the following:

/opt/mx/bin/mxagentconfig -a -n hostname -u root

Once this action is taken, check that Application Discovery is receiving messages from the host. (See #8 in this section.)

Check that SSH is configured correctly on the managed node .

In this case, you may need to repair the HP Systems Insight Manager agent on the managed system. Click the following menu selections: Configure, then Configure or Repair Agents. Make sure to check the box for 'configure SSH access' before running the repair agent.

To verify that the repair action has resolved any SSH configuration problem, you can issue a remote ls command toward the managed system by doing the following:

If the configuration is still not working, you may see an error message:

Ssh Operation failed for node:managed_node. 
The connection could not be established. 
Reason:Failed to read remote identification

In conjunction with this, you may also notice that running mxagentconfig and selecting ConfigureConfigure or Repair Agents fail on the target managed node.

To reconfigure SSH on the managed node, do the following steps:

Once this action is taken, check that Application Discovery is receiving messages from the host. (See #8 in this section.)

Check that Application Discovery agent is authorized to exchange data with the CMS and that exchange is complete.

Click through the following HP Systems Insight Manager menus: ConfigureConfigure VSE Agents Check AD Agent States. Any status other than Connected indicates that a certificate exchange may be necessary.

See “Introduction” for completing the certificate exchange. The Application Discovery agent starts running (and begins sending data to the Application Discovery server) on completion of the certificate exchange.

Once this action is taken, check that Application Discovery is receiving messages from the host. (See #8 in this section.)

Check that the WBEM connection is working correctly on the managed node.

To check the status of the WBEM connection, do the following in Application Discovery user interface:

Check that Application Discovery is receiving messages from the host.

Check that the package is marked as 'visible' in Application Discovery.

Check that Application Discovery is showing that total packages and completed packages have the same value.

It is possible that certificate exchange has not been completed.

See Appendix B for instructions on completing the certificate exchange.. The Application Discovery agent starts running (and begins sending data to the Application Discovery server) on completion of the certificate exchange.

	Have you recently restored or removed and reinstalled the CMS? : A restore or removal of the central management server also removes the certificate recognition previously established between Application Discovery server on the CMS and Application Discovery agents on managed nodes. This relationship must be re-established when the CMS is reinstalled or restored by completing the Application Discovery certificate exchange.

Application Discovery may not be correctly configured.

Run vseinitconfig -a on the command line to correct the configuration of Application Discovery. (See also vseinitconfig(1M).)

To identify other configuration problems that may be affecting Application Discovery server, check the “Troubleshooting” notes in the VSE Management Software Help instructions, or use vseassist(1M).

Check that Application Discovery server is running on the CMS.

Type ps -elf | grep amgrserver.jar on the command line of the CMS. You should see a Java process running the Application Discovery server.

If you do not see this Java process, type /opt/amgr/bin/cms_start . You must be logged in as user 'root' on the CMS to initiate this command.

Check that Application Discovery server is running on the CMS.

Type ps -elf | grep amgrserver.jar on the command line of the CMS. You should see a Java process running the Application Discovery server.

If you do not see this Java process, type /opt/amgr/bin/cms_start . You must be logged in as user 'root' on the CMS to initiate this command.

Check that the host is known to Application Discovery.

Check that Application Discovery server is running on the CMS.

Type ps -elf | grep amgrserver.jar on the command line of the CMS. You should see a Java process running the Application Discovery server.

If you do not see this Java process, type /opt/amgr/bin/cms_start . You must be logged in as user 'root' on the CMS to initiate this command.

Check that the host is known to Application Discovery.

Check that the Application Discovery agent is running.

Click the following menu choices in HP Systems Insight Manager: Configure Configure VSE Agents Check AD Agent States . Follow the instructions for selecting hosts and checking agent state.

If the Application Discovery agent is installed, but is not running, click Configure Configure VSE Agents Start AD Agents and follow the instructions for selecting hosts and starting agents.

Check that Application Discovery agent is writing process maps for this workload on the managed system.

If you confirm that process maps are not being updated, you can try the following actions to get process maps working correctly.

Check that the workload is defined for this host.

A workload receives process maps only for the host or hosts for or on which it is deployed. To check that a workload is defined for a host, click the Workloads tab in Virtualization Manager. You may need to modify a workload to include this host or create a new workload for it. For help on this topic, see the Virtualization Manager Help reference.

Check to see if the workload is parked.

A parked workload does not generate process maps anywhere. Process maps that existed prior to parking the workload are deleted. See the discussion of “General Workload Properties ” in Virtualization Manager Help and the glossary for information about parked workloads.

Check to see that the application associated with the workload is currently running.

In Application Discovery, click the Applications tab. Then, under the Running tab, sort by host. (Click the 'Host' column header to toggle the list to sort in ascending or descending alphabetical order.) To rule out the possibility that the running application is hidden, click the drop-down menu above the 'Application Instances' to 'Show hidden apps'. If the application that you are looking for is not in this list, you must run the application so that it can be discovered.

Check that Application Discovery server is running on the CMS.

Type ps -elf | grep amgrserver.jar on the command line of the CMS. You should see a Java process running the Application Discovery server.

If you do not see this Java process, type /opt/amgr/bin/cms_start . You must be logged in as user 'root' on the CMS to initiate this command.

	NOTE: If none of these measures are sufficient, other underlying problems may be the cause. See also the suggestions in “Host Not Visible in Application Discovery Screens” that relate to communication between the Application Discovery server and the WBEM provider and between the WBEM provider and the Application Discovery agent.

Application Discovery might not be correctly configured.

Run vseinitconfig -a on the command line to correct the configuration of Application Discovery. (See also vseinitconfig(1M.)

To identify other configuration problems that might be affecting Application Discovery server, check the “Troubleshooting” notes in the VSE Management Software Help instructions, or use vseassist(1M).

	NOTE: Be aware that one possible cause for incorrect configuration is the case where installation and startup deviate from the documented process. In this situation, you might see the following error message: Application Discovery UI encountered an error: The UI and server are out of sync. If Application Discovery web application and Application Discovery server are not from the same installation version, you must reinstall Application Discovery before using vseinitconfig -a.

Check that Application Discovery server is running on the CMS.

Type ps -elf | grep amgrserver.jar on the command line of the CMS. You should see a Java process running the Application Discovery server.

If you do not see this Java process, type /opt/amgr/bin/cms_start . You must be logged in as user 'root' on the CMS to initiate this command.