Keep in mind the following information:

•The 4.1, 6.x and 7.x agents do not require Application Discovery certificate exchange in order to secure server-agent communication between the agent and the server. In these versions, Application Discovery relies on standard authorizations that do not require an additional certificate exchange.

•The 4.0 agent does require Application Discovery certificate exchange. Therefore, certificate exchange must occur for the 6.x and 7.x server to communicate with a 4.0 agent.

NOTE: When you use the Insight managed system setup wizard to configure a managed system for the first time, the wizard will automatically install the 7.0 agent when Application Discovery is installed. Any managed nodes with 4.0 agents that are re-configured in the managed system setup wizard will also automatically be updated with the 7.0 agent. Version 4.1 agents are not automatically updated by the managed system setup wizard.

You can update a 4.1 agent by using the install option. While running through the steps in managed system setup wizard, you get a screen with two options “install” and “do not install”, by default the “do not install” option is chosen. If you select the “install” option the new agent will be installed.

If you find that you have version 4.0 agents within your computing network, and you suspect that there are problems in the agent-server communication, the following troubleshooting information may be helpful.

•If you are running a version 4.0 Application Discovery agent on a managed node (or on a CMS server on HP-UX), check that the Application Discovery agent certificate has been installed on the managed node (or CMS server).

Type the following on the command line of the system of concern:

#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.

See Appendix D (page 67). 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 older 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 .

•If you are running a version 4.0 Application Discovery agent on a managed node (or on a CMS server on HP-UX), check that the “Application Discovery agent accessible” event action is set to 'Show in AD'.

To check the settings for event actions, click the Admin/Config tab, then the Events tab.

•If you are updating Matrix Operating Environment in an environment that includes Linux managed nodes, check that the Application Discovery agent updated to the latest version on the Linux managed nodes.

You will know this step is necessary when starting the AD agents fails with the following error:

Missing directory /var/opt/amgr/ssl

To fix this error, do one of the following:

Errors due to incompatibilities between different versions of Application Discovery agents and servers 49