Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

 

1. Overview

The purpose of the Outside Discovery is to automatically discover, collect, and send information related the monitored system to Solution Manager. As of Solution Manager 7.1 SP 6, the Outside Discovery is able to collect following information:

  • Host: data related to Physical Host and Virtual Host (like operating system type, version, CPU, memory …)
  • Database: data related to installed database (like database type, version, …)
  • Microsoft Internet Information Services: data related to installed instance of Microsoft IIS (like .Net version, IIS Applications, IIS Sites…)

The Outside Discovery is an application of the Diagnostics Agent and it is is packaged inside the Agelet called DCC (agelet archive: sap.com~tc~smd~agent~application~e2edcc.ear).

The Outside Discovery process relies on the SAP Host Agent Web Service process for collecting all raw technical data related to monitored system.

The process is ready to push as soon as the running Diagnostics Agent gets connected to a Solution Manager system. Data are:

  • Collected from the SAP Host Agent Web Service.
  • Filtered and cached on the Agelet side.
  • Sent to a Java RMI object (SMD_DataEnrichment_Registrator) via a P4 connection.
  • Stored in the LMDB (AI_DIAGNOSTICS_DATA_ENRICHMENT package).

The following picture describes the basic architecture of the Outside Discovery:

(info) When the Diagnostics Agents on-the-fly feature is enabled in a host, only the SMDAgent of the Physical/Virtual host performs the Outside Discovery process. The Outside Discovery is disabled in the SMDAgents on-the-fly nodes to avoid duplicate information.

2. Prerequisites

The Outside Discovery process itself does not require any specific set-up in order to run, but it is required to meet some prerequisites. These requirements are described in the following step of the SOLMAN_SETUP:

  1. SOLMAN_SETUP
  2. System Preparation
  3. Step Prepare Outside Discovery

The activities described in step Prepare Outside Discovery must be performed for all the servers where the Outside Discovery process must run.

As mentioned in the previous section, the Outside Discovery relies in the SAP Host Agent to collect the information. One of the most important requirements of the Outside Discovery is the SAP Host Agent level and its configuration. The section below provides information about the SAP Host Agent requirements to run the Outside Discovery.

2.1. SAP Host Agent

All data discovered by the Outside Discovery process are collected from the SAP Host Agent installed on the physical host.

2.1.1. SAP Host Agent Version

The SAP Host Agent should have the correct version – the minimum required version is described in section 'Checking the SAP Host Agent Version' of the Diagnostics Agent Maintenance Procedures WIKI page. The SAP Host Agent release can be checked in the Agent Admin UI as follows:

  • Access the Agent Admin UI (http://<solman_host>:<JAVA_HTTP_Port>/smd/AgentAdmin)
  • Go to SAP Host Agent tab
  • Find the target host

The following picture shows how to check the SAP Host Agent release in the Agent Admin UI:

As general rule always have the SAP Host Agents up-to-date. The section 'Upgrading SAP Host Agent' of the Diagnostics Agent Maintenance Procedures WIKI page contains information about how to update the SAP Host Agent.

2.1.2. SAP Host Agent Porttype

The SAP Host Agent provides a Web Service access to some subservices, also called Porttypes. The SAP Host Agent should be configured in order to expose these Porttypes to the Web Service.

The configuration of the available services is defined in the SAP Host Agent file “host_profile” located at:

  • On UNIX:
    • /usr/sap/hostctrl/exe/
  • On Windows:
    • C:\Program Files\SAP\hostctrl\exe

The following porttypes are mandatory for the Outside Discovery process:

  • SAPHostControl
  • SAPOscol

The PortTypes configuration is done in property  service/porttypes of the host_profile. Ensure that the property service/porttypes contains the PortTypes SAPHostControl and SAPOscol in its value. For example:

  • service/porttypes = SAPHostControl NwaManagement SAPCCMS SAPOscol

The picture below shows an example of the PortTypes configured in the host_profile of a Windows Server.

2.1.3. SAP Host Agent Trusted Connection

Some methods within the SAP Host Agent are restricted. In order to allow the Diagnostics Agent to access protected Web Services from the SAP Host Agent a trusted connection is necessary between the 2 parties. The Trusted connection is also defined in the SAP Host Agent file host_profile.

To configure the Trusted Connection between the Diagnostics Agents and the SAP Host Agent, the Diagnostics Agents OS user must be added in property service/admin_users of the host_profile. The steps to perform this configuration are:

  • Open the following file:
    • On UNIX: /usr/sap/hostctrl/exe/host_profile
    • On Windows:C:\Program Files\SAP\hostctrl\exe\host_profile
  • Check/Add the following parameter: service/admin_users
  • Add the SMDAgent OS user admin users as parameter values separated by a blank space (for example service/admin_users = <user1> <user2> <user3>): For all Diagnostics agents installed on the various virtual hosts of the physical hosts on which the SAP host agent is running, add the <sid>adm user as parameter, like in the example below.
    • On Unix : service/admin_users = <DASID>adm <DASID2>adm
    • On Windows: service/admin_users = domain\SAPService<DASID> domain\SAPService<DASID2>

In the above example <DASID> & <DASID2> stand for the Diagnostics Agent System IDs of 2 Diagnostics Agents that would have been installed on the same physical host. The list of OS users have to be separated by a <space> character.

  • Save.
  • Restart SAP Host Agent with:
    • On UNIX: "/usr/sap/hostctrl/exe/saphostexec -restart"
    • On Windows: "C:\Program Files\SAP\hostctrl\exe\saphostexec.exe -restart"

The picture below shows an example of the Trusted Connection configured in the host_profile of a Windows Server.

2.2. Diagnostics Agent

In order to start the Outside Discovery process, the Diagnostics Agent must be connected to the Solution Manager System. The connection between the Diagnostics Agents and the Solution Manager system is configured either during the installation of the Diagnostics Agents or using the smdsetup script.

To connect the Diagnostics Agents to the SAP Solution Manager using the smdsetup script refer to KBA 1907909. The KBA 1907909 contains a video showing exactly how to perform this configuration.

  • 1907909 - How to connect Diagnostics Agent to Solution Manager system directly by using smdsetup script [VIDEO]

For information about the Diagnostics Agents installation, refer to the Diagnostics Agents WIKI page.

3. User Guide

As soon as the Diagnostics Agent gets connected to a Solution Manager system, the Outside Discovery Agelet starts running.

The Outside Discovery Agelet contains 3 different jobs:

  • Host Discovery: this job is retrieving data from physical and virtual host on the monitored system.
  • Database Discovery: this job is retrieving data for all installed database on the monitored host.
  • IIS Discovery: this job is retrieving data for installed Microsoft IIS on monitored host.
(warning) The Host Discovery process is the master process of the Outside Discovery Agelet. Database Discovery and IIS Discovery processes are only started if Host Discovery has been able to successfully push and create the host entity in the Solution Manager.

 

The status of the Outside Discovery can be checked in the Landscape Browser application in the SAP Solution Manager. The Landscape Browser can be accessed using the following URL:

3.1. Host Discovery

The Host Discovery (aka PhysicalHostPushJob) is the master process and gets started first. The Host Discovery is retrieving the following data from the monitored system:

  • Physical Host – this includes:
    • Operating System Information
    • Virtualized Solution used.
  • All Logical hosts defined on the monitored Physical Host.

3.1.1.  Host Details

Hosts associated to Technical Systems are enriched by the Outside Discovery process, the details of the host can be checked in the Landscape Browser application. To access the Landscape Browser, use the following URL:

After access the Landscape Browser, search for the target system and find the host in the list. The following picture describes a host of an ABAP System enriched by the Outside Discovery:

As shown in the picture above, in the Landscape Browser it is possible to see the Operating System version, the IP, FQDN and host type.

In the LMDB it is also possible to see the host details that are enriched by the Outside Discovery process. The steps to find them are:

  1. Transaction LMDB;
  2. Opens the LMDB definition of the target Technical System;
  3. Go to Hosts in the left pane;

In the LMDB it is possible to see details like Operating System version, the IP, FQDN, host type and CPU type.

The complete list of host data is available in the LMDB as follows:

  1. Transaction LMDB;
  2. Go to Hosts tab;
  3. Open the definition of the target hos;
  4. Click on 'Details' button.
  5. go to Properties tab

The following picture shows the complete list of landscape properties for a host.

3.1.2. How to Check Outside Discovery Status for the Host

The Outside Discovery runtime status for the host can be checked in the Landscape Browser as follows:

  1. Access the Landscape Browser using the URL:
  2. Go to Hosts tab
  3. Find and select the target host
  4. Expand the 'More Details'
  5. Check column Status

The following picture describes how to check the Outside Discovery status:

In case of errors in the Outside Discovery status, check the Troubleshooting section for the most common problems and solutions.

3.1.3. Physical Host information retrieved by the Outside Discovery

Following data are retrieved for the Physical Host:

Physical Host fieldsDescription
NameShort name of the physical host
Full Host NameFull host name of the physical host
IP AddressIP Address
Virtualized SolutionIdentify if the physical host is running inside a virtualized solution.

For the Physical Host, the Outside Discovery also retrieves the following Operating System information:

Operating System dataExample
OpSysUnameWindows NT
OpSysWINDOWS_X86_32
OpSysRelease5.2
OsSysBits32
OpSysCategoryWindows NT
OpSysReleaseNameWindows NT 5.2
ManufacturerPC Vendor
PhysicalRAMinMB3904
VirtualRAMinMB12276
NumberofCPUs4
CPURate2799
CPUCache 
CPUTypeIntel 801586 (Mod 2 Step 9)

3.1.4.  Logical Host infomration retrieved by the Outside Discovery

The Outside Discovery process is retrieving all logical hosts from the installed SAP product instance: SAP J2EE Engine, Diagnostics Agent, etc. The following information is retrieved for Logical Hosts.

Logical Host fieldsDescription
NameShort name of the logical host

Full Host Name

Full host name of the logical host
IP AddressIP Address

(warning) The logical host inherits from the same operating system data as its physical host.

  • Logical Hosts of SAP Instances

The Full Host Name (FQDN) for the Logical Hosts of SAP Instances is retrieved from property SAPLOCALHOSTFULL=<FQDN> of the SAP Profile. If the Fully Qualified Domain Name is not reported correctly, then the property SAPLOCALHOSTFULL=<FQDN> in the SAP Profile should be modified manually in order to match the network configuration. Refer to note 962955 for information the usage of Logical Hosts and parameter SAPLOCALHOSTFULL.

962955 - Use of virtual or logical TCP/IP host names

  • Logical Hosts of Non SAP Instances

For non-SAP instances, logical hosts are retrieved from the Diagnostics Agent. This means installing a Diagnostics Agent on the logical host is necessary in order to get the logical host reported correctly to LMDB by Outside Discovery. This is usually part of the installation when enabling the monitoring capabilities of the 3rd Party Component.

The important point is that the host, FQDN and IP should be the one defined for the logical host.

3.1.5.  How to Check Host Type

  1. Access the Landscape Browser using the URL:
  2. Go to Hosts tab
  3. Find and select the target host
  4. Expand the 'More Details'
  5. Check column 'Type'

The picture below shows where the information is available in the Landscape Browser.

If the Host Type is 'Unknown', it indicates that the Outside Discovery for the host haven't provided the information yet. Refer to section 'How to Check Outside Discovery Status for the Host' to check if the Outside Discovery for the host is running without errors.

3.2. Database Discovery

Database Discovery (aka DatabaseInfoPushJob) is started only after a successful push of the Host Discovery process. Database Discovery is retrieving the following data from the monitored system:

  • List of databases installed on the monitored host.
  • Database type, name and additional properties like vendor and version.

The databases will be created automatically by the Outside Discovery in the LMDB as of SAP Solution Manager 7.10 SP12. With Solman 7.10 SP12, the SAP Note 2062076 must be applied in the SAP Solution Manager system.

2062076 - Outside Discovery does not create a new database

3.2.1. Database Details

The databases are registered and enriched by the Outside Discovery process, the details of the database can be checked in the Landscape Browser application. To access the Landscape Browser, use the following URL:

After access the Landscape Browser, search for the target system and find the database in the list. The following picture describes a database of an ABAP System enriched by the Outside Discovery:

3.2.2. How to check the Outside Discovery status for the Database

The Outside Discovery runtime status for the host can be checked in the Landscape Browser as follows:

  1. Access the Landscape Browser using the URL:
  2. Go to Database tab
  3. Find and select the target host
  4. Expand the 'More Details'
  5. Check column Status

The following picture describes how to check the Outside Discovery status:

In case of errors in the Outside Discovery status, check the Troubleshooting section for the most common problems and solutions.

3.2.3. Database discovery process

To discover the databases within a server, the Outside Discovery uses the SAP Host Agent command ListDatabases. The database that needs to be registered in the SAP Solution Manager system must be described in the output of the ListDatabases command. The command can be executed as follows:

  •  On Windows:

C:\Program Files\SAP\hostctrl\exe\saphostctrl.exe -function ListDatabases

  •  On UNIX:

/usr/sap/hostctrl/exe/saphostctrl -function ListDatabases

If the command ListDatabases fails when executed at OS level, it indicates an issue with the SAP Host Agent. Check the SAP Host Agent logs for more details about the error. If needed an incident might be created in BC-CCM-HAG to check the error with ListDatabases command. The Outside Discovery for the database will not work if the ListDatabases command fails.

If the command ListDatabases works correctly, but the Database Status is shown as error in the command then the database will not be created in the LMDB. In this case, the Outside Discovery will send the database information to the Solution Manager, however if the Solman ABAP code sees the Status "Error", then the database information is simply ignored. The following table shows an example of ListDatabases when the status is error:

/usr/sap/hostctrl/exe/saphostctrl -function ListDatabases

----------------------------------------------------------------------

Instance name: SOL, Hostname: solsapdb, Vendor: SYB, Type: syb, Release: 15.7.0.101

  Database name: ERP, Status: Error

  Database name: XIS, Status: Error

  Database name: solsap, Status: Error

  Database name: solsap2, Status: Error

  Database name: solsap3, Status: Error

----------------------------------------------------------------------

(lightbulb) To have a successfull discovery of the database ensure that the ListDatabases command works fine and that the DB is described in the output with a 'Running' status.

3.3. Microsoft IIS Discovery

IIS Discovery (aka IISInfoPushJob) is started only after a successful push of the Host Discovery process. IIS Discovery is only running on the operating system “Windows”. The process is stopped if no IIS instance is found on the monitored system. IIS Discovery is retrieving the following data from the monitored system:

  • IIS instance automatically created in LMDB
  • IIS version (supported versions are IIS 6 and IIS 7)
  • All installed .Net versions
  • All IIS Applications and IIS Pools

3.3.1. Microsoft IIS Details

The Outside Discovery runtime status for the host can be checked in the Landscape Browser as follows:

  1. Access the Landscape Browser using the URL:
  2. Go to Tehnical Systems tab
  3. Search for *MSIISINST* to list the Internet Information Services systems

The following picture shows the IIS details in the Landscape Browser:

The IIS systems can be found in the LMDB itself as follows:

  1. LMDB
  2. Technical Systems tab
  3. Select type Microsoft Internet Information Services
  4. Select target system

The following picture shows the Overview tab in the LMDB for a IIS System, the IIS version is one of the information available in the definition.

The LMDB also provides information about the IIS Applications:

 

(lightbulb) In case it is not required to register the IIS of a Windows Server in the LMDB of the Solman, then it is possible to disable the Outside Discovery for the IIS. Refer to KBA 1860100 for more information about how to disable the Outside Discovery for the IIS.

1860100 - Internet Information Services (IIS) related entries in Managed systems configuration - Solution Manager 7.1

4. Troubleshooting

4.1 Guided Answer for Outside Discovery

To troubleshoot issues with the Outside Discovery, refer to the Guided Answer for Outside Discovery.

2468030 - How to troubleshoot Outside Discovery issues - Solution Manager 7.1 / 7.2

4.2. Check Outside Discovery Status

4.3. Outside Discovery Log Files

The Outside Discovery has the following distinct log files:

Outside Discovery jobLog File NameDescription
Host Discoverye2edcc_host.*.logLog file will provide details about the outside discovery process for the hosts.
Database Discoverye2edcc_db.*.logLog file will provide details about the outside discovery process for the database.
IIS Discoverye2edcc_iis.*.logLog file will provide details about the outside discovery process for the IIS Systems.

The log files can be found in the 'log' folder of the Diagnostics Agent:

  • <drive:>\usr\sap\<SID>\SMDA<XX>\SMDAgent\log

It is possible to download the Outside Discovery log files in the Agent Admin UI as follows.

  • SM_WORKCENTER
  • SAP Solution Manager Administration
  • Infrastructure
  • Framework
  • Agent Framework
  • Agents
  • All Agents, in this step the Agent Admin UI is accessed.
  • Go to Agent Log Viewer tab in the Agent Admin UI
  • Select the target Diagnostics Agent in 'Select an Agent'.
  • Click on 'Download logs'

The following picture shows the download place for the Diagnostics Agent logs.

4.3.2 Increase the Outside Discovery Log Level to Debug

To see the details retrieved by the Outside Discovery for the host, database or IIS System it is required to increase the corresponding log level to 'Debug'. The Outside Discovery logs will show the details only in level debug. To check/change the Log Level for the Outside Discovery log files, you need to access the Agent Log Viewer as shown in the previous section and then use the 'Log Configuration' to change the Log Level. The following picture describes how to change the Log Level:

(lightbulb) After increase the desired Outside Discovery Log Level to Debug, wait 15 minutes for the next Outside Discovery execution, or refer to KBA 1830735 to trigger the Outside Discovery process manually.

1830735 - How to manually trigger Outside Discovery

 

4.3.3 Agent Error Monitoring Tab in the Agent Administration UI

It is also possible to check the Outside Discovery errors in the Agent Admin UI, tab 'Agent Error Monitoring', the steps to access it are:

  • SM_WORKCENTER
  • SAP Solution Manager Administration
  • Infrastructure
  • Framework
  • Agent Framework
  • Agents
  • All Agents, in this step the Agent Admin UI is accessed.
  • Go to Tab Agent Error Monitoring

In the left menu, select the target Diagnostics Agents to be analyzed, the filter for the relevant location in the log entries table (right pane). The following locations are available for filtering the Outside Discovery jobs:

Outside Discovery JobLocation
Host Discoverycom.sap.smd.e2edcc.host
Database Discoverycom.sap.smd.e2edcc.db
IIS Discoverycom.sap.smd.e2edcc.iis

The following picture describes how to check the Outside Discovery logs for the Host Discovery in the Agent Error Monitoring of the Agent Administration.

4.4. Landscape API logs and traces

In the SAP Solution Manager it is possible to activate the Landscape API logs to check details of the Outside Discovery information retrieved. The Landscape API logs are available in the Landscape Browser. The steps to find them are:

  1. Access the Landscape Browser using the URL:
  2. Go to Administration tab
  3. Go to Unified Logs/Traces

The following picture describes the Landscape API logs:

4.4.1 Activate Landscape API logs and traces

The Landscape API logs are not collected by default, to check the Outside Discovery information in the Landscape API logs it is required to enable the logging first. The steps to active the Landscape API logs for the Outside Discovery are:

  1. Access the Landscape Browser using the URL:
  2. Go to Administration tab
  3. Go to Unified Config.
  4. Select user SMD_RFC     (info) The Landscape API logs are user dependant. The Outside Discovery process is executed by user SMD_RFC.
  5. Select Enable Logging and Level Debug
  6. Save

The following picture describes how to activate the Landscape API logs for the Outside Discovery:

4.4.2 Check Landscape API logs and traces

After activate the Landscape API logs, it is possible to check the Landscape API logs collected in tab 'Unified Logs/Traces' of the Landscape Browser. The Landscape API Logs contains information about changes in the landscape, the Outside Discovery is not the only one application which performs such changes. The following picture shows an example for the logs.

The logs for the Outside Discovery will start with message 'Push <object>', so to filter only for the Outside Discovery entries search for 'Push*' as shown in the picture above.

(lightbulb) After activate the Landscape API logs, it is required to wait the Outside Discovery run or trigger it manually as shown in KBA 1830735.

4.4.3 Disable/Enable Landscape API Cache

The Landscape API has a cache that in some cases might be obsolete or contains incorrect information from the Landscape Management Database (LMDB). If the Outside Discovery status for the host or database is correct, but the Outside Discovery is not being updated in the Landscape, try to disable the Landscape API cache to check if the cache is up-to-date. The Landscape API cache can be disabled in the Landscape Browser as follows:

  1. Access the Landscape Browser using the URL:
  2. Go to Administration tab
  3. Go to Landscape Config. tab
  4. Select the desired user and clear the option 'Enabled' in the Cache section.

The following picture describes where and how to disable the Landscape cache.

(lightbulb) Disable the Landscape Cache for the LoggedOn User and also for user SMD_RFC to perform tests.

In case you find out problems with the Landscape API cache, the note 1662466  contains information about how to manually update the Landscape API cache.

1662466 - Landscape API cache is not up-to-date

4.5 Diagnostics Agent Support Tool

The Diagnostics Agent Support Tool can be used to get more details about the Outside Discovery application, the following checks can be performed:

  • Java RMI object registration - SMD_DataEnrichment_Registrator
  • Discovery jobs statistics

The steps to access the Agent Support Tool are the following.

  • SM_WORKCENTER
  • SAP Solution Manager Administration
  • Infrastructure
  • Framework
  • Agent Framework
  • Agents
  • All Agents, in this step the Agent Admin UI is accessed.
  • Go to Advanced Settings tab
  • Click on 'Agent Support Tool' to open the application.

4.5.1 SMD Server Analysis View

In the Agent Support Tool, go to tab SMD Server Analysis and check section 'SMD JNDI objects auto-registered', ensure that the JAVA RMI object SMD_DataEnrichment_Registrator is registered as shown in the picture below.

(warning) If the object is not registered correctly, use the “Objects Reinitialization” button to recreate all objects.

(info) Roles SAP_J2EE_ADMIN and SAP_RCA_AGT_ADM are required to access the Agent Support Tool.

4.5.2 Discovery jobs statistics

In the Agent Support Tool, go to tab Diagnostics Agent Runtime to get statistics about the Outside Discovery Jobs. For this, select the target Diagnostics Agents and check tab Agent Monitoring to see the details. Search for the entries with namespace Outside Discovery. The picture below describes this check:

The Agent Runtime provide the following statistics about the Outside Discovery Jobs.

  • Outside Discovery jobs running on the Diagnostics Agent
  • Average execution time per jobs
  • Total number of executions
  • Last execution date
  • Number of exceptions
  • Number of time-out exceptions.

4.6. Troubleshooting Roadmap

In order to troubleshoot a specific Outside Discovery process, the following roadmap can be used – this applies to any discovery job running on a specific host.

There is also a "Guided Answer" troubleshooting tool available for Outside Discovery: https://gad5158842f.us2.hana.ondemand.com/dtp/viewer/#/tree/1094/actions/12233

 

ToolCheckSection Reference
Landscape Browser
  • Check host status for the application area “Data Enrichment”.
  • The status should be green as the host discovery process is the master process.

3.1.2 - Check Outside Discovery status for the host

3.2..2 - Check Outside Discovery status for DB

SAP Solution Manager

Administration -> Infrastructure /

Logs and Trace view

  • Use the search string “push*<hostname>” to check logs for each discovery job.

  • If an exception is found then the problem is located in the persist process.

4.3. Landscape API logs and traces

Diagnostics Agent Administration /

Agent Error Monitoring Tab

  • Select the relevant Diagnostics Agent
  • If an exception is found then the problem is located in the discovery process.
4.4 Diagnostics Agent Support Tool

Diagnostics Agent Administration /

Agent Log Viewer

  • Select the relevant Diagnostics Agent and set the relevant log file to debug
  • The log file should display all actions related to the discovery process
4.2. Outside Discovery Log Files

 

5) Common Problems and Known Errors

5.1) Diagnostics Agent Is Not Connected to the Solution Manager

If the Outside Discovery status is grey, or you find out that the Outside Discovery last update occurred a long time ago. Check if whether the Diagnostics Agents of the affected host or database is connected to the SAP Solution Manager system. Refer to section Diagnostics Agent of this WIKI for more information. The Outside Discovery status might show the following error in this case:

(error) Diagnostics agent is not connected to solution manager server, connection status: CONNECTING Diagnostics agent is not connected to solution manager server, connection status: LAST_REGISTRATION_ON_ERROR

The message above might also occurs if the Java RMI oject SMD_DataEnrichment_Registrator is not available. Check section SMD Server Analysis View of this WIKI if the SMDAgent is correctly connected to the Solution Manager and the error above is shown.

5.2) Step 'Check prerequisites' of the Managed System Configuration fails due to missing Software Component Version for the Operating System

(error) Error

 When running the Managed System Configuration, the following error is displayed:

The definition of Technical System SYS~XXX is not correct: “SYS~XXX”: Operating System “<Any operating system> of Host “hostname” must have at least one Software Component Version.

(info) Description

The Software Component Version of the operating system is mandatory for some set-up steps.

This information is retrieved by the Host Outside Discovery Process. All prerequisite actions concerning the Outside Discovery process should be completed before running the set-up.

(tick) Additional Checks

1) Ensure that the SAP Host Agent is up-to-date and that that the Trusted Connection and Port Types are correctly configured. Refer to section SAP Host Agent of this WIKI.

2) Ensure that the Outside Discovery status for the host is green, refer to section 'How to Check Outside Discovery Status for the Host'. In case of errors in the Outside Discovery Status, search for solution in KBAs or in this WIKI.

3) If not errors are found in the Outside Discovery status then refer to section '4.3.1 Activate Landscape API logs and traces' of this WIKI page, enable the Landscape API logs and trigger the Outside Discovery process manually as shown in the mentioned section. Finally check the Landscape Logs to search for errors.

4) If no 'Push <target_host>' entry has been found for the affected host in the Landscape API Logs then refer to section '4.2.2 Increase the Outside Discovery Log Level to Debug' of this WIKI, increase the Outside Discovery log for the host to Debug and trigger the Outside Discovery process manually as shown in the mentioned section. Finally check the corresponding log file to search for errors.

Know Problems and Solutions:

2313988 - Outside Discovery: Software Component Version for host is missing due to error 'Software Component not found' for HPUX_IA64

2103078 - Outside Discovery: Software Component Version for host is missing due to error 'Software Component not found' for LINUX_X86_64~SLES

 

5.3) Step 'Check prerequisites' of the Managed System Configuration fails due to missing Software Component Version for the Database

(error) Error

 When running the Managed System Configuration, the following error is displayed: 

The definition of Technical System '<SID~TYPE>' is not correct: '<SID~TYPE>': Database '<SID>' must have one Software Component Version.

(info) Description

The Software Component Version of the database system is mandatory for some set-up steps.

This information is retrieved by the Host Outside Discovery Process. All prerequisite actions concerning the Outside Discovery process should be completed before running the set-up.

(tick) Additional Checks

1) Ensure that the SAP Host Agent is up-to-date and that that the Trusted Connection and Port Types are correctly configured. Refer to section SAP Host Agent of this WIKI.

2) Ensure that the Outside Discovery status for the database is green, refer to section 'How to Check Outside Discovery Status for the Database'. In case of errors in the Outside Discovery Status, check if the solution is described in this WIKI page.

3) Refer to section 'Database discovery process' and check the results of the SAP Host Agent command ListDatabases. Ensure that the affected DB is listed in this command and that the DB status is 'Running'. If the DB is not listed, or the DB status is not running open an incident in BC-CCM-HAG team.

3) If not errors are found in the Outside Discovery status then refer to section '4.3.1 Activate Landscape API logs and traces' of this WIKI page, enable the Landscape API logs and trigger the Outside Discovery process manually as shown in the mentioned section. Finally check the Landscape Logs to search for errors.

4) If no 'Push <target_database>' entry has been found for the affected host in the Landscape API Logs then refer to section '4.2.2 Increase the Outside Discovery Log Level to Debug' of this WIKI, increase the Outside Discovery log for the database to Debug and trigger the Outside Discovery process manually as shown in the mentioned section. Finally check the corresponding log file to search for errors.

5.4) Error An exception occurred during the execution of the function 'FM_DIAGLS_PUSH_PHYSICAL_HOST'

(error) Error

java.rmi.RemoteException:RfcExecutionException; nested exception is: com.sap.sup.admin.abap.rfc.exception.RfcExecutionException:An exception occured during the execution of the function 'FM_DIAGLS_PUSH_PHYSICAL_HOST': DBIF_RTAB_SQL_ERROR > com.sap.mw.jco.JCO$Exception:SQL error -964 when accessing table VBMOD. <MiddlewareJRfc.java:516:g

(info) Description

An error occurs during the communication between the SMD_DataEnrichment_Registrator and the persistence Function Module in ABAP (package AI_DIAGNOSTICS_DATA_ENRICHMENT).

This is a global exception from the AI_DIAGNOSTICS_DATA_ENRICHMENT package and should be resolved in the Solution Manager ABAP stack.

(tick) Additional Checks

  • Check the SOLMANDIAG destination between the SAP AS Java and the ABAP stack.
  • Check ST22 dumps for additional information

5.5) Exception while parsing SapOsCol Data … No data allowed here

(error) Error

com.sap.smd.agent.plugins.dcc.exc.SapOsColParsingException:Exception while parsing SapOsCol Data. > com.sap.engine.lib.xml.parser.NestedSAXParseException:Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here(:main:, row:951, col:1) > com.sap.engine.lib.xml.parser.ParserException:XMLParser: No data allowed here (:main:, row:951, col:1) <XMLParser.java:2509:scanMisc()>

(info) Description

This exception occurs when the Host Discovery process is trying to parse SAPOsCol data retrieved from the SAP Host Agent.

In some situation the SAP Host Agent creates the SAPosCol.xml file partially before sending it to the Web Service.

(tick) Solution

Apply SAP Note 1587142 – SAPOscol WS Returns malformed XML response.

5.6) Exception while parsing SapOsCol Data … Parsing an empty source

(error) Error

 com.sap.smd.agent.plugins.dcc.exc.SapOsColParsingException:Exception while parsing SapOsCol Data. > java.io.IOException:Parsing an empty source. Root element expected! <XMLParser.java:2885:onEncodedDataReaderEOF()>

(info) Description

 SAP Host Agent Web Service is returning an empty SAPosCol.xml file.

(tick) Additional Checks

 SAP Host Agent log files should be analyzed in order to identify the SAP Host Agent issue.

5.7) Failed to open HW file

(error) Error

 Failed to open HW file. <MimeHttpBinding.java:747:buildFaultException()>                                                                                                                                                                                   

(info) Description

 This exception occurs when the SAP Host Agent process (Porttype SAPOsCol) is not able to provide the SAPosCol.xml file

(tick) Additional Checks

 SAP Host Agent log files should be analyzed in order to identify the SAP Host Agent’s exception.

5.8) Error CIM Request EnumerateInstances for classes Application failed: … : Provider load failure

(error) Error

 java.rmi.RemoteException:Webservice invocation error occured on stub com.sap.smd.agent.wsclients.saphostcontrol.SAPHostControlStub@680a68e9; nested exception is: javax.xml.rpc.soap.SOAPFaultException: CIM Request EnumerateInstances for classes Application failed: EnumerateInstances for Application failed: Provider load failure >

(info) Description

 The issue is the restriction done by IIS 7.0 on Windows 2008 and higher while discovering IIS Applications in the WMI namespace. Additional information is available at http://learn.iis.net/page.aspx/162/managing-sites-with-iis-7039s-wmi-provider/.
You must be an administrator to connect to the Web Administration WMI namespace. This means that you are logged in as one of the following:

  • The built-in Administrator account on Windows Server 2008
  • A member of the Administrators group and you have disabled User Account Control (UAC)
  • A member of the Administrators group and UAC is enabled.

(tick) Additional Checks

Add the user sapadm to the Local Administrator Groups.

5.9) Error GetObject ADSi Object IIS://localhost/W3SVC failed: Error : Access is denied

(error) Error

java.rmi.RemoteException:Webservice invocation error occured on stub com.sap.smd.agent.wsclients.saphostcontrol.SAPHostControlStub@16e3879; nested exception is: javax.xml.rpc.soap.SOAPFaultException: GetObject ADSi Object IIS://localhost/W3SVC failed: Error : Access is denied.

(info) Description

The SAP Host Agent user does not have authorization to access the ADSi IIS object.

(tick) Additional Checks

Add the user sapadm to the Local Administrators group.

5.10) Error java.net.SocketTimeoutException: Read timed out

(error) Error

java.rmi.RemoteException:Service call exception; nested exception is: java.net.SocketTimeoutException: Read timed out > java.net.SocketTimeoutException:Read timed out <SocketInputStream.java:-2:socketRead0()>

(info) Description

A time-out exception occurred while accessing one of the SAP Host Agent Web Service methods.

(tick) Additional Checks

SAP Host Agent log files should be analyzed in order to identify a SAP Host Agent performance or read issue.

5.11) Error Timeout waiting for saposcol answer

(error) Error

Timeout waiting for saposcol answer. <MimeHttpBinding.java:747:buildFaultException()>                                                                                                                                                      

(info) Description

A time-out exception occurred while accessing the SAP Host Agent Web Service (Porttype SAPOsCol)

(tick) Additional Checks

SAP Host Agent log files should be analyzed in order to identify SAP Host Agent performance or read issues.

5.12) Error to perform http request cause … Socket output stream shutdown by peer

(error) Error

 java.net.SocketException: Socket output stream shutdown by peer. > java.net.SocketException:Socket output stream shutdown by peer. <Response.java:481:initialize()>

(info) Description

The SAP Host Agent has closed the communication channel with the Diagnostics Agent.

(tick) Additional Checks

SAP Host Agent log files should be analyzed in order to identify SAP Host Agent performance or read issues.

5.13) Error Unable to open connection to host "localhost:1128". The host is down or unavailable

(error) Error

java.rmi.RemoteException:Error to perform http request cause by java.io.IOException: Unable to open connection to host "localhost:1128". The host is down or unavailable...;

(info) Description

The SAP Host Agent is down or unaccessible.

(tick) Additional Checks

Please check that SAP Host Agent is running correctly.

5.14) Error Cannot established a trusted connection to SAP host agent webservice

(error) Error

Cannot established a trusted connection to SAP host agent webservice. (SAP Host agent version installed doesn't support trusted connection method) <SAPHostAgentTrustedConnectionConfigurator.java:117:setupTrustedConnection()>

(info) Description

SAP Host Agent does not support the trusted connection, or the trusted connection is not correctly configured.

(tick) Solution

Ensure that the SAP Host Agent is up-to-date, and the configuration of the Trusted Connection is correctly performed. Refer to section SAP Host Agent of this WIKI.

5.15) Error Webservice port type not enabled

(error) Error

Webservice port type not enabled <MimeHttpBinding.java:747:buildFaultException()>

(info) Description

One of the service porttypes of the SAP Host Agent is unavailable or not set up correctly.

(tick) Solution

Ensure that the SAP Host Agent is up-to-date, and the configuration of the Port Types is correctly performed. Refer to section SAP Host Agent of this WIKI.                                                           

5.16) Error Webservice invocation error occurred … Generic error

(error) Error

java.rmi.RemoteException:Webservice invocation error occured on stub com.sap.smd.agent.wsclients.saphostcontrol.SAPHostControlStub@46b8c77f; nested exception is: javax.xml.rpc.soap.SOAPFaultException: Generic error. Check the trace file C:\Program Files\SAP\hostctrl\work\dev_sapdbctrl for more details. Increasing the trace level may provide further details. > javax.xml.rpc.soap.SOAPFaultException:Generic error. Check the trace file C:\Program Files\SAP\hostctrl\work\dev_sapdbctrl for more details.

(info) Description

Generic exception in the SAP Host Agent process

(tick) Additional Checks

SAP Host Agent log files should be analyzed in order to identify SAP Host Agent performance or read issues.

5.17) ABAP Dumps of type UNCAUGHT_EXCEPTION and exception CX_DIAGLS_CANNOT_CREATE_REF caused by program CL_DIAGLS_BASE_LANDSCAPE

(error) Error

The SAP Solution Manager frequent ABAP Dumps with the following details in transaction ST22:

Category                             ABAP Programming Error   

Runtime Errors                       UNCAUGHT_EXCEPTION       

Except.                              CX_DIAGLS_CANNOT_CREATE_REF

ABAP Program                         CL_DIAGLS_BASE_LANDSCAPE======CP

Application Component                 SV-SMG-LDB

 

(tick) Solution

Check KBA 2315917.

2315917 - ABAP Dumps of type UNCAUGHT_EXCEPTION and exception CX_DIAGLS_CANNOT_CREATE_REF caused by program CL_DIAGLS_BASE_LANDSCAPE

6) FQDN and IP Problems

The Outside Discovery is responsible to enrich the LMDB information with the FQDN and IP for the hosts discovered. Refer to this section in case you have problems with the IP or FQDN values in the LMDB definition.

(lightbulb) The configuration of the FQDN and IP sometimes depend on the Host type, distinct configurations need to be checked if the affected host is Physical/Virtual or Logical. Check in the Landscape Browser application the Host Type before proceed with the checks below. The steps to check the Host Type are described in section 'How to Check Host Type'.

6.1) Physical Host

A physical host is identified by a unique identifier: short name. This short name is provided by the SAP Host Agent process. There is a one to one relation between a Physical host and a SAP Host Agent instance. Depending on the network configuration, the Physical Host may have one or more FQDN/IP addresses defined.

(warning) The SAP Host agent does not return a unique FQDN/IP for a physical host – this means any FQDN/IP may be a valid from Outside Discovery process point of view.
  • Physical Host information in the Landscape Browser:
Field NameDescription
sld_idUnique Identifier of the Physical Host (one to one relation with SAP Host Agent).
full_nameFQDN provided by Outside Discovery (selected from the full_names list provided by SAP Host Agent).
typeHost type (P: Physical, V:Virtual, L: Logical)
ipIP provided by Outside Discovery (selected from the ips list provided by SAP Host Agent).
full_namesList of FQDN defined on the physical host (network configuration) – provided by SAP Host Agent
ipsList of IP defined on the physical host (network configuration) – provided by SAP Host Agent

The following picture shows the properties in the Landscape Browser:

The information provided by the Outside Discovery is also available in the LMDB definition for the host. The picture and table below shows the relation between the Landscape Browser and LMDB information.

Field Name in the LMDB Host definitionCorresponding field name in Landscape Browser
Host namesld_id
Fully Qualified Domain Namefull_name
IP AddressIp
Alternative Hostnamesfull_names/ips

6.2) Virtual Host

A virtual host has exactly the same properties as a physical host. The only exception is that a virtual host is running inside a virtualized solution (e.g. VMware …).
Regarding SAP Host Agent, same rule as physical host applies: only one SAP Host Agent can be installed on a virtual host. There is a one to one relation between virtual host and SAP Host Agent.

(info) From a discovery point of view, we are not able to discover the physical host that is hosting the virtual host.
  • Virtual Host information in the Landscape Browser:
Field NameDescription
typeHost type - V:Virtual
Virtual_sol_nameTechnical name of the virtualization solution
Virtual_sol_typeType of virtualization
Virtual_sol_versVersion of virtualization

6.3) Logical Host

Any other aliases/network adapters defined on a physical/virtual host are considered as logical host:

  • A physical/virtual host can have one or many logical hosts.
  • From a landscape point of view, Outside Discovery process is able to make a connection between a logical host and a physical/virtual host. At any time, the landscape knows which physical/virtual host is hosting a logical host.
  • In case of HA configuration, if a logical host moves from one physical/virtual host to another physical/virtual host, the change is reflected in the landscape browser.
  • A logical host inherit properties from the hosting physical/virtual host (Operating System, …

6.3.1) Logical host in Landscape Browser

The Logical Host definition can also be found in the Landscape Browser, in this definition it is possible to see which physical/virtual host is hosting the logical host.

 

6.4) Warning 'No FQDN found in Host <hostname>' during Managed system Configuration for Physical/Virtual Host.

In case the warning 'No FQDN found in Host <hostname>' is shown for a physical host during the Managed System Configuration. The following steps can be used to troubleshoot the problem.

  • Check network configuration:

Most of the missing FQDN issues are related to an incorrect network configuration. The recommended solution is to check if the hosts are correctly defined within hosts file of the Operating System. The hosts files location is:

  • On UNX:
    • /etc/hosts
  • On Windows:
  • <drive>:Windows\System32\drivers\etc\hosts

The hosts file must be configured using the following format, otherwise the information cannot be collected:

# Example of hosts files with correct format for Outside Discovery

#IP                                            Full Qualified Domain Name                                      short name

 10.79.0.12                                ld8xxx.wdf.sap.corp                                                   ld8xxx

 

  • Check FQDN reported by the SAP Host Agent

In order to check FQDN/IP information returned by the SAP Host Agent, the log of Outside Discovery process should be set in debug mode. Refer to section 'Increase the Outside Discovery Log Level to Debug' and increase the Outside Discovery process for the host to Debug. After an Outside Discovery run, the following entries can be found in the logs:

Log entryDescription
Debug [PhysicalHostPushJob:getComputerSystem] [Name][hostA]Unique identifier of the physical/virtual host returned by SAP Host Agent.

Debug [PhysicalHostPushJob:getComputerSystem] [Hostnames][localhost;hostA.wdf.sap.corp;hostA;]

Debug [PhysicalHostPushJob:getComputerSystem] [IPAdresses][127.0.0.1;127.0.0.2;10.18.112.167;]

List of FQDN/IP returned by SAP Host Agent – if hostnames only contains short name, this indicates that SAP Host Agent is not able to get FQDN correctly from the network configuration.

Debug [PhysicalHostPushJob:getComputerSystem] Physical Host Name [hostA]

Debug [PhysicalHostPushJob:getComputerSystem] resolveFQDNandIP [hostA]

Debug [PhysicalHostPushJob:getComputerSystem] resolveFQDNandIP successfully [FQDN:hostA.wdf.sap.corp][IP:127.0.0.2]

Outside Discovery is using the short host name to select the most relevant FQDN from the list provided by SAP Host Agent.

 

  • Manual Configuration of FQDN and IP for Physical/Virtual Hosts

In some cases the network configuration is too complex and the SAP Host Agent might have problems to report the correct FQDN and IP for the Physical/Virtual hosts. To overcome this problem, it is possible to manual configure the correct FQDN and IP in the Outside Discovery configuration. To manual adjust the FQDN and IP in the Outside Discovery configuration refer to note 1626853 and configure the following properties in the Outside Discovery Configuration:

Property NameDescription
job.physicalhost.fqdnUsed this property to force the FQDN for the physical/virtual host.
job.physicalhost.ipUsed this property to force the IP for the physical/virtual host.

(warning) The above properties cannot be used with SAP Solution Manager 7.10 SP03. Refer to note 1626853 for more information.

The steps to configure these properties are:

  • Access the Agent Admin UI (http://<solman_host>:<JAVA_HTTP_Port>/smd/AgentAdmin)
  • Go to Applications Configurations tab
  • Select application 'com.sap.smd.agent.application.e2edcc'
  • Select the Diagnostics Agents of the affected host in 'Scope'.    >>> DO NOT FORGET <<< >>> DO NOT USE GOBAL <<<
  • Add the configuration properties above.

The following picture describes this configuration:


6.5) Warning 'No FQDN found in Host <hostname>' during Managed system Configuration for Logical Host.

  • Missing FQDN for Logical Hosts running SAP Instances:

If the FQDN is missing for Logical Hostname of a SAP System, then maintain the following profile parameters must be check/configured n the SAP Profile to reflect the network configuration:

  • SAPLOCALHOST = <shortname>
  • SAPFQDN = <fqdn suffix>
  • SAPLOCALHOSTFULL=$(SAPLOCALHOST).$(SAPFQDN)

Below there is an example of the instance profile configuration.

#.************************************************************************************************************************************************************************************************************************************           

#.*       Default profile DEFAULT                                                                                                     

#.*       Version                 = 000001                                                                                     

#.*       Generated by user =

#.*       Generated on = 25.03.2015 , 15:15:35                                                                                 

#.************************************************************************************************************************************************************************************************************************************

#parameter created

rslg/max_diskspace/central = 12000000

#parameter created

rslg/max_diskspace/local = 3000000

#parameter created

rec/client = OFF SAPSYSTEMNAME = SD7

SAPGLOBALHOST = hostA

system/type = DS

SAPDBHOST = hostdb7

SAPLOCALHOST = hostname

SAPFQDN = wdf.sap.corp

SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)

 

  • Manual Configuration of FQDN and IP for Logical Hosts reported by the Agents On-The-Fly:

In case a FQDN is missing for a Logical Host which is reported by a SMDAgents on-the-fly, it is possible to manually configure the correct FQDN and IP in the configuration of the Diagnostics Agents node controller (SMDAgent of Physical/Virtual host). Refer to the WIKI 'Outside Discovery: Overriding IP Address or FQDN for Agent Nodes' for more information about this configuration.

 

 

 

  • No labels

1 Comment

  1. very helpful - thanks