HP Matrix Operating Environment Software manual Data missing in Application Discovery screens

Page 43

7.Check that SSH is configured correctly on the managed node.

NOTE: This instruction applies only to 4.x agents; the 6.x and 7.x agents do not require SSH for secure communications with the Application Discovery server.

In this case, you may need to repair the 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:

a.Select Tools →Command Line Tools →UNIX/Linux →ls...

b.In the text field, type /tmp

If the contents in /tmp are visible, then SSH is working correctly.

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 Configure→Configure or Repair Agents fail on the target managed node.

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

1.Log on the managed node as user root.

2.# cd /.ssh /* <root_user_home_directory>/.ssh */

3.# rm * /* Erase all possible corrupted contents */

4. # ssh-keygen -b 2048 -t rsa /* Generate root ssh key */

5.# ps -elffgrep sshd /* Find the sshd PID */

6.# kill -1 <pid> /* Re-start sshd */

7.# mxagentconfig -a -n managed_node

8.# /opt/amgr/bin/agent_config -start

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

8.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:

a.Click the AD Agents tab.

b.Look for the WBEM Stat column in the 'Hosts/Agents' table. If the status message for WBEM is not 'OK', do the following:

Check that Systems Insight Manager CMS has an authorized logon with the managed system.

See Appendix E (page 69) to complete this authorization.

Alternatively, you can configure the managed system's WBEM authorization to trust the

CMS to perform a remote "root" WBEM user logon. Do this by clicking Configure

→Configure or Repair Agents. Make sure to mark the box for 'Configure WBEM client certificate authentication' before you run the tool.

Data missing in Application Discovery screens 43

Page 42 Page 44
Image 43
Page 42 Page 44
Contents Application Discovery 7.2 User Guide Page Contents Support and other resources TroubleshootingKey to event attributes Error messages Completing certificate exchangeConfiguring the Wbem provider password Glossary Index Documentation feedbackPage Introduction Features of Application DiscoveryIntroduction Application Discovery components Components and conceptsDiscovery ratio Refining Application DiscoveryHow discovery works Understand your current discovery stateWarm-up ratio Understanding application templatesRefine discovery by checking agent state Refine discovery by creating application templatesUnderstanding server resource consumption How memory usage is calculatedUsed mem Page Starting Application Discovery Procedures and examplesUsing System Insight Manager to start the agent Starting the agent from the command lineChecking agent state Reconfigure a running agent from the command lineUsing System Insight Manager to stop the AD agent Stopping the agent from the command lineSet screen data refresh interval Adjusting the user interfaceWorking with data views Explanation of agent statesSort data in view tables Change the data viewSet color theme Set number of table rowsOther controls available from right-clicking on a view table Filter data in view tablesSet visibility for hosts on Application Discovery screens Navigate between viewsSet visibility for matched applications Set visibility for packages on Application Discovery screens Modifying the maximum size of an event listSetting data polling interval Setting event attributesIntroduction to event settings in Application Discovery Find an application template Setting event severitySetting alert location Managing application templatesChange application template values Create a new template Application identity and system scope fields Key to application template valuesUsr/sbin/biod OSver Separation rule fields and their descriptionsUser scope Aggregation rule fields and their descriptions Create an application template ruleCreate a process aggregation rule Managing application templates Procedures and examples Managing application templates Check unmatched processes to find application candidates How to remove types from the aggregation ruleUnderstanding the tables that show unmatched processes Filling in the aggregation rule fields using table data Filling in the system scope fields using table dataFilling in the template separation rule fields Create an application workload in HP Matrix OE visualization Backing up Application Discovery files Page Errors in installation Troubleshooting Data missing in Application Discovery screens Applications not visible in Application Discovery screens Host not visible in Application Discovery screens Data missing in Application Discovery screens Packages not visible in Application Discovery screens Page Go to /var/opt/amgr/procmaps UI Unable to connect to servermessages Errors in Application Discovery user interface operationJava UI exception message displays To fix this error, do one of the following On the managed nodes, run the command Information to collect before contacting HP How to contact HPSubscription service Support and other resourcesResources HP authorized resellersRelated information DocumentsComputer output Typographic conventionsPage Documentation feedback Page Page Options AmgrdNodaemon InstallationAuthors Amx -c AgentconfigOpt/amgr/bin/agentconfig Agentconfig file Opt/amgr/bin/amgrd Event types Key to event attributesAdditional event types specific to Application Discovery Event severity typesEvent viewing locations Error messages seen when trying to log Error messagesPage Completing certificate exchange Completing certificate exchange from the command lineIntroduction Completing certificate exchange Configuring the Wbem provider password Page Application GlossaryOperating system referred to as a guest OS See also system Wbem Index Agentwbemcleanup commandCmdline Path Pid scope Title
Related manuals
Manual 111 pages 21.04 Kb Manual 12 pages 7.25 Kb
Top Page Image Contents