HP Matrix Operating Environment Software manual Host not visible in Application Discovery screens

Page 42

See Table 3 (page 27) for a demonstration of the different results that you can expect when using the same executable and arguments in Application Discovery as compared to Global Workload Manager (gWLM).

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

“Processes unmatched by this template” table for a particular host.

“Processes unmatched by this template” table.

"Applications effected by this template" table. See Individual application template view in the Application Discovery Online Help.

Or, to see examples of working templates, click the following tabs: Admin/Config, then AD Templates. Click a template name to see its attributes.

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.

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” (page 42) and “Errors due to incompatibilities between different versions of Application Discovery agents and servers” (page 48) .

Host not visible in Application Discovery screens

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

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

To learn how to add a managed system to the system list, see “Setting up managed systems” in HP Systems Insight Manager Help Online Help.

2.Check that the managed systems (including virtual machines) have valid sign-in credentials defined in Systems Insight Manager.

3.Check that an Application Discovery agent is running on the managed host. To view the list of hosts running an Application Discovery agent, click the Admin/Config tab, and then the Agents tab. The Agents tab lists all discovered hosts running the Application Discovery agent.

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

a.Click the following tabs in Application Discovery: Admin/Config, then Discovery.

b.Find the column heading “Visible”. Hosts marked with 'Y' are currently visible in Application Discovery screens. Hosts marked with 'N' are hidden.

5.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.)

6.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.)

42 Troubleshooting

Image 42
Contents Application Discovery 7.2 User Guide Page Contents Troubleshooting Support and other resourcesDocumentation feedback Error messages Completing certificate exchangeConfiguring the Wbem provider password Glossary Index Key to event attributesPage Features of Application Discovery IntroductionIntroduction Components and concepts Application Discovery componentsUnderstand your current discovery state Refining Application DiscoveryHow discovery works Discovery ratioRefine discovery by creating application templates Understanding application templatesRefine discovery by checking agent state Warm-up ratioHow memory usage is calculated Understanding server resource consumptionUsed mem Page Starting the agent from the command line Procedures and examplesUsing System Insight Manager to start the agent Starting Application DiscoveryStopping the agent from the command line Reconfigure a running agent from the command lineUsing System Insight Manager to stop the AD agent Checking agent stateExplanation of agent states Adjusting the user interfaceWorking with data views Set screen data refresh intervalSet number of table rows Change the data viewSet color theme Sort data in view tablesFilter data in view tables Other controls available from right-clicking on a view tableNavigate between views Set visibility for hosts on Application Discovery screensSet visibility for matched applications Modifying the maximum size of an event list Set visibility for packages on Application Discovery screensSetting event attributes Setting data polling intervalIntroduction to event settings in Application Discovery Managing application templates Setting event severitySetting alert location Find an application templateChange application template values Create a new template Key to application template values Application identity and system scope fieldsUsr/sbin/biod Separation rule fields and their descriptions OSverUser scope Create an application template rule Aggregation rule fields and their descriptionsCreate a process aggregation rule Managing application templates Procedures and examples Managing application templates How to remove types from the aggregation rule Check unmatched processes to find application candidatesUnderstanding the tables that show unmatched processes Filling in the system scope fields using table data Filling in the aggregation rule 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 Troubleshooting Errors in installationData 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 Errors in Application Discovery user interface operation UI Unable to connect to servermessagesJava UI exception message displays To fix this error, do one of the following On the managed nodes, run the command Support and other resources How to contact HPSubscription service Information to collect before contacting HPDocuments HP authorized resellersRelated information ResourcesTypographic conventions Computer outputPage Documentation feedback Page Page Amgrd OptionsInstallation NodaemonAuthors Agentconfig Amx -cOpt/amgr/bin/agentconfig Agentconfig file Opt/amgr/bin/amgrd Key to event attributes Event typesEvent severity types Additional event types specific to Application DiscoveryEvent viewing locations Error messages Error messages seen when trying to logPage Completing certificate exchange from the command line Completing certificate exchangeIntroduction Completing certificate exchange Configuring the Wbem provider password Page Glossary ApplicationOperating system referred to as a guest OS See also system Wbem Agentwbemcleanup command IndexCmdline Path Pid scope Title
Related manuals
Manual 111 pages 21.04 Kb Manual 12 pages 7.25 Kb

Matrix Operating Environment Software specifications

HP Matrix Operating Environment (MOE) is an innovative software platform designed to deliver efficient management and orchestration of IT resources across physical, virtual, and cloud infrastructures. It provides a comprehensive solution for organizations that require a robust and flexible environment to manage their IT operations seamlessly.

One of the main features of HP MOE is its ability to optimize resource utilization by automating the provisioning and management of infrastructure components. This includes the ability to rapidly deploy servers, storage, and networking resources in a manner that meets the dynamic needs of modern businesses. This automation significantly reduces the time and effort required for manual configurations, enabling IT teams to focus on strategic initiatives rather than routine tasks.

The software offers a unified management interface that provides visibility into the entire IT environment. Users can monitor performance metrics, track resource allocation, and manage workflows through a single dashboard. This centralized control not only simplifies operations but also enhances decision-making capabilities by providing real-time insights into system health and performance.

Another critical characteristic of HP MOE is its support for both physical and virtual resources. The platform is designed to seamlessly integrate with existing infrastructure, making it easier for organizations to adopt virtualization and hybrid cloud strategies. Its compatibility with industry-standard hypervisors allows businesses to leverage their current investments while taking advantage of the benefits of virtualization.

HP MOE incorporates advanced technologies such as automation scripts, APIs, and tools for workload balancing. This technological backbone enables organizations to implement elasticity in their environments, allowing them to scale resources up or down based on demand. The software also supports a service-oriented architecture, facilitating integration with other enterprise applications and systems.

Security is a top priority in the design of HP MOE. The software provides robust security features that ensure data integrity and protect against unauthorized access. This includes role-based access controls, encryption, and compliance reporting, all of which contribute to a secure operating environment.

In summary, HP Matrix Operating Environment Software is a powerful solution that addresses the complexities of managing modern IT resources. Its key features include automation, unified management, support for physical and virtual environments, and strong security measures. With its ability to enhance efficiency and streamline operations, HP MOE is an essential tool for organizations looking to stay competitive in an increasingly digital landscape.